Win8.1 Update and DISM Failed with Error Codes

szoo

Member
Joined
Sep 18, 2018
Posts
7
Hi, guys, my Windows Update(Win8.1 64bits) stop working a few weeks ago with error code 800703F1.
I already tried to use DISM and SFCFix to solve the problem, but they both end with same error code 1009.
SFCFix screen shot is below, , and log files for CBS, DISM and SFCFix are at Dropbox - log files of CBS DISM and SFCFix.zip
Thank you.
--------- start screen shot ----
Welcome to SFCFix by niemiro and sysnative.com.

Checking for updates . . .
No new update is available at this time.

Processing directive 1 of 1 (AutoAnalysis::)
Checking store directories . . .
Checking CBS.log . . .
Checking CBS.persist.log . . .
Checking CheckSUR.log . . .
Checking CheckSUR.persist.log . . .

Attempting repair . . .
Stage 1
Stage 2
Stage 3

Due to the nature of your corruptions, scan times have been extended by
approximately 15-20 minutes. Please be patient and allow the operation to
complete.


Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]

Error: 1009

The configuration registry database is corrupt.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

--- end screen shot ---------------
 
Hello and welcome!

Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to a file sharing service and just provide the link here.
 
Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try running DISM just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


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 and attach the LogFile.PML file as well as your CBS.log
 
Well, I just downgraded from Win10 a few months age, because the Etron USB 3.0 caused a lot of Watchdog/IRQ/Kernel BSOD on Win10.
 
I don't think the downgrade cause the problem, because I did the downgrade by re-format.
But the HDD maybe need some test, any software recommend to test NVMe SSD ?
 
That is even more concerning. You have reformatted the drive? When did the issues start? Was there a sudden power outage maybe?

You can test the NVME with its manufacturer's tool. I cannot be more precise, because I do not have the info on the NVME.
 
I used the tool from the NVMe's manufacturer to examine the SSD, and report didn't show any error.
About two months before windows update stopped working, My PC had several power outages, Maybe that's the cause ?
 

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

Back
Top