Endless Corrupt Files and Troubleshooting.

Anonymous
2015-06-03T14:16:05+00:00

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.

0 comments

100 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. 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

    Was this answer helpful?

    0 comments
  2. 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.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-06-07T23:30:00+00:00

    The Command Prompt still works fine.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-06-07T22:34:24+00:00

    Powershell loads normally then a message comes on and it disappears.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2015-06-07T20:34:49+00:00

    No.  I tried to access powershell from command prompt.  I got this message.  "Windows Powershell terminated with the following error; Could not load file or assembly or one of it's dependencies.  The system cannot find the file specified.  'System Management. Automation, version=3.0.0.0 culture=neutral

    Publickey Token=31bf3856ad364e35'

    Was this answer helpful?

    0 comments