chukcha Posted June 25, 2012 Share Posted June 25, 2012 There is a problem with UAC when create reports from logon script. If user doesn't have admin rights on Windows 7 - report created without any confirmation, this mean what there is a way to make job and not ask any questions. But when user is admin aida64 request elevation. Can you add some command line key or .ini settings to disable elevation and make job on user level ? PS: I tried "runas /trustlevel:0x20000 aida64.exe" but get error 740. 1 Quote Link to comment Share on other sites More sharing options...
Squall Leonhart Posted June 25, 2012 Share Posted June 25, 2012 aida64 initiates a driver when run, requiring admin elevation. Quote Link to comment Share on other sites More sharing options...
Mice007 Posted June 25, 2012 Share Posted June 25, 2012 You should use the following command line parameter to start AIDA64 in a network /SAFE Using this option the most common hardware incompatibility issues can be avoided by disabling low-level PCI, SMBus and sensor scanning. In network audit this option should be used in all cases to make sure AIDA64 does not cause system instability. There is a problem with UAC when create reports from logon script. If user doesn't have admin rights on Windows 7 - report created without any confirmation, this mean what there is a way to make job and not ask any questions. But when user is admin aida64 request elevation. Can you add some command line key or .ini settings to disable elevation and make job on user level ? PS: I tried "runas /trustlevel:0x20000 aida64.exe" but get error 740. Quote Link to comment Share on other sites More sharing options...
chukcha Posted June 26, 2012 Author Share Posted June 26, 2012 aida64 initiates a driver when run, requiring admin elevation. But it can work on ordinary user without admin privileges, its mean possible to create key, which will disable run driver. Quote Link to comment Share on other sites More sharing options...
chukcha Posted June 26, 2012 Author Share Posted June 26, 2012 You should use the following command line parameter to start AIDA64 in a network /SAFE Using this option the most common hardware incompatibility issues can be avoided by disabling low-level PCI, SMBus and sensor scanning. In network audit this option should be used in all cases to make sure AIDA64 does not cause system instability. Of course, I tried to use this option (and /safest too) but it not disable UAC confirmation. Quote Link to comment Share on other sites More sharing options...
Fiery Posted June 30, 2012 Share Posted June 30, 2012 You can disable elevation if you remove (or rename) the file AIDA64.EXE.MANIFEST Quote Link to comment Share on other sites More sharing options...
Petr Soucek Posted February 25, 2017 Share Posted February 25, 2017 This is old topic, but still relevant for me. Is there any way how to: 1. start AIDA64 form the network share 2. not require user intervention 3. report things like HDD serial number, HDD SMART values and memory SPD information? 4. running on Windows 7 and Windows 10 ? If I remove AIDA64.EXE.MANIFEST, AIDA64 does not report HDD serial number, HDD SMART values, memory SPD information and other low level information. Petr Quote Link to comment Share on other sites More sharing options...
Fiery Posted March 3, 2017 Share Posted March 3, 2017 You cannot achieve that, unless you disable UAC prompt or UAC completely on your workstations. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.