Win 10: Corrupt Components

No problem.

On the Device manager right click the "Generic Bluetooth Adapter" and force Update Driver it should update to a more specific one.
 
I'm getting "The system cannot read from the specified device." from device manager as well as from the manually downladed INF file. Windows Update also found the driver missing and gives me error code 0x8007001e.
Also tried dism and sfc. No change there. Is the Bluetooth adapter related to their errors? Since I'm not using it we could also switch it off.
 
Hi,

Found the replacement for the corrupted files lets replace them...


SFCFix Script

!!! WARNING !!! The following fix is only relevant for this system and no other, applying this fix on another computer will not work and most likely will cause problems...
  • Download SFCFix.exe (by Niemiro) and save it to the Desktop
  • Download the file SFCFIX.ZIP, attached below, and save this to your Desktop
  • On your Desktop, make sure you have the two files:
    myjIXnC.png
    SFCFix.exe and
    sfpcJCen14An3ndjNGCI7mByhjHJud.png
    SFCFIX.zip
  • Drag the file SFCFIX.zip onto the file SFCFix.exe and release it
  • The SFCFix tool will process the script
  • Upon completion, a log file SFCFix.txt should be created on your Desktop
  • Open the SFCFix.txt log and copy & paste the contents to your post
 

Attachments

Hi,
sorry for the delay. I was running a tool that checks for broken sectors and it indeed found one, but it needed 29h for it :/
Your zip produced:
Code: 
SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-06-25 05:44:57.875
Microsoft Windows 10 Build 16299 - amd64
Using .zip script file at C:\Users\gs\Downloads\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bth.inf
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bthenum.sys
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bthmini.sys
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bthport.sys
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bthusb.sys

Failed to backup file C:\WINDOWS\WinSxS\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bth.inf with error code 0x570.

Successfully copied file C:\Users\gs\AppData\Local\niemiro\Archive\Winsxs\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bth.inf to C:\WINDOWS\WinSxS\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bth.inf.
The file \\?\C:\WINDOWS\WinSxS\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bthenum.sys is in use and must be replaced over a reboot.
Successfully copied file C:\Users\gs\AppData\Local\niemiro\Archive\Winsxs\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bthmini.sys to C:\WINDOWS\WinSxS\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bthmini.sys.
The file \\?\C:\WINDOWS\WinSxS\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bthport.sys is in use and must be replaced over a reboot.
The file \\?\C:\WINDOWS\WinSxS\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bthusb.sys is in use and must be replaced over a reboot.

Successfully pended file for replace over reboot: \\?\C:\WINDOWS\WinSxS\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bthenum.sys
Successfully pended file for replace over reboot: \\?\C:\WINDOWS\WinSxS\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bthport.sys
Successfully pended file for replace over reboot: \\?\C:\WINDOWS\WinSxS\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bthusb.sys

Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bth.inf
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bth.inf
Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bthmini.sys
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bthmini.sys
PowerCopy:: directive completed successfully.




Reboot:: directive completed successfully.




PostRebootCorruptionDetection::
No hash verification failures detected.
PostRebootCorruptionDetection:: directive completed successfully.




PostRebootRestorePermissions::
Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bthenum.sys
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bthenum.sys
Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bthport.sys
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bthport.sys
Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bthusb.sys
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_dual_bth.inf_31bf3856ad364e35_10.0.16299.64_none_7d34aa5bf072cd3a\bthusb.sys
PostRebootRestorePermissions:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 12 datablocks.
Finish time: 2018-06-25 17:38:32.360
----------------------EOF-----------------------
The Bluetooth Driver installed now :)
Best Regards
Zifix
 
Hi,

That is good. The error affected the Microsoft Bluetooth driver that supports the installation of the specific Bluetooth driver.

Run SFC /scannow again and collect the CBS.log if it fails or that it reports corrupted files that coudn't fix.
 
Here you go.
Code: 
2018-06-25 17:46:06, Info                  CSI    000006ef Hashes for file member [l:10]'UsbNcm.inf' do not match.
 Expected: {l:32 b:4bdef634c190d9f72d5816b300565deab15bff6a260f27af883347fd1cd31683}.
 Actual: {l:32 b:7bd99fe884b744dbc72b6216870c79f713c4fe3b049acd92e82d6e5533d80354}.
