08-04-2015, 04:13 PM
Not a bug. but just a heads up:
I was used to just turn UAC off in Windows 7 and everything in QM ran correctly.
I am in the process of upgrading my 3 machines to Windows 10 and noticed that macro's where not running correctly.
(Got a lot of "Failed" errors)
It turns out that turning of UAC alone is not sufficient anymore, you also have to run QM itself as admin.
I tried to setup QM to make it run as admin but:
If I go to QM >> Options >> TAB: General >> dropdown listbox "Run as" = disabled (ghosted).
The following also didn't work for me
Setting permission through right click QM icon >> properties >> TAB: security >> Users (PC-NAME\Users) => did not work
So I just:
I right click the QM icon and select "Run as Admin"
EDIT:
Is there a way to set up a macro that is compiled to .exe to always run as admin? (Could not find it in the compile options).
I assume this has nothing to do with QM but just the way Windows 10 is constructed internally permission wise...(?)
I was used to just turn UAC off in Windows 7 and everything in QM ran correctly.
I am in the process of upgrading my 3 machines to Windows 10 and noticed that macro's where not running correctly.
(Got a lot of "Failed" errors)
It turns out that turning of UAC alone is not sufficient anymore, you also have to run QM itself as admin.
I tried to setup QM to make it run as admin but:
If I go to QM >> Options >> TAB: General >> dropdown listbox "Run as" = disabled (ghosted).
The following also didn't work for me
Setting permission through right click QM icon >> properties >> TAB: security >> Users (PC-NAME\Users) => did not work
So I just:
I right click the QM icon and select "Run as Admin"
EDIT:
Is there a way to set up a macro that is compiled to .exe to always run as admin? (Could not find it in the compile options).
I assume this has nothing to do with QM but just the way Windows 10 is constructed internally permission wise...(?)