User Access Control (UAC) and automated builds

[kinook]

On Windows Vista and later with UAC (User Account Control) enabled, applications started by an admin user do not have admin rights. Visual Build itself does not require admin rights to run or perform builds, but this limitation can cause problems with common build activities such as COM registration, COM+ administration, copying files to protected folders, editing HKEY_LOCAL_MACHINE registry entries, etc. To perform these tasks, you may need to explicitly run VBP in an elevated mode (with administrative privileges). Here are some ways to do this:

1) Right-click the Visual Build icon and choose Run as Administrator (if not available, hold down Shift while right-clicking).

2) Right-click the Visual Build icon and choose Properties, switch to the Compatibility tab and check Run this program as administrator.

3) Task Scheduler: Configure the task to run under an administrator account, and on the General tab of the Task properties dialog, check the Run with highest privileges checkbox.

4) Run Visual Build from a Command Prompt that was run as administrator.

5) Disable UAC on the build box:

Windows 11: https://www.minitool.com/news/how-to...indows-11.html

Windows 10: https://winaero.com/blog/how-to-turn...in-windows-10/

Windows 8: https://www.petri.com/disabling-user...-windows-8.htm

Windows 7: https://www.petri.com/disable-uac-in-windows-7.htm

Windows Vista: http://www.petri.co.il/disable_uac_in_windows_vista.htm


Note: To detect whether the build is running as an elevated admin user, the isadmin.exe utility (https://web.archive.org/web/20220704...om/?page_id=23) can be called from a Run Program action. Use a Success exit codes field value of 1 to succeed for elevated admins and fail for non-admins/unelevated admins.