2018-06-25 17:46:06, Info                  CSI    000006f0 [SR] Cannot repair member file [l:10]'UsbNcm.inf' of dual_usbncm.inf, version 10.0.16299.15, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, type [l:14]'dualModeDriver' in the store, hash mismatch
2018-06-25 17:46:06, Error                 CSI    000006f1 (F) STATUS_FILE_CORRUPT_ERROR #3289327# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysReadFile(h = 88c ('\Device\HarddiskVolume6\Windows\WinSxS\amd64_dual_vhdmp.inf_31bf3856ad364e35_10.0.16299.98_none_b19c179e6ad1b206\vhdmp.sys'), evt = 0, apcr = NULL, apcc = NULL, iosb = @0x317287b840, data = {l:0 b:}, byteoffset = 0, key = (null))
[gle=0xd0000102]
2018-06-25 17:46:06, Error                 CSI    000006f2@2018/6/25:15:46:06.128 (F) onecore\base\wcp\sil\merged\ntu\ntsystem.cpp(3480): Error STATUS_FILE_CORRUPT_ERROR originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysReadFile expression: (null)
[gle=0x80004005]
I was trying it earlier hence the timestamp.
 
Hi,

I need the full log.

Please do like you did before, copy cbs.log to the Desktop, zip it and upload or share the zip file.
 
Another fix.


SFCFix Script

!!! WARNING !!! The following fix is only relevant for this system and no other, applying this fix on another computer will not work and most likely will cause problems...
  • Download SFCFix.exe (by Niemiro) and save it to the Desktop
  • Download the file SFCFIX.ZIP, attached below, and save this to your Desktop
  • On your Desktop, make sure you have the two files:
    myjIXnC.png
    SFCFix.exe and
    sfpcJCen14An3ndjNGCI7mByhjHJud.png
    SFCFIX.zip
  • Drag the file SFCFIX.zip onto the file SFCFix.exe and release it
  • The SFCFix tool will process the script
  • Upon completion, a log file SFCFix.txt should be created on your Desktop
  • Open the SFCFix.txt log and copy & paste the contents to your post
 

Attachments

We improved ourselves from 7 to 12 %. Yay :P
Is the place where you are getting the files from available to me? I'm pretty sure I could do some of them on my own :)
 

Attachments

Hum 7 to 12% its a slow improvement...

It depends on the files versions, some from the install DVD others we have to identify the Windows Update that installed them, download the update and extract to source the files...
 

Attachments

15% ;)
How would I go verify the hash of such a file? Right not the log doesn't seem to contain the expected hash of bootmgr.efi.mui. So if I find the file in my ISO how can I know it's the right version etc.?
 

Attachments

Hi,

Depending on the errors the log will show the actual hash and the expected one.

Usually if the file is sourced from the correct folder amd64_microsoft-windows-b..nager-efi.resources_31bf3856ad364e35_10.0.16299.19_fr-fr_441bb4024d2ad964 it should match the hash but there are special cases where this doesn't happen.

Can you run dism to see if it can helps fixing more files.

Dism /Online /Cleanup-Image /RestoreHealth
 
Sorry, but DISM still refuses to use the temporary directory it just created :(
 
Ok, lets continue with SFC and see if Windows gets to a point where you can upgrade to the latest version...

Another fix
 

Attachments

Sounds like plan. Windows Update keeps trying to install a feature update. Is that what you are referring to? I will also keep trying dism regularly, if that doesn't hurt.
I uploaded the new CBS.log.
 

Attachments

zifix said:
Sounds like plan. Windows Update keeps trying to install a feature update. Is that what you are referring to?
Click to expand...

Yes.

zifix said:
I will also keep trying dism regularly, if that doesn't hurt. I uploaded the new CBS.log.
Click to expand...

I don't think dism will work because of the errors... For now run only SFC until it finish with 100% and without reporting errors.
 

Attachments

You must log in or register to reply here.
Back
Top