Windows 10 Pro stuck on Version 1909

donnell500 · Jan 8, 2022

Hello,

My Windows 10 Pro system is stuck on Version 1909 (OS Build 18363.1556) and will not upgrade. I already tried repairing the file system and an in-place upgrade without success (get bluescreen half way through and changes are reversed).

Also tried most of the tips mentioned at

FIX DISM Source Files Could not be Found Windows 10/8 - wintips.org - Windows Tips & How-tos.

Running 'SFCFix.exe' either results in 'SFCFix Has Crashed' or it not finding any issues.

Running the following commands in order results in the attached dcim and CBS log files.

sfc /scannow ( Windows Resource Protection found corrupt files but was unable to fix some of them ... )

DISM /Online /Cleanup-Image /StartComponentCleanup ( The operation completed successfully. )

Dism /Online /Cleanup-Image /RestoreHealth ( Error: 0x800f081f )

Looking through a section of the CBS.log below, I tried reinstalling Windows Update KB4586863 with 'wusa /uninstall /KB:4586863' but always get a message about the update being required and cannot be uninstalled.

Any ideas?

Thanks in advance.

2022-01-08 13:50:32, Info CBS =================================
2022-01-08 13:50:32, Info CBS Checking System Update Readiness.
2022-01-08 13:50:32, Info CBS
2022-01-08 13:50:32, Info CBS (p) CBS Catalog Missing

Package_24_for_KB4586863~31bf3856ad364e35~amd64~~18362.1190.1.0
2022-01-08 13:50:32, Info CBS Repair failed: Missing replacement mum/cat pair.
2022-01-08 13:50:32, Info CBS (p) CSI Payload Corrupt

amd64_microsoft-windows-s..-installers-onecore_31bf3856ad364e35_10.0.18362.1497_none_f952e3fe084ae7a6\NetSetupAI.dll
2022-01-08 13:50:32, Info CBS Repair failed: Missing replacement payload.
2022-01-08 13:50:32, Info CBS (p) CSI Payload Corrupt

x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.1497_none_bad7392f71d18690\dpx.dll
2022-01-08 13:50:32, Info CBS Repair failed: Missing replacement payload.
2022-01-08 13:50:32, Info CBS (p) CSI Payload Corrupt

x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.1430_none_bad1d6eb71d63b1f\dpx.dll
2022-01-08 13:50:32, Info CBS Repair failed: Missing replacement payload.
2022-01-08 13:50:32, Info CBS (p) CSI Payload Corrupt

amd64_microsoft-windows-s..u-education-license_31bf3856ad364e35_10.0.18362.1533_none_024b87f6a25ad4c2\Education-Volume-MAK-1-ul-phn-rtm.xrm-ms
2022-01-08 13:50:32, Info CBS Repair failed: Missing replacement payload.
2022-01-08 13:50:32, Info CBS
2022-01-08 13:50:32, Info CBS Summary:
2022-01-08 13:50:32, Info CBS Operation: Detect and Repair
2022-01-08 13:50:32, Info CBS Operation result: 0x800f081f
2022-01-08 13:50:32, Info CBS Last Successful Step: Remove staged packages completes.
2022-01-08 13:50:32, Info CBS Total Detected Corruption: 5
2022-01-08 13:50:32, Info CBS CBS Manifest Corruption: 1
2022-01-08 13:50:32, Info CBS CBS Metadata Corruption: 0
2022-01-08 13:50:32, Info CBS CSI Manifest Corruption: 0
2022-01-08 13:50:32, Info CBS CSI Metadata Corruption: 0
2022-01-08 13:50:32, Info CBS CSI Payload Corruption: 4
2022-01-08 13:50:32, Info CBS Total Repaired Corruption: 0
2022-01-08 13:50:32, Info CBS CBS Manifest Repaired: 0
2022-01-08 13:50:32, Info CBS CSI Manifest Repaired: 0
2022-01-08 13:50:32, Info CBS CSI Payload Repaired: 0
2022-01-08 13:50:32, Info CBS CSI Store Metadata refreshed: True
2022-01-08 13:50:32, Info CBS Staged Packages:
2022-01-08 13:50:32, Info CBS CBS Staged packages: 0
2022-01-08 13:50:32, Info CBS CBS Staged packages removed: 0

