The first screenshot shows that Synctool is enabled and should be disabled. I appear to have released with my synctool config file still in place, my bad, just delete synctool_config.json from the root of QuickPlay's directory and that will go away. But this should not stop you playing games at all, Synctool should just exit because it has no work to do and your game should load, the screenshot you showed does not show an error, it shows that synctool has no work to do and is going to exit
The second screenshot you post seems to be the same error we have already talked about in this thread and on PM, and I have been waiting for your reply on PM: I do need someone to do some troubleshooting with that error, you were going to work out whether the affected rom has been compressed with LZMA2 (you can look for its properties in the 7zip file manager to tell you that) and work out if the errors only happen with LZMA2 compressed roms, or not? I also asked if you could try a clean install of the latest QuickPlay and see if that error is the same with the same rom - to make sure you really do have the new 7z.dll file and there hasn't been some drag+drop problem (could you try diffing/comparing the file properties of 7z.dll in quickplay 3.8.4 with the latest QuickPlay just to make 100% sure you are using an updated dll file - i say this because the error is what i'd expect the old 7z.dll to give if passed a goodmerged LZMA2 rom)? Finally I asked if you could just send me one of the affected roms (and perhaps an unaffected one, you did have unaffected roms last time this happened to you I seem to recall?) so I could test myself to work out what the problem is? I need as much information as possible to figure out what causes which roms to give that error, otherwise you will continue to get that error
Lastly, in terms of upgrading, because QuickPlay is a portable app, doesn't use the registry and wants to be as free and open as possible, there is no msi install package to do any upgrade logic, just a drag+drop process. The second guide on the QuickPlay wiki, the one I linked you to at the start of this topic, gives upgrade instructions:
http://quickplay.sourceforge.net/wiki/i ... /Upgrading - the instructions are basically to take a copy of QuickPlay first, and THEN drag and drop the new files over the old ones. If you do that, then if the new QuickPlay doesn't work as you want it, the old one is just the same as it ever was, and there's no need to panic. However, I would say that there is no DATS folder in a new QuickPlay zip file, and that's where all the settings live, so I'm pretty suprised that any of your settings could possibly be overwritten.
I would say, that users do need to help for open-source development to work - there is too much work for a developer to do unpaid in their own free time (there is some debate at the moment about open source software and where the whole ideology has gotten us). If you can do some troubleshooting to tell me exactly which of your settings got overwritten, what file they seem to have been in, and what they were overwritten with, then that will help me write something that will protect errant old settings when upgrading. Again having your old QuickPlay folder and your new one would help you with doing that. But it sounds like maybe you unpacked new QuickPlay in a new folder and ran it and expected it to remember the settings of your other QuickPlay? QuickPlay is a portable app, no data is stored outside our QuickPlay's own folder, and that's a great thing!