Upgrading 1809 to 1909 - mysterious problem.

O

Orkhis

Well-known member
Joined
Jan 12, 2020
Posts
74
Hi.

I'm currently stuck trying to upgrade 1809 to 1909. I'm an IT professional by trade, so I've trying basically everything that can be found on Google and Microsoft sites . I've even raised a ticket with MS support, which eventually went to L3 and they refused to work on it any further, saying that my only option is clean install. The scenario is always the same - update finishes preparations, reboots PC and starts "Working on updates" phase. At 0% or sometimes at 1% the process crashes, Windows starts "Undoing changes", reboots again and after login I'm greeted with

0xC19000101 - 0x2000C
The installation failed in the SAFE_OS phase with an error during APPLY_IMAGE operation.


There is 2 really strange things happening

1) Power off reboot during "Safe OS" stage. I can hear fans and HDDs powering down, and then starting up again after several seconds. In other words that doesn't looks like a typical reset or BSOD.
2) There is no crash dump, event logs or anything. SetupDiag sometimes cannot even find a matching error pattern.

This might be a HW issue, but I have disabled or removed everything except my video card (it's Nvidia with latest WHQL drivers, so very-very unlikely is a root cause). All services except MS are disabled. Even run a full check with CHKDSK. Cleaned all legacy drivers, so now only MS, Intel and Nvidia drivers are present. SFC cannot find anything. DISM is showing this, but this came with last cumulative update, so I think it's MS issue, looks like they haven't updated DISM to match it.

Code: 
C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.17763.771
Image Version: 10.0.17763.914
[===========================84.3%================          ]
Error: 0x800f081f
The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

I'm attaching results from SetupDiag. Any ideas what else I can try ?
 

Attachments

I've run SFCFix, which also didn't found any issues

Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-01-18 00:06:53.537
Microsoft Windows 10 Build 17763 - amd64
Not using a script file.




AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.



Failed to generate a complete zip file. Upload aborted.


SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2020-01-18 00:12:18.570
----------------------EOF-----------------------
 
Hi,

Are you installing Windows 10 form a flash drive/DVD or doing an on-line upgrade?

Do you have any printers installed/connected? uninstall the printers and make sure they are disconnected from the computer.

Did you try to upgrade without the machine connected to the internet?
 
Thanks for a reply!

Tried flash (don't have optical drive), online and even custom build image using UUP dump. Same result.

Disconnected everything, including all internal HDDs except this one. Same result.

Haven't tried without internet connection, will give it a try tomorrow. However, I think it shouldn't change anything, as SAFE_OS stage doesn't have networking.
 
Hi,

And the printers? The logs seems to suggest that there are 2 OEM drivers that are blocking the upgrade!

Based on your description it seems that the installer is installing updates...

Orkhis said:
The scenario is always the same - update finishes preparations, reboots PC and starts "Working on updates"...
Click to expand...
 
And the printer as well. Although it's connected by Ethernet via router, so also shouldn't matter. Which drivers are blocking ?
 
Hmm. There is no such store. SetupDiag seems to collect logs from several past attempts, could this be from an earlier attempt before I've radically cleaned up the drivers ?

driver_store.png
 
From the logs
oem82.inf - C:\Windows\System32\DriverStore\FileRepository\prnms009.inf_amd64_80184dcbef6775bc\prnms009.inf
oem83.inf - C:\Windows\System32\DriverStore\FileRepository\prnms001.inf_amd64_f340cb58fcd23202\prnms001.inf
 
Right.

C:\Windows\System32\DriverStore\FileRepository\prnms009.inf_amd64_80184dcbef6775bc\prnms009.inf - this one is "Microsoft Print To PDF"
C:\Windows\System32\DriverStore\FileRepository\prnms001.inf_amd64_f340cb58fcd23202\prnms001.inf - this one is "Microsoft XPS Document Writer v4"

Do you think I should remove those ?
 
Lets try a different way go to Programs and Features / Turn Windows Features on or off and disable both then search for the file compatscancache.dat inside a Panther folder and delete it then try to upgrade.
 
Hi,

Please post the following files:
- $Windows.~bt\Sources\Rollback*.evtx
- $Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log
- $WINDOWS.~BT\Sources\Panther\setuperr.txt
 
Hi,

Thanks for log. Did you run a Diagnostic tool to check the HDD health? some manufactures provide tools to do that others don't.

Some manufacture tools can check and do repairs, there is also a free tool that can check only:

JcJ91sx.png
GSmartControl
Follow the instructions below to test your hard drive health with GSmartControl:

  • Download GSmartControl and save it on your Desktop;
  • Extract the content of the GSmartControl .zip archive and execute gsmartcontrol.exe; To extract you can right-click your mouse on the GSmartControl.zip file and select Extract.
  • Identify your drive in the list, and double-click on it to bring up it's window (usually you'll find your drive by it's size or it's brand name);
  • Go in the Perform Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
  • Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply;
  • Also, go in the Attributes tab and if you have any entries highlighted in red or pink, copy and paste their name in your next reply (or take a screenshot of the GSmartControl window and attach it in your next reply);
    info_failing.png
 
One of the steps that MS engineer did was to run chkdsk fullscan, which din't found any bad sectors. SMART monitoring is enabled in BIOS. Also, the system is completely stable, so it doesn't look like drive is dying. Started extended self-tests, ETA is 5 hours.
 
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