And another one...MobMapUpdater 1.84
The problem: The updater cannot update anything when started without admin rights in that particular situation. It also cannot change its access level after it has been started (requesting admin rights is only possible when a new process is being created, not while it is running).
The solution: Why not start another instance of the updater and force Windows to request admin privileges for this new instance? The new instance will then have admin rights, and the old one is immediately terminated. If you don't know what's actually happening, this looks like the updater requesting admin rights during startup - and it only requests those if the problematic situation requires them!
The newest version 1.84 does exactly that. Thus it will look like the old 1.81 on any machine where admin rights are required to update addons, but it won't request them on any machine where they are not required. If this works out without any bugs now, it's the perfect solution!

