Skip to content
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

Open
AsianJew12 opened this issue Sep 19, 2016 · 11 comments
Open

No Windows power shell in local group policy editor (gpedit.msc) #14

AsianJew12 opened this issue Sep 19, 2016 · 11 comments

Comments

@AsianJew12
Copy link

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

  • Set-ItemProperty -Path HKLM:\Software\Policies\Microsoft\Windows\Powe ...
  • - CategoryInfo          : ObjectNotFound: (HKLM:\Software...dows\PowerShell:String) [Set-ItemProperty], ItemNotF 
      oundException
    - FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.SetItemPropertyCommand`
    
    

and as said at the manual, im supposed to do something at the windows powershell but it doesn't appear in mine, any help?

@Go2Engle
Copy link
Owner

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 =/

@mykill18
Copy link

same here

@dr-antivirus
Copy link

dr-antivirus commented Sep 19, 2016

`Set-ItemProperty : Cannot find path 'HKLM:\Software\Policies\Microsoft\Windows\PowerShell' because it does not exist.

You have to create the key manually in registry editor.
It's a long process, creating the key is just 1 step of this.
Unfortunately I can't explain more now (I have to study for exams) but I'll be back in a few days if your issue won't have been resolved until then.

@dr-antivirus
Copy link

dr-antivirus commented Sep 19, 2016

Well nevermind
Run "regedit"

  • Browse through: "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft"
  • Right click on "Microsoft" > New > Key .
  • Name it : PowerShell
  • Right click on "PowerShell" > New > Key .
  • Name it : 1
  • Right click on "1" > New > Key .
  • Name it : ShellIds // which is "shellids" without the capitals
  • Right click on "ShellIds" > New > Key .
  • Name it : Microsoft.PowerShell
  • Right click on "Microsoft.PowerShell" > New > String Value
  • Name it : ExecutionPolicy
  • Double click on "ExecutionPolicy"
  • Set Value data to Unrestricted and save.
  • Restart your pc and try again, tell me if anything changes

(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.)

@Go2Engle
Copy link
Owner

Awesome find! Is it ok If I close this then? I can reference in the future if anyone else has the issue.

@dr-antivirus
Copy link

It would be better to let the OP give us feedback before closing it.
We may need more steps to fix it 100%

@Go2Engle
Copy link
Owner

Woops didnt even realize you weren't the OP. My bad.

@mykill18
Copy link

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

@dr-antivirus
Copy link

dr-antivirus commented Sep 20, 2016

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)
You have to manually allow powershell Scripts to run.
After doing what I told you in the previous comment:

  • Open powershell (Windows key > Search > Powershell > Run as Administrator)
  • Copy-paste this (without the brackets): "set-executionpolicy unrestricted"
  • If it asks you for confirmation, answer by [Yes to all]
  • Check if it worked by typing a new command (without the brackets) : "Get-ExecutionPolicy"
    It will show you a list of "user types" or something (can't remember exactly), all with "unrestricted" next to them I guess.
  • Restart you computer and restart PoGoMap installation, and tell me if it works.

@mykill18
Copy link

Thank you very much! it worded!!!

@dr-antivirus
Copy link

Glad it helped :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants