Error 0x8007000d after October security update

Mmm, let's try to remove the whole folder.

Start the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool again.

Warning: This script was written specifically for this system. Do not run this script on another system.
  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST.exe and select "Run as administrator".
  • Press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.
 

Attachments

Great, here's the next fix to restore this directory.

Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.

Afterwards run the following command again.
Code:
certutil -hashfile C:\Windows\WinSxS\amd64_usbport.inf.resources_31bf3856ad364e35_10.0.19041.1_en-us_a3fdd12d463484b9\usbhub.sys.mui SHA256
 

Attachments

Looks like everything succeeded this time.

Result:

SHA256 hash of C:\Windows\WinSxS\amd64_usbport.inf.resources_31bf3856ad364e35_10.0.19041.1_en-us_a3fdd12d463484b9\usbhub.sys.mui:
a759151f80ec5cae41fe8e5c07cd251e38d4e7dffaf1de8c2dab06cc1a9445d9
CertUtil: -hashfile command completed successfully.

Thank you
 

Attachments

This looks much better, so please attempt to update and post the result. If it fails attach a new copy of the CBS logs..
 
Awesome, the latest Windows update completed successfully! Much appreciated Maxstar.

That being said, SFC /scannow is still failing at 67% with "Windows Resource Protection could not perform the requested operation.". I assume that means I have more corrupted files. Would I be able to get help with that here, or should I open a new thread?

Thanks again
 
Please post the latest CBS logs, then we can take a look why SFC failed...
 
Last edited:
Rich (BB code):
2023-11-27 10:36:55, Error                 CSI    000001a8 (F) STATUS_FILE_CORRUPT_ERROR #19594197# from CFileInstaller::DoComponentOperation(...)[gle=0xd0000102]
2023-11-27 10:36:55, Error                 CSI    000001a9 (F) STATUS_FILE_CORRUPT_ERROR #19594196# from PrimitiveInstaller::CCoordinator::RepairComponent(Component = usbport.inf.Resources, version 10.0.19041.1, arch amd64, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35})[gle=0xd0000102]

Please run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 
Code:
DISM /online /cleanup-image /RestoreHealth
Result:
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

However, SFC scan result is the same. Logs attached.

Thanks
 

Attachments

Please run the SFC (System File Checker) again with Prosess Monitor running.

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. [Run the System File Checker. SFC /Scannow
3. Stop Process Monitor a minute after it fails. You can simply do this by clicking the square (CTRL +E) on the toolbar as shown below.



4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.
 
Rich (BB code):
9:01:51.2867071 PM    TiWorker.exe    2160    CreateFile    C:\Windows\System32\drivers\en-US\usbhub.sys.mui    FILE CORRUPT    Desired Access: Generic Read, Access System Security, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Open For Backup, Attributes: N, ShareMode: Read, Write, Delete, AllocationSize: n/a, Impersonating: NT AUTHORITY\SYSTEM

Hi,

Here's the next fix to remove another corrupt copy of this file.

Start the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool again.

Warning: This script was written specifically for this system. Do not run this script on another system.
  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST.exe and select "Run as administrator".
  • Press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.
 

Attachments

Start the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool again.

  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST.exe and select "Run as administrator".
  • Press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a ZIP-file called <date>_<time>.zip will appear in the same directory the tool is run from.
  • Post the ZIP File as attachment in your next reply.
 

Attachments

Restart your computer in the Recovery Environment.
  • Press the Windows icon on the keyboard together with the letter I, to get into the Settings.
  • Choose Update and Security.
  • From the menu at the left, choose Recovery.
  • Under the title Advanced startup at the right, choose Restart now.
  • From the window that will appear choose Troubleshoot and then Advanced options.
  • At the next screen, select Troubleshoot and Advanced Options.
  • You will see the following options:
  • Select the Command Prompt and run the following command.
  • Note: replace the driveletter X: with the correct driveletter of the system drive.
    Rich (BB code):
    del /f /q X:\Windows\System32\drivers\en-US\usbhub.sys.mui
 
In recovery CMD, I get "file or directory is corrupted and unreadable". However, after booting back into Windows, I received a notification saying I needed to reboot to repair drive errors (first time I've seen this). I did so, then decided to retry the previous two FixList.txt, however, both failed with identical logs.

Thanks again for the continued assistance
 
Are you able to boot from a Linux ISO to delete the following file outside of Windows?

..\Windows\System32\drivers\en-US\usbhub.sys.mui

Otherwise I will provide some instructions for Ubuntu.
 

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

Back
Top