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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2015-06-05T18:41:04+00:00

    Microsoft Fix-it and Windows 8.1 Troubleshooter keep fixing different errors.  Is there much point to using them several times?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-06-07T15:09:10+00:00

    I was installing some programs in Safe Mode.  When I returned to normal mode, Powershell had a short message I couldn't read as The Powershell Screen only opens up for a split second.  It continues to do so.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-06-07T15:55:33+00:00

    Please run a system file check (SFC) & DISM (if necessary) if you are on win 8 or higher

    All instructions are in our Wiki article below...

    Should you have any questions please ask us.

    System file check (SFC) Scan and Repair System Files

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-06-07T19:30:07+00:00

     Powershell Screen only opens up for a split second.           

    Is there a Taskbar button for it still after that?  If so, it may only be off screen somewhere, waiting to be moved back into view, e.g. with  Alt-Space M CursorRight.   FWIW I always have to do this with my Surface RT.

    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