Windows 10 unresponsive on many bootups, after waking from sleep

Page 2 of 2 FirstFirst 12

  1. Posts : 6
    Windows 10
    Thread Starter
       #11

    Not exactly sure what this means?

    Windows 10 unresponsive on many bootups, after waking from sleep-2015_09_30_00_04_291.png
      My Computer


  2. Posts : 102
    W7
       #12

    Hi It means you still have some corrupt files. I would recommend this tutorial by @Brink
    Then post back here with the results. A in place repair may be needed!
    https://www.tenforums.com/tutorials/2...dows-10-a.html
      My Computer


  3. Posts : 6
    Windows 10
    Thread Starter
       #13

    Got this error when trying the Dism /Online /Cleanup-Image /RestoreHealth.
    Windows 10 unresponsive on many bootups, after waking from sleep-2015_09_30_01_06_181.png

    Here is the text from the SFC:
    Only ones that have something different:

    2015-09-29 21:04:56, Info CSI 00003bd4 [SR] Cannot repair member file [l:96{48}]"MSFT_FileDirectoryConfiguration.Registration.mof" of Microsoft.PowerShell.DSC.CoreConfigurationProvider, Version = 10.0.10240.16384, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2015-09-29 21:04:58, Info CSI 00003cbb [SR] Cannot repair member file [l:96{48}]"MSFT_FileDirectoryConfiguration.Registration.mof" of Microsoft.PowerShell.DSC.CoreConfigurationProvider, Version = 10.0.10240.16384, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2015-09-29 21:04:58, Info CSI 00003cbc [SR] This component was referenced by [l:362{181}]"Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-admin~31bf3856ad364e35~amd64~~10.0.10240.16384.Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-admin-Deployment"
    2015-09-29 21:04:58, Info CSI 00003cbf [SR] Could not reproject corrupted file [ml:166{83},l:164{82}]"\??\C:\Windows\SysWOW64\Configuration\Registration\MSFT_FileDirectoryConfiguration"\[l:96{48}]"MSFT_FileDirectoryConfiguration.Registration.mof"; source file in store is also corrupted
    2015-09-29 21:04:58, Info CSI 00003cd7 [SR] Verify complete

    015-09-29 21:05:53, Info CSI 00004987 [SR] Repairing 1 components
    2015-09-29 21:05:53, Info CSI 00004988 [SR] Beginning Verify and Repair transaction
    2015-09-29 21:05:53, Info CSI 0000498a [SR] Cannot repair member file [l:96{48}]"MSFT_FileDirectoryConfiguration.Registration.mof" of Microsoft.PowerShell.DSC.CoreConfigurationProvider, Version = 10.0.10240.16384, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2015-09-29 21:05:53, Info CSI 0000498d [SR] Cannot repair member file [l:96{48}]"MSFT_FileDirectoryConfiguration.Registration.mof" of Microsoft.PowerShell.DSC.CoreConfigurationProvider, Version = 10.0.10240.16384, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2015-09-29 21:05:53, Info CSI 0000498e [SR] This component was referenced by [l:362{181}]"Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-admin~31bf3856ad364e35~amd64~~10.0.10240.16384.Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-admin-Deployment"
    2015-09-29 21:05:54, Info CSI 00004991 [SR] Could not reproject corrupted file [ml:166{83},l:164{82}]"\??\C:\Windows\SysWOW64\Configuration\Registration\MSFT_FileDirectoryConfiguration"\[l:96{48}]"MSFT_FileDirectoryConfiguration.Registration.mof"; source file in store is also corrupted
    2015-09-29 21:05:54, Info CSI 0000499f [SR] Repair complete
    2015-09-29 21:05:54, Info CSI 000049a0 [SR] Committing transaction
    2015-09-29 21:05:54, Info CSI 000049a5 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
      My Computer


  4. Posts : 102
    W7
       #14

    Looks good! Have you ran sfc again??
    If SFC could not fix something, then run the command again to see if it may be able to the next time. Sometimes it may take running the sfc /scannow command 3 times restarting the PC after each time to completely fix everything that it's able to.
    Last edited by donetao; 29 Sep 2015 at 21:58.
      My Computer


  5. Posts : 6
    Windows 10
    Thread Starter
       #15

    Just an update...Never could get it to act right even after trying multiple things. Contacted the manufacturer for warranty support. They sent me a windows 10 disc so I could do a repair procedure. That seemed to do the trick, haven't had any issues since. Thanks everyone.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 12:26.
Find Us




Windows 10 Forums