I think I’ve commented on this before. When updating Scrivener using Scrivener’s internal update function, Windows shows one version and Scrivener shows another version.
I don’t often update using the internal updater; it has led to issues in the past. However, this time I did so again, and while the “Help > About” function in Scrivener shows version 40, in “Windows > control Panel > Programs and Features,” it says the installed version is 2.9.0.39.
Not sure what’s missing. Other programs do not suffer from this issue (Firefox, for example).
I had done those steps to removed previous versions I had uninstalled but as I don’t really see it as a problem I think I’ll let it stand. I had also uninstalled the program 2 or 3 times after that version due to some type of issue but its been working just fine now as I use the built in updater.
I too have had this issue. I think I have 20 versions of Scrivener now. I use to uninstall and reinstall. But it did weird things with my save files, or at least once it did. So I’m just waiting for full release before I clean it out.
It probably doesn’t hurt to leave them there or clean them. Either way I think it is just Windows junk that doesn’t have any impact on the software itself. When I clear them, it asks for permission to run the installer, then it fails and I click “yes” and it vanishes. I’ve had to do this a few times now and then. Generally I do the uninstall/reinstall routine though as that is best practice in a beta (tip: save your preferences to a file using the “manage” button; the only downsides to reinstall is the extra 20 seconds it takes, and having a click through the one-off warnings once again).
Ultimately it would be nice to get this addressed, but it’s pretty low priority since it is benign—and I have a feeling it is more a bug with the kit used to create the installer. It’s been around since forever, I think people were noting this back when 1.0 was in beta.
It’s not totally benign – it can under certain circumstances cause issues with repairing/uninstalling Scrivener from the installer – but yeah, it’s likely a bug in the installer kit or a missed call/exception in the code that calls the installer. Because yes, it has always been present.
…or use the built-in Windows tools (Control Panel, Uninstall Programs) to do the same thing without having to open the registry editor for people who have no business using it, as narrsd mentioned in another thread.
…and having to recreate your customized toolbars. Unless the beta is now saving toolbar settings to the preferences file, which it wasn’t last time I checked many versions ago.
Possibly something quirky on my PC, but I tried that first and was unable to uninstall the non-existent earlier versions. So, if anyone else has that problem, the Regedit fix takes care of it.