x BlueRobot · Jan 9, 2022

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

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. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.

donnell500 · Jan 9, 2022

Thank you for responding.

Here is the information requested.

Thanks again.

Code:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-01-09 13:36:33.741
Microsoft Windows 10 Build 18363 - amd64
Using .zip script file at C:\Users\admin\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\servicing\Packages
Successfully took permissions for file or folder C:\WINDOWS\servicing\Packages\package_24_for_kb4586863~31bf3856ad364e35~amd64~~18362.1190.1.0.mum

Successfully copied file C:\Users\admin\AppData\Local\niemiro\Archive\Packages\package_24_for_kb4586863~31bf3856ad364e35~amd64~~18362.1190.1.0.cat to C:\WINDOWS\servicing\Packages\package_24_for_kb4586863~31bf3856ad364e35~amd64~~18362.1190.1.0.cat.
Successfully copied file C:\Users\admin\AppData\Local\niemiro\Archive\Packages\package_24_for_kb4586863~31bf3856ad364e35~amd64~~18362.1190.1.0.mum to C:\WINDOWS\servicing\Packages\package_24_for_kb4586863~31bf3856ad364e35~amd64~~18362.1190.1.0.mum.

Successfully restored ownership for C:\WINDOWS\servicing\Packages
Successfully restored permissions on C:\WINDOWS\servicing\Packages
Successfully restored ownership for C:\WINDOWS\servicing\Packages\package_24_for_kb4586863~31bf3856ad364e35~amd64~~18362.1190.1.0.mum
Successfully restored permissions on C:\WINDOWS\servicing\Packages\package_24_for_kb4586863~31bf3856ad364e35~amd64~~18362.1190.1.0.mum
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2022-01-09 13:36:35.771
Script hash: kU1q37VpcGC6x1Sibnk+B5vG8oCWMD0t4w+IDDMIgCQ=
----------------------EOF-----------------------

x BlueRobot · Jan 9, 2022

Thanks, I'll look at sourcing those missing payload files for you.

x BlueRobot · Jan 9, 2022

Same instructions as before please. I'll look at the last payload file, it seems to be part of a cumulative update which I'll need to setup a VM for.

donnell500 · Jan 9, 2022

Thank you. Looking good so far !!!

Just 1 left.

Code:

2022-01-09 17:08:23, Info                  CBS    Checking System Update Readiness.
2022-01-09 17:08:23, Info                  CBS   
2022-01-09 17:08:23, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_microsoft-windows-s..u-education-license_31bf3856ad364e35_10.0.18362.1533_none_024b87f6a25ad4c2\Education-Volume-MAK-1-ul-phn-rtm.xrm-ms
2022-01-09 17:08:23, Info                  CBS    Repair failed: Missing replacement payload.
2022-01-09 17:08:23, Info                  CBS   
2022-01-09 17:08:23, Info                  CBS    Summary:
2022-01-09 17:08:23, Info                  CBS    Operation: Detect and Repair
2022-01-09 17:08:23, Info                  CBS    Operation result: 0x800f081f
2022-01-09 17:08:23, Info                  CBS    Last Successful Step: Remove staged packages completes.
2022-01-09 17:08:23, Info                  CBS    Total Detected Corruption:    1
2022-01-09 17:08:23, Info                  CBS        CBS Manifest Corruption:    0
2022-01-09 17:08:23, Info                  CBS        CBS Metadata Corruption:    0
2022-01-09 17:08:23, Info                  CBS        CSI Manifest Corruption:    0
2022-01-09 17:08:23, Info                  CBS        CSI Metadata Corruption:    0
2022-01-09 17:08:23, Info                  CBS        CSI Payload Corruption:    1
2022-01-09 17:08:23, Info                  CBS    Total Repaired Corruption:    0
2022-01-09 17:08:23, Info                  CBS        CBS Manifest Repaired:    0
2022-01-09 17:08:23, Info                  CBS        CSI Manifest Repaired:    0
2022-01-09 17:08:23, Info                  CBS        CSI Payload Repaired:    0
2022-01-09 17:08:23, Info                  CBS        CSI Store Metadata refreshed:    True
2022-01-09 17:08:23, Info                  CBS    Staged Packages:
2022-01-09 17:08:23, Info                  CBS        CBS Staged packages:    0
2022-01-09 17:08:23, Info                  CBS        CBS Staged packages removed:    0

