Your forum account is not the same as the account used in the shop. They are completely separate accounts.
Uninstalling v2.0.224.0
Hi Stephen
Just updating from v224 to v238, and noticed this error-message on the uninstall of the former. I think I've reported it once before, but this time I wrote down the text in full, in case that helps. It says:
Warning 1910.Could not remove Shortcut GoFlight Interface Tool.lnk. Verify that the shortcut file exists and that you can access it.
I'm not entirely sure which shortcut this is referring to, though. I'm using Windows 7 Professional 64-bit. The shortcut on the desktop is removed successfully, as is the entire PollyPot Software folder from the Start Menu. However I notice that there is still a shortcut in the Start Menu, at the top, above the All Programs line (maybe this one is just created by Windows itself, as a 'Recent' hint - not sure).
Hope this sheds some light - perhaps others can chip in if they are noticing the same thing?
Cheers
Neil
(apologies for posting this in User Provided Bespoke Events - for some reason, using Internet Explorer 9, it's impossible to select anything from the Vanilla Forums Category dropdown box, and this is the unchangeable default! - Sorry Scrub that... the dropdown works in Chrome, so I moved it to a more appropriate place. Not sure why it doesn't work in IE. )
Comments
Hi Neil,
I'll test it out and come back to you. The categories are working now by the way!
Best wishes
Steve
Having same error message when uninstalling but I'm sure it'll be fixed.
Regards...Marc
cut before I can move my mouse. So it is removing the short cut and nothing is left behind except for the config folder, I checked using Ccleaner after I did an uninstall. So it does remove it just not sure why the error pops up..
Terry
For ref - still occurring when uninstalling v2.304.0 tonight. I wonder if this is because I always select the 'Everyone' option when installing it in the first place? I'm figuring the shortcut would then be written to a different location rather than the per-user location, and is thus subject to different Windows permissions?
Cheers
Neil