Michiel

Standard user in Windows 7 Premium

4 posts in this topic

I've noticed that when logged on as a "standard user" in Windows 7 Home Premium, even when i've confirmed an elevation prompt, I still don't have write access to e.g. the registry or the program files folder.

I can make the user in question member of Administrators, but that's not point. What causes this? Is this known?

Also, when I start a process as an elevated user, the privileges gained don't seem to propagate further to child processes as I'm accustomed to. Does this sound familiar?

Share this post


Link to post
Share on other sites



Sounds like you might be wrestling with a group policy, >link to topic.


Snips & Scripts


My Snips: graphCPUTemp ~ getENVvars
My Scripts: Short-Order Encrypter - message and file encryption V1.6.1 ~ AuPad - Notepad written entirely in AutoIt V1.9.4

Feel free to use any of my code for your own use.                                                                                                                                                           Forum FAQ

 

Share this post


Link to post
Share on other sites

You need to post some code so we can see where the problem might be. How do you start "child processes"?


My UDFs and Tutorials:

Spoiler

UDFs:
Active Directory (NEW 2017-04-18 - Version 1.4.8.0) - Download - General Help & Support - Example Scripts - Wiki
OutlookEX (NEW 2017-02-27 - Version 1.3.1.0) - Download - General Help & Support - Example Scripts - Wiki
ExcelChart (2015-04-01 - Version 0.4.0.0) - Download - General Help & Support - Example Scripts
Excel - Example Scripts - Wiki
Word - Wiki
PowerPoint (2015-06-06 - Version 0.0.5.0) - Download - General Help & Support

Tutorials:
ADO - Wiki

 

Share this post


Link to post
Share on other sites

#4 ·  Posted (edited)

Sounds like you might be wrestling with a group policy, >link to topic.

 

It's Windows 7 Home Edition, it isn't connected to a domain. Thanks for replying though.

You need to post some code so we can see where the problem might be. How do you start "child processes"?

 

With all due respect, but, what's with the quotes? Are you suggesting I don't understand what a child process is?

Obviously I mean spawned from e.g. cmd, explorer or AutoIt. In any case, the child process should inherit the parent process' privileges.

Edited by Michiel

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now