Code:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-01-09 17:00:14.624
Microsoft Windows 10 Build 18363 - amd64
Using .zip script file at C:\Users\admin\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.1497_none_bad7392f71d18690
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.1430_none_bad1d6eb71d63b1f
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_microsoft-windows-s..-installers-onecore_31bf3856ad364e35_10.0.18362.1497_none_f952e3fe084ae7a6

Successfully copied file C:\Users\admin\AppData\Local\niemiro\Archive\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.1497_none_bad7392f71d18690\dpx.dll to C:\WINDOWS\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.1497_none_bad7392f71d18690\dpx.dll.
Successfully copied file C:\Users\admin\AppData\Local\niemiro\Archive\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.1430_none_bad1d6eb71d63b1f\dpx.dll to C:\WINDOWS\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.1430_none_bad1d6eb71d63b1f\dpx.dll.
Successfully copied file C:\Users\admin\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..-installers-onecore_31bf3856ad364e35_10.0.18362.1497_none_f952e3fe084ae7a6\netsetupai.dll to C:\WINDOWS\WinSxS\amd64_microsoft-windows-s..-installers-onecore_31bf3856ad364e35_10.0.18362.1497_none_f952e3fe084ae7a6\netsetupai.dll.

Successfully restored ownership for C:\WINDOWS\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.1497_none_bad7392f71d18690
Successfully restored permissions on C:\WINDOWS\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.1497_none_bad7392f71d18690
Successfully restored ownership for C:\WINDOWS\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.1430_none_bad1d6eb71d63b1f
Successfully restored permissions on C:\WINDOWS\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.18362.1430_none_bad1d6eb71d63b1f
Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_microsoft-windows-s..-installers-onecore_31bf3856ad364e35_10.0.18362.1497_none_f952e3fe084ae7a6
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_microsoft-windows-s..-installers-onecore_31bf3856ad364e35_10.0.18362.1497_none_f952e3fe084ae7a6
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 5 datablocks.
Finish time: 2022-01-09 17:00:15.096
Script hash: oNHy2EEFexbx4rniLLWMM9pVh6YHOqxzHdEYN0viPkc=
----------------------EOF-----------------------

x BlueRobot · Jan 9, 2022

Here's the final file. Please follow the same instructions as before, however, once it has successfully copied over, then open an elevated command prompt and enter the following command:

Rich (BB code):

sfc /scannow

If there is no integrity violations reported by the command, then please try Windows Update again.

donnell500 · Jan 10, 2022

Thanks for your help so far. No more issues in the CBS.log file. Those fixes allowed me to get the Microsoft Store apps working again and Windows Update now says "You're up to date" but I'm still on Windows 10 Pro Version 1909.

Using the "Windows 10 Update Assistant" or "Media Creator" to reach Version 21H1 still blue-screens with "stop code: KMODE_EXCEPTION_NOT_HANDLED" at around 65% with no additional information.

From what I've read, it could be a driver issue but I don't see any issues in the Device Manager.

x BlueRobot · Jan 10, 2022

Could you please check the following directory?

Rich (BB code):

C:\$WINDOWS.~BT\Sources\Rollback\setupmem.dmp

If there is a dump file present, then please zip it and upload it in your next post.

donnell500 · Jan 10, 2022

Here is a link to the file you requested.

setupmem.zip

The attached screen shot after reversing changes may also be a clue.

Thank again for your assistance.

x BlueRobot · Jan 11, 2022

Rich (BB code):

