[SOLVED] windows 7 sfc /scannow cant repair

P

Pod Karacz

Member
Joined
Dec 11, 2016
Posts
5
Hi,

I ran sfc /scannow and it cant repair then i used sfcfix and it does not find anything what to do next?
 
here is my cbs file i spammed sfc /scannow a bit becouse i run sfc /scannow it says it fixed some then i run it again it says it cant fix and story happens in circle.

2019-07-08 16:31:07, Info CSI 00001367 [SR] Verify complete
2019-07-08 16:31:07, Info CSI 00001368 [SR] Repairing 1 components
2019-07-08 16:31:07, Info CSI 00001369 [SR] Beginning Verify and Repair transaction
2019-07-08 16:31:07, Info CSI 0000136a Hashes for file member \??\C:\Windows\system32\drivers\en-US\usbhub.sys.mui do not match actual file [l:28{14}]"usbhub.sys.mui" :
Found: {l:32 b:vYkBXtG1oCmsNP1esG4J3ULGtVN29TvzWckQzoIszP8=} Expected: {l:32 b:P+QMS/aJGY12ZeV7xk99rf2BlNR5Z+xU2AWVKrnIdpo=}
2019-07-08 16:31:07, Info CSI 0000136b [SR] Repairing corrupted file [ml:520{260},l:74{37}]"\??\C:\Windows\system32\drivers\en-US"\[l:28{14}]"usbhub.sys.mui" from store
2019-07-08 16:31:07, Info CSI 0000136c WARNING: File [l:28{14}]"usbhub.sys.mui" in [l:74{37}]"\??\C:\Windows\system32\drivers\en-US" switching ownership
Old: usbport.inf.Resources, Version = 6.1.7601.23403, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
New: usb.inf.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2019-07-08 16:31:07, Info CSI 0000136d Repair results created:
POQ 909 starts:
0: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\d291fdc79935d501f287010098116006._0000000000000000.cdf-ms", Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"
1: Move File: Source = [l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\e2b8fdc79935d501f387010098116006.$$.cdf-ms", Destination = [l:74{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms"
2: Move File: Source = [l:214{107}]"\SystemRoot\WinSxS\Temp\PendingRenames\02e902c89935d501f487010098116006.$$_system32_21f9a9c4a2f8b514.cdf-ms", Destination = [l:126{63}]"\SystemRoot\WinSxS\FileMaps\$$_system32_21f9a9c4a2f8b514.cdf-ms"
3: Move File: Source = [l:230{115}]"\SystemRoot\WinSxS\Temp\PendingRenames\52ac03c89935d501f587010098116006.$$_system32_drivers_dc1b782427b5ee1b.cdf-ms", Destination = [l:142{71}]"\SystemRoot\WinSxS\FileMaps\$$_system32_drivers_dc1b782427b5ee1b.cdf-ms"
4: Move File: Source = [l:242{121}]"\SystemRoot\WinSxS\Temp\PendingRenames\72fa03c89935d501f687010098116006.$$_system32_drivers_en-us_4bb913fc5eb96bcf.cdf-ms", Destination = [l:154{77}]"\SystemRoot\WinSxS\FileMaps\$$_system32_drivers_en-us_4bb913fc5eb96bcf.cdf-ms"
5: Hard Link File: Source = [l:224{112}]"\SystemRoot\WinSxS\amd64_usb.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_851353ad2a152114\usbhub.sys.mui", Destination = [l:104{52}]"\??\C:\Windows\system32\drivers\en-US\usbhub.sys.mui"
 
Hello and welcome!

Due to the precise nature of your corruption, you will receive help from a user named writhziden. He's one of our senior trainees here who's in his final phase of his studies and needs to gain some real world experience in specific areas of Windows Update. This means that he'll be assisting you, but that I will first need to double check and approve his fixes before he posts them to you. If anything this is a good thing for you because it means that you've got at least two of us watching over your thread, but it will unfortunately add a slight delay between each reply. I hope that you understand and can accept the need for us to train up new members in this way in order to carry on doing what we do here, however, if for any reason you object to this setup, I will happily take on your thread myself.

Thank you very much for your understanding. We'll be with you very shortly.
 
Hello, and welcome to Sysnative Forums. There are some oddities in the excerpt of the log you shared, but we will need to see the full log file to see if we can find any additional information to help with our analysis.

Export/Upload CBS log file
  1. On Windows 8 and Windows 10, press the Windows key, type This PC, and press Enter.
    On Windows Vista and Windows 7, click the Start button then click Computer.
  2. Double-click on the C: drive, under the Hard Disk Drives category, and then scroll down to, and double click on the Windows folder.
  3. Find and double click on the Logs folder.
  4. Find and double click on the CBS folder.
  5. Right-click on the CBS Text Document file, and select Copy.
  6. Go back to your Desktop, right-click on it, and select Paste. You should now see a copy of the CBS Text Document file appear on your Desktop called CBS.
  7. Right-click on this new Text Document file, and navigate through Send to, and select Compressed (zipped) folder.
  8. A new file, also called CBS (CBS.zip), but this time with a different icon, will be created on your desktop.
  9. Attach the CBS.zip file.
    Note: If your CBS.zip is larger than about 7MB then you will need to upload your file to a hosting service and provide a link instead. See “What to do if your CBS log file is too large to upload” below.

What to do if your CBS log file is too large to upload
Read More:
 
Im so sorry for wasting ur expensive time guys but after running ( WUACPUFIX ) something like zeffy did to unlock updates on kaby lake i updated my system and now sfc /scannow runs without errors. Thanks for interest and you can close thread becouse once i updated my system with latest updates ( 100~ udpates ) after i unlocked them , error is not showing up anymore.
 
If you are having problems with corruption on kaby lake or higher just keep ur system up to date ( zeffy patch or wuacpufix ) will unlock updates for you !
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top