PowerShell AuthorizationManager check failed (resolution)

I recently had a problem running PS scripts on one of my servers running Windows Server 2003. Every script was failing with the following error message;

AuthorizationManager check failed.
At line:1 char:2
+ . <<<< ‘C:\Path\Microsoft.Powershell_profile.ps1’
+ CategoryInfo : NotSpecified: (:) [], PSSecurityException
+ FullyQualifiedErrorId : RuntimeException

Here are the steps I took to clear the error in my environment.

– First, check PowerShell to ensure the ExecutionPolicy is not set to “Restricted”.


If it is, set it to either “RemoteSigned” or “Unrestricted” depending upon your security preferences.

Set-ExecutionPolicy RemoteSigned

If the error continues;

– Check to make sure Windows Management Instrumentation service (WMI) is Enabled and running. If it’s disabled, try enabling it and starting it to see if that clears the error.

– Occasionally, with the ExecutionPolicy set to “RemoteSigned” or “Unrestricted”, this error may occur if the script was downloaded from the internet using Internet Explorer and IE has “blocked” the file. Right-click the file, select “Properties” and click “Unblock”.

– If all else fails, go to the path noted in the error and delete the PowerShell profile file.

If you found the answer to your problem here, please leave me a quick comment to let me know! You can also find me on Google+.

VN:F [1.9.22_1171]
Rating: 4.2/5 (9 votes cast)
PowerShell AuthorizationManager check failed (resolution), 4.2 out of 5 based on 9 ratings
Want to share?
This entry was posted in Techy Stuff and tagged , , , , , , , , , , . Bookmark the permalink.

13 Responses to PowerShell AuthorizationManager check failed (resolution)

  1. I had the same issue. Turns out it was the file encoding of my profile files. It was ASCII and needed to be UTF8. Not sure how they got this way… I suspect it was PowerGUI… Anyway here’s a one liner fix.

    “$pshome\Microsoft.PowerShell_profile.ps1”, $profile | % {$p = $_ ; [IO.File]::ReadAllText($_) | sc -Path $p -Encoding UTF8}

    VA:F [1.9.22_1171]
    Rating: +3 (from 5 votes)
  2. Adrian says:

    Muchas Gracias, luego de un dia completo de intentar resolver el issue gracias a tu publicacion lo puede resolver.

    VA:F [1.9.22_1171]
    Rating: 0 (from 0 votes)
  3. Jack says:

    Thanks a lot!

    VA:F [1.9.22_1171]
    Rating: 0 (from 0 votes)
  4. F. Morrison says:

    Caution: when you copy/paste Andy’s excellent suggestion, the double-quote characters may not copy property.

    Instead of “straight-up vertical” double-quote characters, you may get the “leaning slightly on their side” type of double-quote characters, so retype them with the ones from your keyboard before running that script in PowerGUI.

    (this might be obvious to experience uses, but I figured I would write this for any newbies that might try Andy’s suggestion and wonder why it doesn’t work at first).

    VA:F [1.9.22_1171]
    Rating: +2 (from 2 votes)
  5. hari says:

    Thank you. It worked

    VA:F [1.9.22_1171]
    Rating: 0 (from 0 votes)
  6. Saransh says:

    Unblocking the downloaded file did the trick and resolved it. Thanks.

    VA:F [1.9.22_1171]
    Rating: 0 (from 0 votes)
  7. Seb says:

    Thanks, the “unblock” thing helped me a lot 😉

    VA:F [1.9.22_1171]
    Rating: 0 (from 0 votes)
  8. Cedric HENRY says:

    I got the same issue and use the steps above it solved.
    Then, the issue reappeared as I started using a self-signed certificate instead of the test certificate generated from Visual Studio. It gave me quite a headache until I found the the solution under http://stackoverflow.com/questions/8815145/how-to-trust-a-certificate-in-windows-powershell.

    VA:F [1.9.22_1171]
    Rating: 0 (from 0 votes)
  9. John says:

    Many thanks for writing this article! The IE Unblock solved the issue for me!

    VA:F [1.9.22_1171]
    Rating: 0 (from 0 votes)

Leave a Reply

Your email address will not be published.