Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, July 10, 2018 5:26 PM
In our work environment the computers are very locked down through group policy and a few registry entries. We've been transitioning to windows 10 from our working windows 7 platform. Long and short of it is that we have a batch file that will open cmd prompt as the built in administrator and prompt for the password to give our techs a way around to be able to access what they need to fix the daily blips. Somehow when attempting to run the command to do something such as "explorer c:\blah\blah" it comes back with an error message about permissions. I've removed all the group policy settings and I still get that error. When simply running the regular command prompt of the "user" it will open file explorer to the folder I designate. It seems that somehow the elevated runas administrator command prompt won't run when logged in as "user". This was not a problem previously. I'm continuing more testing and research but I figured it could save me some time if someone else has run into or seen something similar.
Oh, I also checked the permissions for explorer.exe and it is identical for all administrators and users
All replies (4)
Tuesday, July 10, 2018 5:51 PM
to give our techs a way around to be able to access what they need to fix the daily blips.
Don't fix the symptom; fix the problem.
Tuesday, July 10, 2018 5:54 PM
/user <UserName> should be in form USER@DOMAIN or DOMAIN\USER
Wednesday, July 11, 2018 1:34 PM
The syntax in the batch file is correct. The workstations we have are not part of the domain. On our current windows 7 boxes we use the same batch cmd to log on as the enabled/activated built in administrator account so that the cmd prompt is "running as administrator". How could that possibly not have permission to file explorer? I also just realized that it was working properly until windows updated the other day. Something bizarre broke. I was hoping I would get some special insight but I'm starting to think it's a needle in a haystack to figure out what happened and to just start over.
Thursday, July 12, 2018 9:42 AM
Hi，
What's your build of Windows 10?
I have test on Windows 10 1803, if my built-in Administrator account is enabled. I can run runas /user:administrator cmd command in Run box successfully.
Thus it might be any other problem in your batch file. Here I suggest you post your whole script in script forum to see if your script have problem.
https://social.technet.microsoft.com/Forums/scriptcenter/en-US/home?category=scripting
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].