-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No Windows power shell in local group policy editor (gpedit.msc) #14
Comments
I would do some google searching on this. Seems like an issue with the PC and not the application. I would do some searching but I'm at work right now ahh =/ |
same here |
You have to create the key manually in registry editor. |
Well nevermind
(I had to do this, but with many other steps so not sure which step is the one who made PowerShell recognized and unrestricted. By the way I could never see Powershell in gpedit.msc, and I didn't need it. Manually allowing the scripts to run via programming code made the job for me.) |
Awesome find! Is it ok If I close this then? I can reference in the future if anyone else has the issue. |
It would be better to let the OP give us feedback before closing it. |
Woops didnt even realize you weren't the OP. My bad. |
Same issue here, thanks for the help but it didn't resolve my problem,i still got the same error, plus it seems that i dont have "windows powershell" folder in gpedit.msc: Computer Configuration > Administrative Templates > Windows Components > Windows PowerShell |
Nobody seems to have Powershell in gpedit.msc (including me, but I made it work without needing to edit Powershell in gpedit.msc options)
|
Thank you very much! it worded!!! |
Glad it helped :) |
I'm having this error
`Set-ItemProperty : Cannot find path 'HKLM:\Software\Policies\Microsoft\Windows\PowerShell' because it does not exist.
At line:1 char:1
and as said at the manual, im supposed to do something at the windows powershell but it doesn't appear in mine, any help?
The text was updated successfully, but these errors were encountered: