I get an error when I try to run PowerShell:
Internal Windows PowerShell error. Loading managed Windows PowerShell failed with error 80070002.
I am running Windows 7 Home Premium (64-bit). This error occurs whether I start PowerShell from the command line or from the start menu shortcut. Running as administrator does not solve the issue either.
How do I fix this problem, so that I can use PowerShell?
asked May 15, 2011 at 14:31
sourcenouveausourcenouveau
3,5663 gold badges31 silver badges37 bronze badges
I used my laptop’s system recovery feature to reinstall Windows, and then I was able to use PowerShell just fine.
answered Nov 19, 2011 at 20:15
sourcenouveausourcenouveau
3,5663 gold badges31 silver badges37 bronze badges
This is caused by missing
Microsoft.PowerShell.ConsoleHost.dll
Which should be at
C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.PowerShell.ConsoleHost
It can be restored reinstalling Windows Management Framework
PowerShell failed with error 80070002 — Server Fault
answered Jul 6, 2014 at 9:55
Have you tried reinstalling powershell? This sounds like a corrupted install.
answered Nov 19, 2011 at 13:02
wullxzwullxz
2,7364 gold badges26 silver badges38 bronze badges
2
You must log in to answer this question.
Not the answer you’re looking for? Browse other questions tagged
.
Not the answer you’re looking for? Browse other questions tagged
.
I get an error when I try to run PowerShell:
Internal Windows PowerShell error. Loading managed Windows PowerShell failed with error 80070002.
I am running Windows 7 Home Premium (64-bit). This error occurs whether I start PowerShell from the command line or from the start menu shortcut. Running as administrator does not solve the issue either.
How do I fix this problem, so that I can use PowerShell?
asked May 15, 2011 at 14:31
sourcenouveausourcenouveau
3,5663 gold badges31 silver badges37 bronze badges
I used my laptop’s system recovery feature to reinstall Windows, and then I was able to use PowerShell just fine.
answered Nov 19, 2011 at 20:15
sourcenouveausourcenouveau
3,5663 gold badges31 silver badges37 bronze badges
This is caused by missing
Microsoft.PowerShell.ConsoleHost.dll
Which should be at
C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.PowerShell.ConsoleHost
It can be restored reinstalling Windows Management Framework
PowerShell failed with error 80070002 — Server Fault
answered Jul 6, 2014 at 9:55
Have you tried reinstalling powershell? This sounds like a corrupted install.
answered Nov 19, 2011 at 13:02
wullxzwullxz
2,7364 gold badges26 silver badges38 bronze badges
2
You must log in to answer this question.
Not the answer you’re looking for? Browse other questions tagged
.
Not the answer you’re looking for? Browse other questions tagged
.
- Remove From My Forums
-
Question
-
I have installed a brand new instance of Windows 8 on my 64 bit laptop.
When I try to launch the pre-installed Windows Powershell (or the Azure Powershell window) i get an exception 80070002 and all it says is :
«Internal Windows PowerShell error. Loading managed Windows PowerShell failed with error 80070002.»
Does anyone have any idea how to fix this?
All replies
-
Try downloading and installing the latest updates for Windows 8.
Grant Ward, a.k.a. Bigteddy
-
I get updates checked every day. Only option is a Zune update.
-
Hi,
I would like to know after installing all lastest updates for Windows 8, whether the issue still there? If there is anything else we can do for you, please feel free let us know.
Regards,
Yan Li
TechNet Subscriber Support
If you are
TechNet Subscription
user and have any feedback on our support quality, please send your feedback
here.
Yan Li
TechNet Community Support
-
I am actually having this exact same issue. Windows 8 64-bit.
Error when trying to run both 32-bit and 64-bit versions of PowerShell, I have a fully patched Windows 8 environment:
Internal Windows PowerShell error. Loading managed Windows PowerShell failed with error 80070002.
I tried removing / reinstalling Windows PowerShell 2.0 from the Add/Remove Windows Features, no help. I have also tried SFC to repair files.
This is incredibly annoying that I can’t:
- Get a better error
- Manually / forcibly reinstall PowerShell on Windows 8
|| Aaron E
-
Edited by
Wednesday, October 24, 2012 9:49 PM
-
The error message itself means File not found.
Did you try already to run PowerShell As Administrator?
I remember there was a bug in Windows 7 with PowerShell as well, related to a missing registry key. I cannot remember, if it was HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1 or something else — at least it was a simple one.
Best greetings from Germany
Olaf -
Running a command prompt as Admin does not solve the problem. Same error.
However, I just fixed my issue!
While investingating a little bit and comparing my broken machine to a working machine I noticed that my broken machine had a
powershell.exe.config file in it. My working machine had no config file. The contents are:<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v3.5" />
<supportedRuntime version="v3.0" />
<supportedRuntime version="v2.0.50727" />
<supportedRuntime version="v4.0.30319" />
</startup>
</configuration>UGH — Just did some more testing, it appears that installing Windows Azure PowerShell is what breaks this.
Removing this config file entirely seems to resolve my problem.
UPDATE: The «fix» is actually to remove the specific .NET 2.0 and .NET 4.0 version numbers. Doing this fixes both regular Windows PowerShell AND the Windows Azure PowerShell windows.
Update #2 — Well this is annoying, the fixes above work «one time», somehow when I run the Azure PowerShell it RE-ADDS these to the .config file and then breaks itself for the next time it loads.
Update #3 — I have blogged about this and found out what was creating this file:
http://happyfunpartytime.com/2012/10/powershell-internal-windows-powershell-error-loading-managed-windows-powershell-failed-with-error-80070002/
|| Aaron E
-
Proposed as answer by
Aaron E. _
Wednesday, October 24, 2012 11:11 PM -
Unproposed as answer by
Aaron E. _
Thursday, October 25, 2012 3:17 AM -
Proposed as answer by
Aaron E. _
Thursday, October 25, 2012 6:35 AM -
Edited by
Aaron E. _
Thursday, October 25, 2012 6:35 AM
-
Proposed as answer by
I have a Windows 2008 R2 SP1 server with all current windows updates.
I am attempting to run PowerShell but it gives the following error:
Internal Windows PowerShell error. Loading managed Windows PowerShell
failed with error 80070002
It then promptly goes back to the cmd line.
I have run a sfc /scannow
and it has come back clean.
I have tried running powershell -noprofile
asked Dec 21, 2013 at 12:34
I used this script to test all the .NET folders
@echo off
cd C:\Windows\Microsoft.NET\assembly\GAC_MSIL
for /D %%z in (*) do (
echo %%z
rename %%z %%z1
powershell 'powershell works'
rename %%z1 %%z
pause
echo.
)
Out of 236 folders, the only one that gave me error 80070002 was
Microsoft.PowerShell.ConsoleHost
You can repair PowerShell likes this
wusa /extract:. Windows6.1-KB2819745-x64-MultiPkg.msu dism /online /remove-package /packagepath:Windows6.1-KB2819745-x64.cab dism /online /add-package /packagepath:Windows6.1-KB2819745-x64.cab
answered Nov 18, 2014 at 3:55
You must log in to answer this question.
Not the answer you’re looking for? Browse other questions tagged
.
Not the answer you’re looking for? Browse other questions tagged
.
- Ahmir
- Comments Off on How do I fix error code 80070002?
How do I fix error code 80070002?
Updated October 2023: Stop error messages and fix your computer problem with this tool. Get it now at this link
- Download and install the software.
- It will scan your computer for problems.
- The tool will then fix the issues that were found.
Windows PowerShell internal error. Loading managed Windows PowerShell failed with error 80070002. After that, it immediately returns to the current command prompt. I ran the specific sfc /scannow and it came up clean. Uninstalling and reinstalling Windows Framework Management 4.0 (KB2819745) fixed some issues.
The error occurs when the instant client is not a member of the AADSyncAdmins group on the adjacent computer, or if Azure Active Directory Sync Services is currently installed. How to fix this error 80070005? Recently, one of our potential clients contacted us with error 80070005.
PowerShell Core (debug build) gives more errors + assertion message but dies: Full error fix [] Full error fix path [] PowerShell Copyright (C) Microsoft Corporation.
How can I update this action plan Windows Error 0x80070002?
- Stop updating the Windows service. Temporarily
- Delete the update files in the software distribution folder.
- Restart the Windows Update service.
- Check, Sorry, updates are installed here.
- Run the Application Troubleshooter.
- Run. Perform a clean boot.
- Step 1 : Install PC Repair & Optimizer Tool (Windows 10, 8, 7, XP, Vista).
- Step 2 : Click Start Scan to find out what issues are causing PC problems.
- Step 3 : Click on Repair All to correct all issues.
< li>Use or disable the System Update Readiness Tool.
< /ol>
What do I do if I get error code 80070002?
With just one click, you can quickly clone, update, migrate, or migrate your system. Indeed, most Windows users often encounter the following type of situation: “An error occurred while checking for new updates to support your computer. Error encountered: 80070002, l ‘city code Windows Update encountered an unknown problem’.
Updated: October 2023
Are you grappling with persistent PC problems? We have a solution for you. Introducing our all-in-one Windows utility software designed to diagnose and address various computer issues. This software not only helps you rectify existing problems but also safeguards your system from potential threats such as malware and hardware failures, while significantly enhancing the overall performance of your device.
Como corrigir o erro 80070002?
Windows 10: Error 0x80070002 Como Resolver??
What kind of error occurred in class failed to load either due to not being on the classpath or due to failure in static initialization Noclassdeffound error stackoverflow error out of memory error file found error?
NoClassDefFoundError – This exception means that a particular class cannot be loaded, either because it is not on someone’s classpath or because the old-fashioned initialization failed. OutOfMemoryError – This exception is due to the JVM running out of available memory while checking multiple objects.
RECOMMENATION: Click here for help with Windows errors.
I’m Ahmir, a freelance writer and editor who specializes in technology and business. My work has been featured on many of the most popular tech blogs and websites for more than 10 years. Efficient-soft.com is where I regularly contribute to my writings about the latest tech trends. Apart from my writing, I am also a certified project manager professional (PMP).