Error 0x8007000d after October security update

I don't have a prepared Linux USB drive on hand right now, but if you recommend Ubuntu, I'll happily try that with a blank USB.

I'll await your instructions.

Thanks again
 
1. Download Ubuntu (22.04.3 LTS) from the following location: Thank you for downloading Ubuntu Desktop | Ubuntu
2. Create the USB-stick with Rufus (portable): https://github.com/pbatard/rufus/releases/download/v4.3/rufus-4.3p.exe
3. Boot from the USB-stick and select in the GNU Grub menu the option: Ubuntu Safe Graphics.
4. When the install screen appears - select your preferred language and click Try Ubuntu.
5. In the left menu click Files and click on + Other locations to open the system drive, this should be /dev/sda2 like the example below.

Ubuntu.png

5. Navigate to the directory: /dev/sda2/Windows/System32/drivers/en-US and copy this directory to your USB-drive (or another location) as backup.
6. Select the file usbhub.sys.mui and delete it from the above directory.
7. Reboot the system and provide a copy of the en-US directory in a ZIP-file.
 
Hi,

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.
 

Attachments

Hello again,

Oh, I forgot to mention, copying that file in Ubuntu also failed, so I didn't have to manually delete it.

Latest SFCFix log attached.

Thank you
 

Attachments

Last edited:
Hi,

Unfortunately the fix failed! But we have a copy of all the other files from that directory, so we can try to remove the whole dir and rebuild it with a known good copy of usbhub.sys.mui.

Step 1. 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.


Step 2.
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.
 

Attachments

Ok, I didn't bother trying the second step with SFCFix just yet, as Fixlist seems to have failed, even after reboot. Or is the SFCFix still safe to try?

Log attached

Thanks
 

Attachments

Please boot the system from the Ubuntu USB-stick and navigate to: /dev/sda2/Windows/System32/drivers/en-US

1. Which message appears when you try to remove the usbhub.sys.mui file?
2. Which message do you get when you try to remove the en-US directory?
 
1. The file simply doesn't appear in Ubuntu's file explorer.

2. I was able to successfully delete the en-US directory, no problem. No error messages or anything like that.

Am I able to safely boot back into Windows now or remain in Ubuntu?

Thanks again
 
Ok, late reply, I had another intermittent, seemingly random, issue with my PS/2 devices not getting recognized at startup (Code 10 in device manager for one device, the other just simply didn't appear). Wasn't sure if it had anything to do with corrupted files, or not. Anyway, I troubleshooted that myself. It stopped happening after I disabled a memory heavy app at startup, along with some unused devices inside the BIOS, not sure which one exactly did it, but it seems fixed regardless. Maybe a Windows Update changed something, because I don't recall this happening previously?

TDLR: Had another issue, probably unrelated to corrupt files, fixed it.

Back on topic, SFC /scannow and CHKDSK both found issues and corrected them on their first run. However, on their second runs, no issues were found. So I think I'm good to go now.

I know I'm repeating myself, but Thank you so much, Maxstar, much appreciated! Elsewhere, everyone else said to just reinstall Windows, which for a few different reasons I really didn't want to do. So glad I found, this forum, I would have been truly screwed without you guys, lol. Keep up the good work!
 
I spoke too soon. Now I'm having an issue with a single Group Policy setting I set, getting reverted/reset. I'm trying to disable Windows Defender, as it's been causing me issues.

It seems to be random, as far as I can tell. Sometimes it stays set after a reboot, sometimes not. I'm using an admin account, and I've already tried gpupdate /force, same result, gets randomly reset after some reboots.

In my frustration, I also tried disabling it via the registry via a number of different registry settings I found listed online. However, none seem to actually work to disable the "antimalware service executable", only the group policy setting. Could that be conflicting? Or could it be related to corruption?

Thanks
 
Ok, I just noticed the policy revert/reset multiple times without even a restart today. Latest CBS attached.

Thank you
 

Attachments

Hi,

The latest CBS shows no errors, so this looks good. However, forcibly disabling Windows Defender does have consequences and may cause other issues.

If you have installed another security program rather than Windows Defender, it will disable the main protection level. But Defender will be active in the background to protect your system, so it is not recommended to use tweaks to bypass this.
 
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