Powershell loads normally then a message comes on and it disappears.
Endless Corrupt Files and Troubleshooting.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
Yesterday my SFC /Scannow command, run from Powershell Admin found corrupt files it was unable to fix. I expected The Dism /Online /Cleanup-Image /Restorehealth command to take care of it. Instead it reported "error 0x800f0906" and said it lacked the files to repair the problem.
I looked up error 0x800f0906 in a Dism command. It suggested a repair that started and stopped services, a
net stop wuauserv
cd %systemroot%\SoftwareDistribution
ren Download Download.old
net start wuauserv
net stop bits
net start bits
net stop cryptsvc
cd %systemroot%\system32
ren catroot2 catroot2old
net start cryptsvc
It also suggested Windows Update was malfunctioning and that I should fix it from The Troubleshooting screen. I did, and SFC /Scannow came up clean and Dism /Online /Cleanup-Image /RestoreHealth reported error code 0x800f081f instead.
I then used The Dism /Online /Cleanup-Image /StartComponentCleanup and The Dism /Online /Cleanup-Image /StartComponentCleanup /ResetBase Commands. I then used The Dism /Online /Cleanup-Image /ScanHealth Command and it reported "No component store corruption detected." I thought I was in the clear, but Dism /Online /Cleanup-Image /RestoreHealth keeps reporting it found and repaired files and The Troubleshooter keeps reporting it's fixed problems in Windows Update. Probably not the biggest deal in the Windows world but a little unsettling.
Windows for home | Previous Windows versions | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
100 answers
Sort by: Oldest
-
Anonymous
2015-06-07T22:34:24+00:00 -
Anonymous
2015-06-07T23:30:00+00:00 The Command Prompt still works fine.
-
Anonymous
2015-06-08T12:50:50+00:00 The problem mainly started when I uninstalled AVG Tune-Up Utilities 2014. I have several errors recorded if they would be helpful.
-
Anonymous
2015-06-08T15:51:43+00:00 The Command Prompt still works fine.
So you should try starting Powershell from it. E.g. in an elevated cmd window you would expect to see it converted into an elevated Powershell. What happens? E.g. does the whole thing then go away?
Another approach along the same tack but with potentially more control and better diagnostics would be to use ProcExp to start it. E.g. ProcExp's has two choices of Run as...
In fact, ProcExp's Search tool (Ctrl-f) for System.Man is showing me that other processes besides Powershell would want to load various instances of System.Management.ni.dll from %windir%\assembly\NativeImages_v4.0.30319_64. One of them is mmc.exe which I guess must be Hyper-V Manager. Vmconnect.exe is another which would be related to that.
Oh. In fact, it is probably System.Management.Automation.ni.dll that you are missing. Only Powershell and its ISE are loading that.
FWIW I always start ISE from PowerShell but I'm not sure that I need to. So you could try starting it independently instead.
Otherwise, I wonder if those .dll are checked by SFC /scannow? That might repair them or at least give you better clues about what is wrong with them. Ditto for DISM as a potential repair/diagnostic.
Good luck
Robert
-
Anonymous
2015-06-08T21:08:20+00:00 I tried opening Powershell/ISE from Command Prompt. I got the message "Windows Powershell terminated with the following error: Could not load file or assembly 'System.Management.Automation, System.Managment.Automation, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of it's dependencies. The system cannot find the file specified