Elevated Program Shortcut - Create for Standard User

What were the names of the 3 programs, and I'll see if I may be able to install them to play with. :)

1. Asus DigiPower Control Help
2. Asus AI Suite II Execute
3. Not Starting up have to fix.

I'm not going to be able to install them since those programs are specific to only Asus OEM PCs.

Oh I'm still on the issue, hopefully someone can give me a solution, until then, I have to manually enter in the UAC password each time the computer logs-in.

If you don't use those programs, you could disable them from running at startup to no longer get a UAC prompt for them at log in. Afterwards, you could just run them as needed from their shortcuts.

Startup Programs - Change

I use two of those programs. I've unable to get a solution, I've had solutions presented, none have worked so far

Hello Tech77,

Please go ahead and post screenshots showing what you are seeing instead in the steps.

Screenshots and Files - Upload and Post in Seven Forums

Since you have the "Include inheritable permissions from this object's parent" check box, it means that this file already has "disable inheritance" from parent (source) folder applied.

Are you able to pick up at step 14 to set permissions for the user?

Hello, Shawn, and thanks for the quick reply. I'd also like to take a moment to express my thanks for all the valuable knowledge and insights I've gained from your tutorials & replies @ the various Vista/7/8 Forums over the years. Here are the requested screenshots of what I see in the various tabs & dialogs invoked from the context menu Properties sheet of a shortcut (or any other file) on this W7 HomePremSP1 build. For Step 9, the Properties sheet of the shortcut copied to the standard user's desktop, after navigating to that folder while still logged in to the Administrator account shortcut was created in:



For Step 10, the Properties sheet's Security tab:



Clicking "Advanced" results in the below Advanced Security Settings dialog box:



The "Change Permissions..." button must be clicked to invoke a dialog box similar to that shown in Step 11 of the tutorial; it's the right-hand one in the next screenshot (this dialog box is also named Advanced Security Settings; I've noticed that the "Include inheritable permissions from this object's parent" tick-box is always ticked - and #greyed out - in this dialog box, for any object, whether of container or non-container variety, that I've seen on this build):



It can be seen that the "Disable Inheritance" button is missing, replaced on this build by another "Change Permissions..." button and an "Include inheritable permissions from this object's parent" tick-box that is active, and that may indeed be toggled to change permissions; it does not, however, invoke the "Block Inheritance" dialog box shown in the tutorial's Step 12, but rather a Windows Security warning dialog:



Clicking "Add" - which the Security warning dialog says will "...convert and add inherited parent permissions on this object" - would seem to do exactly the opposite, as evidenced (I believe) by the results shown in the below screenshot, which shows permissions are "<not inherited>"; since the permissions were inherited when the tick-box "Include inheritable permissions from this object's parent" was ticked (see earlier screenshot #5), and removing the tick removes the inherited permissions, I assume that this is correct behavior, and that either the Windows Security warning dialog is poorly worded or, perhaps more likely, I am simply failing to interpret it correctly. One thing I've noticed in creating these elevated shortcuts is that doing so from the built-in administrator account never results in that account being listed in the DACL shown in the security tab, and that adding it to the list through the "Select User or Group" dialog always results in that account's permissions showing as "<not inherited>", but I don't yet have a firm enough grasp of NT security principles to understand why this is so...Here's the result of clicking the "Add" button in the Windows Security warning dialog:



And here's the result of clicking the "Remove" button in the Windows Security warning dialog - all groups and users have been removed from the object's DACL, with the caveat that the object's owner may now assign permissions, as shown below:



I have screenshots showing how the "Change Permissions..." button may be utilized to invoke the "Select User or Group" dialog and add either back into the DACL, but I realize this post is already rather long, and I'd like to see what you think of what I've demonstrated so far. I've already verified that my initial assumption, concerning possible involvement of the use of Windows Classic theme (which I prefer because of the "Display full path in the title bar (Classic Theme only)" feature), holds no water, as I created a pristine user account with the default Windows 7 settings in Folder Options, onto which account's desktop I placed this shortcut, and then took these screenshots of it's security tab (while still logged into the elevated admin account) - the results are exactly the same as those for shortcuts in my daily-use standard account, which does have Folder Options set to my personal preferences. As I've already reverted this build to the Factory partition's "OOB" settings in researching this permissions behavior without making any difference in what the security tab's advanced settings show, I'm starting to think that the OEM has done some strange things via their WIM or WAIK in creating this build...or that I'm more clueless than I had imagined!

If you like, a standard user is able to run the perfmon.exe file without having to "run as administrator".

Since this is a system file, this is why you have "Change Permissions" instead. To restore the default permissions of this file, you will need to check the Include inheritable permissions from this object's parent box in your last screenshot, and click on OK.