I’m noticing that the Odrive version is not matching up to what is being displayed in Installed Programs. This appears to be a new(er) bug as I have not ran into this with previous installations -
Hi @lopsahl ,
This will happen if an automatic update is deployed. The update is done within the user context so it updates the binaries deployed in the user’s profile and leaves the Program Files files (and the install/uninstall information) untouched.
Hey Tony,
Thanks for the response. The predicament I am running into now is our monitoring agent (and I would assume most) report based off the Program Files. This makes it difficult me to know what is the next version upgrade our machines need, how many users are on what version, etc.
Is there a way to know what announced updates are automatic vs. not? Or are they now all automatic, and if so, can this be disabled in the installation?
Thanks!
Hi @lopsahl ,
We post all of the notes for every release here: Release Notes - odrive Forum
You can click on the bell icon to register for notifications whenever there is a new release to stay up to date. We don’t push out autoupdates very often because the client is at a very stable point. When we do it is usually to address a specific item with an integration (new API change or requirement) or an OS need. We don’t announce the autoupdate, currently.
The current version for each user can be determined by reading the “version” file in the user’s profile directory under the .odrive directory (i.e. C:\Users\[user name here]\.odrive\version)
You can also set an advanced seting to prevent the autoupdate from restarting the software. It will acquire the new version, but won’t use it until an odrive restart.