Desparately Trying to Upgrade Windows 10 (stuck on 20H2)

dalchina said:

Sure, you've got a healthy 1st Recovery partition- that's neither here nor there. I'm sure that will turn out to be an irrelevant partition.

Just considering the minor point- your Recovery partition- have you yet tried (as I suggested)
You could try
reagentc /enable
then to check
reagentc /info

- again from an admin command prompt.

As for your upgrade failure, you're back to
- checking integrity (see previous posts)
- setupdiag.exe
- reviewing log files
doing the basics to eliminate things that might interfere.

Feel free to try the MS Update Assistant.

Diagnosing upgrade failure is HARD and time consuming. Few will try to undertake it- or are able to.

Note how a driver problem can cause what you see:
Fix Windows 10 update stuck at 61% (Percent) - Easy ways
- perhaps not that specific driver... look at your log files.

Here's a case where the poster digs deeper: interesting...
Case of upgrade stuck on 62% – DeployWindows

Woohoo! WSUS Offline did its trick again!

I ran that program once more to redownload the update package and this time after installing & rebooting, my Windows has successfully update itself to 22H2 now, oh yea!


Now its is running cumulative updates via Windows Update, somehow these updates are still functional even if major revision update fails. In any case looks like there is still hope for my broken Windows to keep on living. Haha.

I guess I will be relying on this program to keep my system updated whenever there is a major release. At least for now until I'm ready to go Win11.

I will come back to your suggestions above once I'm all up to date and backed up. Thanks dalchina for sticking with my problem for this long. I will come back with the dxdiag log shortly if I can find a way how to upload a log file here.

dalchina said:

Interesting it's so hard to upgrade- I've not seen one that had to resort exclusively to WSUS.

You can upload a log (text) file by zipping it and uploading that as an attachment. There is a tutorial about uploading attachments etc, listing permitted types and sizes.

Here is a log for SetupDiag
SetupDiagResults.zip

And here is my Windows Setup log
setupact.zip

SetupDiag seems to point a DISM error at Error: 0x8007025d. But searching that seems like the cause issue isn't the same as mine and the fixes are quite random.

I gone thru the 2 links you gave me the solutions they gave is what I have already tried so I still don't know where went wrong.

dalchina said:

You've upgraded to 22H2- so what now is failing?

And what is the exact error message on the screen?

What exactly did you do that generated those logs?

You seem to have a mix of build numbers..
HostOSVersion = 10.0.19045
HostOSBuildString = 19041.1.amd64fre.vb_release.191206-1406
TargetOSBuildString = 10.0.19041.1940 (vb_release_svc_prod2.220711-1757)

Umm I tried to manually do an upgrade repair with 22H2 ISO, just to see if its resolved. But nope that still failed at 61% so I did a SetupDiag log which showed the error still remains so even after updating the Windows10 version, the underlying issue that prevented me from updating the normal way is still broken somewhere.

For the other log I used C:\$Windows.~BT\Sources\Panther\setupact.log but while it was obvious to the author of that article where went wrong, I couldn't see where was the fault in mine from the log.

And as for the build I really have no idea whats going on. I don't even know how WSUS did what the others I have tried failed.

dalchina said:

I really don't think you're going to resolve this.

I suggest you have two options.. if it works now, keep using it, but with the expectation it will fail to upgrade.

or

I refer you to post #10 which would give you a sound build and the same working environment as you have now.

Yeah I think so too. But as long as WSUS can keep manually forcing thru the update revisions, then I might as well keep using it, broken as it may be, it still works somewhat. Anyhow I was already resigned myself that this Windows was unfixable when it was still in my lappie but back then the programs & games I used still works so ehh if it wasn't broken in a way I can't use it then...

Thanks to you guys now my Windows is not as broken as it was then and at least now I have away to move it forward. I will see over the weekend if I can manage to wipe the SSD clean, reinstall and get PCTrans to transfer over, but honestly tackling this problem even before I can here was such an exhausting trip.