Windows 10: powershell -executionpolicy not recognized

Discus and support powershell -executionpolicy not recognized in Windows 10 Support to solve the problem; I need to enter this command into ps: >PowerShell -ExecutionPolicy bypass -file "C:\Program Files\Stubby\stubby_setdns_windows.ps1" - i tried enter... Discussion in 'Windows 10 Support' started by empleat, Aug 29, 2019.

  1. empleat Win User

    powershell -executionpolicy not recognized


    I need to enter this command into ps:

    >PowerShell -ExecutionPolicy bypass -file "C:\Program Files\Stubby\stubby_setdns_windows.ps1" - i tried enter this command without >PowerShell and without -file

    But i still get error:

    -ExecutionPolicy : The term '-ExecutionPolicy' is not recognized as the name of a cmdlet, function, script file, oroperable program. Check the spelling of the name, or if a path was included, verify that the path is correct and tryagain.

    I found this and this didn't help me at all. I checked in registry that new entries are there and command run successfully.

    https://absolute-sharepoint.com/2014/03/change-powershell-machinepolicy-execution-policy-windows-server-2012r2.html


    Also i am using powershell 2.0

    Please help!

    :)
     
    empleat, Aug 29, 2019
    #1
  2. Kursah Win User

    PowerShell instead of Commandline in Creators Update

    Interestingly enough my personal laptop just got the update...and still has Command Prompt listed, not PowerShell...

    Edit: Not that it matters...I use both regularly. *Toast :toast:
     
    Kursah, Aug 29, 2019
    #2
  3. Windows 10 - the remote procedure call failed

    Hi,

    Thanks for the response.

    I suggest you to follow the below steps and check if it helps:

    • In the Search box, type PowerShell

    • Right click on PowerShell and choose
      Run as administrator

    • In the command prompt, enter the following command:

    • PowerShell -ExecutionPolicy Unrestricted -Command "& {$manifest = (Get-AppxPackage Microsoft.WindowsStore).InstallLocation + '\AppxManifest.xml' ; Add-AppxPackage -DisableDevelopmentMode -Register $manifest}"
    Thanks.
     
    Divya Murugan, Aug 29, 2019
    #3
  4. powershell -executionpolicy not recognized

    Windows 10 app store not working propperly

    Hi Connor,

    Thank you for posting your reply.

    I suggest you to run the powershell command by following the steps below:

    • Right click on Start button and select “Command Prompt (Admin)”.
    • Type “powershell -ExecutionPolicy Unrestricted Add-AppxPackage -DisableDevelopmentMode -Register $Env:SystemRoot\WinStore\AppxManifest.xml” (Without quotes) and press Enter.
    Hope the information is helpful. Keep us posted on the status.
     
    Eeshwar Kumar, Aug 29, 2019
    #4
Thema:

powershell -executionpolicy not recognized

Loading...
  1. powershell -executionpolicy not recognized - Similar Threads - powershell executionpolicy recognized

  2. Powershell

    in Windows 10 Customization
    Powershell: This post does not belong in "Windows settings." There is no category to actually post this discussion to. For all the effort Microsoft is making to embrace command line utilities via powershell, you'd think the forums would include a category similar to, I don't know,...
  3. powershell

    in Windows 10 Network and Sharing
    powershell: hi what is the Powershell Adminitrator command to check for corrupt file i.e. "slp /?? https://answers.microsoft.com/en-us/windows/forum/all/powershell/abf64006-a888-4ca6-97af-a2821fc06c57"
  4. The Next Release of PowerShell - PowerShell 7

    in Windows 10 News
    The Next Release of PowerShell - PowerShell 7: Recently, the PowerShell Team shipped the Generally Available (GA) release of PowerShell Core 6.2. Since that release, we’ve already begun work on the next iteration! We’re calling the next release PowerShell 7, the reasons for which will be explained in this blog post. Why...
  5. How to fix PowerShell1 ExecutionPolicy Error

    in Windows 10 BSOD Crashes and Debugging
    How to fix PowerShell1 ExecutionPolicy Error: If I edit the Registry Values for the "ExecutionPolicy" it does not change the error for my system. When I perform a cold boot the setting reset....
  6. Powershell/Powershell admin missing

    in Windows 10 BSOD Crashes and Debugging
    Powershell/Powershell admin missing: When finding a solution to remove skype today I came across a post here where the solution was found to use a powershell command. So I went to open it up and found out it was missing. I looked into it and found some other people with a similar problem, and they went to check...
  7. hkey machine powershell 1 shell id microsoft executionpolicy is bad and i dont know how to...

    in Windows 10 BSOD Crashes and Debugging
    hkey machine powershell 1 shell id microsoft executionpolicy is bad and i dont know how to...: it was detected as bad by dell who used Norton power eraser to locate the issues in my computer, Norton says they can not fix it, that Microsoft needs to fix it , I came to micorosoft to get help a tech, tried to reinstall Microsoft windows, after the computer restarted a...
  8. CMD and PowerShell

    in Windows 10 BSOD Crashes and Debugging
    CMD and PowerShell: Hi all, I run Windows 10, v 1803. Clicking Start, typing CMD, there is only "Command Prompt (desktop application)". Win key + X shows "Windows PowerShell" and "Windows PowerShell (Admin)". If after Win key+R I choose Windows PowerShell" pops up a message: Same with...
  9. No PowerShell cmdlets recognized

    in Windows 10 Support
    No PowerShell cmdlets recognized: Running powershell as Administrator or running the ISE as Administrator (which shows Admin at top of one of the two images) isn't returning what I am expecting for looking at tasks scheduled. Any idea what's up with the output in the images? I was running Windows 7 Home...
  10. PowerShell

    in Windows 10 Performance & Maintenance
    PowerShell: I have a 64-bit laptop running Win 10 Home. I just notice in All apps, there is an entry of PowerShell and PowerShell (x86). I realize the former is for 64-bit and the latter is for 32-bit. Question : In my 64-bit laptop, when I open PowerShell, which one am I...