I found this: UAC Whitelist for Windows 10 · GitHub
And works. I have UAC always on, and policy for scripts Restricted, so to enable a white list for applications like VB6 which do changes to OS, and produce at execution the dark frame to choose to proceed or not (with that beep sound) always shown (according to UAC choice), do as I do:
Open powershell as admin, then change to directory of the script file (which download from the above git and prepared the white list, name for a shortcut which the script produced in the "target" folder - read it the comments).
First you have to change for a while the restrictions of execution scripts, checking this (on powershell:
Get-ExecutionPolicy -List
You would see this (maybe something near this):
So we have to change the execution policy for local machine using this:
Set-ExecutionPolicy Unrestricted
And then we run the script adding .\ before the name:
.\uac-whitelist.ps1
And change again the restriction:
Set-ExecutionPolicy Restricted
So now we open the "target folder", and we will see the created shortcuts
just choose from context menu to copy whatever you want (at the Start menu, or the Task Bar). So now you have UAC and VB6 start without the annoying problem.
Also I have done another job for security, I have signed the VB6, so there is no problem with the "unknown..." tag.
(I have made two certifications, one saved as root CA authority, and the other is one from that Root, so I apply the second one to Vb6, so when the system check it, find it valid)
And works. I have UAC always on, and policy for scripts Restricted, so to enable a white list for applications like VB6 which do changes to OS, and produce at execution the dark frame to choose to proceed or not (with that beep sound) always shown (according to UAC choice), do as I do:
Open powershell as admin, then change to directory of the script file (which download from the above git and prepared the white list, name for a shortcut which the script produced in the "target" folder - read it the comments).
First you have to change for a while the restrictions of execution scripts, checking this (on powershell:
Get-ExecutionPolicy -List
You would see this (maybe something near this):
Code:
Scope ExecutionPolicy
----- ---------------
MachinePolicy Undefined
UserPolicy Undefined
Process Undefined
CurrentUser Undefined
LocalMachine RestrictedSet-ExecutionPolicy Unrestricted
And then we run the script adding .\ before the name:
.\uac-whitelist.ps1
And change again the restriction:
Set-ExecutionPolicy Restricted
So now we open the "target folder", and we will see the created shortcuts
just choose from context menu to copy whatever you want (at the Start menu, or the Task Bar). So now you have UAC and VB6 start without the annoying problem.
Also I have done another job for security, I have signed the VB6, so there is no problem with the "unknown..." tag.
(I have made two certifications, one saved as root CA authority, and the other is one from that Root, so I apply the second one to Vb6, so when the system check it, find it valid)