Cannot upgrade Windows 10 from 1803 (Build 17134.1130) to 1909

Hello!

As this is my forst post, I drafted a long, eloquent, and light-hearted post documenting my woes and my journey thus far.

Then a cleanup needed Firefox to close, and I forgot about this tab. And it closed. Many swears occured.

So, in brief:

Over the years I have successfuly upgraded from 95 to 98SE, then my next PC went from Vista, 7, then transplanted into my new build where in blossomed into the beautiful Windows 10 butterfly it is today. Without meaning to brag, I have never had an issue with any Service Pack or feature update.

Then Windows 10 1903 (and now 1909) arrived.

It fails, every damn time, and nothing makes sense anymore. Not even the world.

I have tried everything my trusty Google-fu has mustered - the usual trickery - including (but not limited to, as memory needs prodding from time to time):

• Installing via Windows Update;
• Installing via Media Creation Tool (whilst online);
• Installing via Media Creation Tool (whilst offline);
• Clearing SoftwareDistribution;
• The usual DISM/SFC commands;
• Un-setting 'Read Only' on $WINDOWS.~BT just before proceeding to the first full-screen 'Installing Windows 10' screen;
• Removing problematic oemxx.inf's;
• Removing old devices from Device manager;
• Updating drivers;
• Clean boot;
• ..probably more besides, it's all a blur now...

Nothing works. Error codes seem different every time. Logs seem to mention BitLocker - I don't even have BitLocker..!

I do not want to do a clean install - I don't believe for a moment that my installation is so muffed-up that it would be the only option. I have no other issues with my OS besides this, it's a well-oiled machine that has been kept well and crapware-free since it's inception.

So please, I beg of you, please help me. I need your patience and in return will match it and provide any details you need in order to hold my hand (platonically, of course) through this ordeal. I'm at my utter wits end. Plus I need Explorer Dark Mode.

SetupDiag logs from today's 1909 attempt are attached for your viewing pleasure.

Thank you, in advance.. :)

- - - Updated - - -

Apologies, I should have mentioned (and did in my first draft) that the furthest I get to every time, is 100%/'Your PC will restart' on the first full blue screen stage (i.e. doesn't even reboot once) - then a 'Windows 10 installation has failed' dialog.

Hi,
Open command prompt as administrator and type sfc /verifyonly or sfc /scannow and see what it shows.

Thanks for the replies so far :)

ThrashZone said:

Hi,
Open command prompt as administrator and type sfc /verifyonly or sfc /scannow and see what it shows.

Microsoft Windows [Version 10.0.17134.1130]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

dalchina said:

Hi, please note that upgrade failures may be next to impossible to resolve.

Noted you have run setupdiag.exe...

and upload a copy of setuperr.log
https://support.microsoft.com/en-us/...sion-of-window

Please post a screenshot of your partitions using a 3rd party partition manager - not disk management- making sure all text is visible.

How much free space do you have on C: ?

Have you tried upgrading by downloading an iso (use MS media creation tool) and upgrading using that- choosing not to accept updates if you get as far as that?

Do you have any other disks in the PC that include a Windows installation or leftovers thereof?

There is much more data that may be collected- that's just for starters...

Interestingly there is no result searching for the error number reported:
0x8007023E - 0x50016

I totally understand, however I'm willing to jump through hoops and try anything to avoid a clean reinstall.

Sorry about that - I've attached setuperr.log now. Partitions screenshot also attached (partitions.png).

Free space on C: is currently approx. 20.5GB.

No other disks have any Windows installation remnants - they were cleared long ago to maximise free space.

Also yes - I have tried creating a 1909 iso with the MCT and unplugging from the internet - and just as a safety net I chose not to uinstall updates. That attempt got me to 30% on the blue screen, and the installer quit without error. I don't have those logs, but it wasn't recent and given then outcome compared to other attempts are a bit of a step backward - the logs I have attached from today are the furthest I get.

- - - Updated - - -

dalchina said:

- This is too small. Bear in mind Windows.old will be created - that's about the same as your existing Windows. + you need working space of course.

Could this be the cause? How much is needed? I've freed up space to pass the free space check and elected another drive for it to use during install..?

dalchina said:

It's one thing, but your setuperr.log points to this
FIX: Windows 10 October 2018 v1809 Update Installation Failed Error 0x800F081F-0x20003 (Solved) • Repair Windows™

as at least one possibility.

You can save disk space by downloading the iso separately and storing it on another drive, then mounting the iso and running setup.exe when logged in.

This is also convenient for reattempts.

