legend911
New member
- Feb 10, 2025
- 2
My ACER NITRO 5 laptop audio stopped working all of a sudden. I uninstalled the audio driver and was unable to reinstall it. I then discovered that Windows Update was unable to install anything as well. I was unable to run SFC /scannow and DISM because of the issue, but the first run of the componentscanner.exe did a fix on a duplicate registry and allowed me to run SFC and DISM.
However, this didn't fix either of my problems. Thankfully, I found somebody thanking you on the Microsoft Forums for your help when nothing else would work. The customer support representative suggested you to their client and you successfully fixed their issue.
I have attached the CBS log zip file and componentscanner text file to this post.
When I try to install the audio driver I get an error 0x000003F1: The configuration registry database is corrupt
Windows update is either getting Install Error - 0x000003F1 or 0x80070103
Windows Update 23H2 successfully downloads and initially installs, but when it asks you to restart to do the rest of the install it fails and removes the whole update...
P.S.
ComponentScanner.exe did say it found issues again in the command prompt window, but the output text file didn't seem to highlight that this time around.
Thanks for all your help!
However, this didn't fix either of my problems. Thankfully, I found somebody thanking you on the Microsoft Forums for your help when nothing else would work. The customer support representative suggested you to their client and you successfully fixed their issue.
I have attached the CBS log zip file and componentscanner text file to this post.
When I try to install the audio driver I get an error 0x000003F1: The configuration registry database is corrupt
Windows update is either getting Install Error - 0x000003F1 or 0x80070103
Windows Update 23H2 successfully downloads and initially installs, but when it asks you to restart to do the rest of the install it fails and removes the whole update...
P.S.
ComponentScanner.exe did say it found issues again in the command prompt window, but the output text file didn't seem to highlight that this time around.
Thanks for all your help!
Attachments
Last edited: