The Run-As-Administrator, is becoming more and more painfully necessary. Just look at how many problems, even run-time ones, have been resolved in the forums.
The fix seems to be a pretty simple one (according to MS). According to this MSDN article (https://msdn.microsoft.com/en-us/library/bb756929.aspx), the only modification that needs to be done in the installer manifest file, is: --- src/VBox/Installer/win/Stub/VBoxStub.manifest (revision 68467) +++ src/VBox/Installer/win/Stub/VBoxStub.manifest (working copy) @@ -7,6 +7,17 @@ type="win32" /> <description>VirtualBox Windows Installer</description> +<!-- Identify the application security requirements. --> +<trustInfo xmlns="urn:schemas-microsoft-com:asm.v2"> + <security> + <requestedPrivileges> + <requestedExecutionLevel + level="requireAdministrator" + uiAccess="false" + /> + </requestedPrivileges> + </security> +</trustInfo> <dependency> <dependentAssembly> <assemblyIdentity And that's where your help is needed. I do not have a setup build for Windows and I can't verify that after this change, a shield should/would appear over the installer's icon. That, and the UAC prompt to verify the elevated privileges. So, any volunteers to test this seemingly innocuous patch? If that works, it will reduce the traffic in the forums by at least 30% (or close ;) ). TIA, Socratis _______________________________________________ vbox-dev mailing list [email protected] https://www.virtualbox.org/mailman/listinfo/vbox-dev