I'm also unsure that your Recovery partition is functional. Please report the result of running this:


Regarding the reports at the start of your setuperr.log, please see
https://answers.microsoft.com/en-us/...7-3cad1b467ead
and follow that.

I've followed the steps at RepairWin.

I also have the iso on a separate drive.

Microsoft Windows [Version 10.0.17134.1130]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

Windows RE status: Enabled
Windows RE location: \\?\GLOBALROOT\device\harddisk1\partition4\Recovery\WindowsRE
Boot Configuration Data (BCD) identifier: 10aa5216-52d6-11e8-b6d6-d70f5706dcdb
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0

REAGENTC.EXE: Operation Successful.

I'll follow the steps on the MS link and attempt the update once more, and report back.

Thank you :)

There are log collectors used in another forum room.
Please run each V2 and DM and upload results into this thread:
BSOD - Posting Instructions

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
10) wmic recoveros get autoreboot
11) wmic recoveros get DebugInfoType
12) bcdedit /enum {badmemory}

13) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

14) Make sure that there is no over clocking while troubleshooting

15) List and uninstall all non-Microsoft antivirus software
(This includes always on and manual software.)
(This includes running the applicable antivirus uninstall tools for any AV that could have been incompletely uninstalled)

16) List and uninstall all non-Microsoft firewall software

17) List all Microsoft and non-Microsoft drive encryption software.
Uninstall all non-Microsoft disk encryption software

############################
# APPRAISER SCRIPT v0.92 #
############################

C:\$WINDOWS.~BT\Sources\Panther - OK!
Found *APPRAISER_HumanReadable.xml
@ C:\$WINDOWS.~BT\Sources\Panther\ZHdLScmLVUOyFFd9.8.10.0.0_APPRAISER_HumanReadable.xml C:\$WINDOWS.~BT\Sources\Panther\ZHdLScmLVUOyFFd9.8.4.0.0_APPRAISER_HumanReadable.xml C:\$WINDOWS.~BT\Sources\Panther\ZHdLScmLVUOyFFd9.8.8.0.0_APPRAISER_HumanReadable.xml - OK!
No Values Found for DT_ANY_FMC_BlockingApplication.*Value="True"!

Press ENTER to Close:

- - - Updated - - -

zbook said:

There are log collectors used in another forum room.
Please run each V2 and DM and upload results into this thread:
BSOD - Posting Instructions

1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
10) wmic recoveros get autoreboot
11) wmic recoveros get DebugInfoType
12) bcdedit /enum {badmemory}

13) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

14) Make sure that there is no over clocking while troubleshooting

15) List and uninstall all non-Microsoft antivirus software
(This includes always on and manual software.)
(This includes running the applicable antivirus uninstall tools for any AV that could have been incompletely uninstalled)

16) List and uninstall all non-Microsoft firewall software

17) List all Microsoft and non-Microsoft drive encryption software.
Uninstall all non-Microsoft disk encryption software

Done steps 1 to 13. Step 4 failed - DISM.log attached.
Step 14 - I don't dare to OC..! :)
Step 15 - n/a
Step 16 - n/a
Step 17 - n/a

V2 log attached (LIQUIDBORN-PC-(2020-01-07_22-15-46).zip)
DM runs, says the archive is outputted to Desktop, but there's nothing there..?

Steps 1 to 13 output:

Microsoft Windows [Version 10.0.17134.1130]
(c) 2018 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.1130

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17134.1

Image Version: 10.0.17134.1130

[==========================100.0%==========================]
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

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.
Volume label is OS.

Stage 1: Examining basic file system structure ...
830720 file records processed.
File verification completed.
28470 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
30633 reparse records processed.
988576 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
30633 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
78929 data files processed.
CHKDSK is verifying Usn Journal...
35002976 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

233734651 KB total disk space.
214899296 KB in 371285 files.
241332 KB in 78930 indexes.
0 KB in bad sectors.
969451 KB in use by the system.
65536 KB occupied by the log file.
17624572 KB available on disk.

4096 bytes in each allocation unit.
58433662 total allocation units on disk.
4406143 allocation units available on disk.

C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\LIQUIDBORN-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk1\\Partition3"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\LIQUIDBORN-PC\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk1\\Partition3"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
FALSE


C:\WINDOWS\system32>wmic recoveros get DebugInfoType
DebugInfoType
7


C:\WINDOWS\system32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier {badmemory}
badmemoryaccess Yes

- - - Updated - - -

I've held off running the update again until the DISM issue is looked at :) just in case.