5: kd> .trap fffff20d`08668860
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000103bd54 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80367f23296 rsp=fffff20d086689f0 rbp=fffff20d08668aa9
 r8=0000000000000001  r9=ffffc387e0e91d40 r10=000000000000005a
r11=000000000103bd54 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!PpmPerfSelectProcessorState+0x1a6:
fffff803`67f23296 f7f1            div     eax,ecx

There appears to have been a divide by zero exception thrown. I'm not sure exactly what has caused it. Could you please run SetupDiag using the instructions below:

Using SetupDiag

To quickly use SetupDiag on your current computer:

Verify that your system meets the requirements described below. If needed, install the .NET framework 4.6.

Download SetupDiag.

If your web browser asks what to do with the file, choose Save. By default, the file will be saved to your Downloads folder. You can also save it to a different location if desired by using Save As.

When SetupDiag has finished downloading, open the folder where you downloaded the file. By default, this folder is the Downloads folder, which is displayed in File Explorer under Quick access in the left navigation pane.

Double-click the SetupDiag file to run it. Click Yesif you are asked to approve running the program.

Double-clicking the file to run it will automatically close the command window when SetupDiag has completed its analysis. If you wish to keep this window open instead, and review the messages that you see, run the program by typing SetupDiag at the command prompt instead of double-clicking it. You will need to change directories to the location of SetupDiag to run it this way.

A command window will open while SetupDiag diagnoses your computer. Wait for this process to finish.

When SetupDiag finishes, two files will be created in the same folder where you double-clicked SetupDiag. One is a configuration file, the other is a log file.

Use Notepad to open the log file: SetupDiagResults.log.

Review the information that is displayed. If a rule was matched, this information can tell you why the computer failed to upgrade, and potentially how to fix the problem. See the Text log sample below.

Source: SetupDiag - Windows Deployment

donnell500 · Jan 11, 2022

Here are the result of running SetupDiag. Thank you.

SetupDiag.zip

x BlueRobot · Jan 12, 2022

Unfortunately, there isn't too much helpful information since the system crashed with the Stop 0x1E bugcheck very early during the upgrade process. Could you please follow these instructions, the log collection tool will collect event logs and other system information such as which drivers are installed, please attach the zip in your next post.

donnell500 · Dec 10, 2022

ISSUE FINALLY RESOLVED ! ! !

After basically giving up almost a year ago, accepting that I will never be able to upgrade my Windows 10 Pro machine past Version 1909, I found the solution.

Any Windows version after 1909 was not compatible with my ASRock P67 Extreme 4 motherboard bios v 1.60.

The solution was to upgrade the bios using the "Instant Flash" option of the current bios (recommended if Windows 10 is the OS). I downloaded the "P67 Extreme4(3.10)ROM.zip" file from the following site (available from other sites too, just not ASRock for some reason)

https://blog.kakaocdn.net/dn/bp0bK2... Extreme4(3.10)ROM.zip?attach=1&knm=tfile.zip

Then followed these 2 extra steps after flashing as recommended by the following thread.

Like the last person, I am yet another person who achieved SUCCESS with

1. Change SATA mode to AHCI in two places. (Both with the top controller and the marvell one)

2. Boot into Safe Mode once first.

Hope this helps someone and special thanks to "BlueRobot" for trying to help me originally.

Windows 10 Pro stuck on Version 1909

donnell500

Member

Attachments

x BlueRobot

Administrator

Attachments

donnell500

Member

Attachments

x BlueRobot

Administrator

x BlueRobot

Administrator

Attachments

donnell500

Member

x BlueRobot

Administrator

Attachments

donnell500

Member

x BlueRobot

Administrator

donnell500

Member

Attachments

x BlueRobot

Administrator

Using SetupDiag

donnell500

Member

x BlueRobot

Administrator

donnell500

Member

Windows 10 Pro stuck on Version 1909

Member

Attachments

Administrator

Attachments

Member

Attachments

Administrator

Administrator

Attachments

Member

Administrator

Attachments

Member

Administrator

Member

Attachments

Administrator

Using SetupDiag​

Member

Administrator

Member

Using SetupDiag