Client version not changing in registry after 9.0.649 upgrade from 8.2.1409

(imported topic written by PKLumos)

We recently migrated from an 8.2.1409 server to a new 9.0.649 server. I migrated my clients to the new server by switching their masthead in an action on the old server. Once the clients hit the new server, I had an open action to upgrade all the 8.x clients to 9.0.649.

They have all migrated and updated successfully, but I’ve noticed a quirk. The clients do report as 9.0.649 based on the Agent Version property, however the BesClientDeploy tool showed them as still running 8.2.1409 due to the fact that the HKLM\SOFTWARE\BigFix\EnterpriseClient key still has the version listed as 8.2.1409. No amount of repairing or reinstalling over top would rectify this. I had to totally uninstall the client and reinstall for this version to report correctly. This is an unacceptable option.

Seeing as how some relevance statements are based on this key, I feel that this could be an issue. Why is this key not being overwritten/updated in an upgrade scenario?
Is this fixed in 9.0.777?

Edit: This is not fixed in 9.0.777.

(imported comment written by cstoneba)

Interesting, mine too (except we went from 8.2.1312.0 to 9.0.649.0).

(imported comment written by MattPeterson)

I found the same problem with my clients. We started at 9.0.649 and upgraded to 9.0.777, but the key is set to 9.0.649.