22H2 update prevents windows from loading

The 22H2 update has been trying to run on my computer for quite some time. It would go through, load into windows and then cause a BSOD page fault in non paged area. It would either uninstall the update itself or I'd have to go into the repair tool and manually undo the update. Today it pushed the update again only this time it still returned the same BSOD but it didn't automatically remove the update and I can no longer uninstall the update. Any attempt to load that windows installation results in page fault bsod. Knowing that this bsod is normally related to memory I tried setting my ram to default settings but to no avail. I installed windows on one of my secondary drives but I'd really hate to lose that windows install since it has a lot of things it would take a lot of time to figure out (passwords and so on.) Any help would be appreciated.

I'm not sure what version number of windows it was running before but it was fully up to date prior to 22h2. I ran the bsod log program but as this isn't the affected installation of windows I wasn't sure how much value it would provide. DESKTOP-S11GNHM-(2024-03-21_10-36-49).zip

[QUOTE=dalchina;2617438]If it had been fully up to date then you wouldn't have been offered - which sounds as if you mean an upgrade taking your build to 22H2.

Presumably what you mean is your build was 22H2 (something or other) i.e. 19045.xxxxx and you were offered not but 'a 22H2 update' i.e. a cumulative update of the 22H2 build which you had.

I mean, I had every update until the Febuary 22H2 update, and all updates after. Unfortunately, none of the methods listed in the article helped, the first 3 because I can't get into that windows installation and the last 2 simple fail when I try to run them, returning the following error.

I suspect that the updates it is detecting are in fact not the offending ones based on their date and also when I try to roll back the updates through WinRE it says there are pending update actions.

There're people here more expert than me in this and the last thing you'd need is worsening your Windows install for a bad advice. But I'm sure this piece of advice won't worsen anything: don't overclock the RAM anymore. This is not enough to recover but at least you cut a possible source of corruption. I'm thinking that your overclocked RAM could have corrupted Windows enough to cause this problem. Take into account that updating Windows is stressful for the hardware (for instance my processor here heats up a lot while searching for updates, a bit less while effectively updating).

I like partition backups myself and resorting to them when these or other less serious problems happen (this is the main reason why I cannot give more concrete advice here), but I'm assuming you don't have that resource. Windows still has it's own internal "partial" backups (recovery points) and, unless the real experts say otherwise, I would resort to them. As you cannot boot the install, possibly you can boot the recovery tools, if not from your hard disk, maybe with a recovery drive that you can do from your new Windows install.

This wouldn't be my 1st attempt, but if you get to boot a recovery media and fail with the recovery points, you could open a command prompt and run "RestoreHealth" and sfc /scannow . As I'm not sure how should they work with the Windows install offline, I've done this search can restorehealth and sfc be run offline - Google Search . It has several promising results.

Another possible route is a Windows repair install: installing Windows from a very modern media conserving your data and programs.

Possibly it's time to get an imaging program now and doing a backup, so if any solution fails or it even worsens the install, you can at least return to the current starting point.

paulmememan said:

{QUOTE=dalchina;2617438}If it had been fully up to date then you wouldn't have been offered - which sounds as if you mean an upgrade taking your build to 22H2.

Presumably what you mean is your build was 22H2 (something or other) i.e. 19045.xxxxx and you were offered not but 'a 22H2 update' i.e. a cumulative update of the 22H2 build which you had.

I mean, I had every update until the Febuary 22H2 update, and all updates after. Unfortunately, none of the methods listed in the article helped, the first 3 because I can't get into that windows installation and the last 2 simple fail when I try to run them, returning the following error.

I suspect that the updates it is detecting are in fact not the offending ones based on their date and also when I try to roll back the updates through WinRE it says there are pending update actions.

This page https://techcommunity.microsoft.com/...es/m-p/4023020 is for this situation (uninstalling an LCU that includes a wusa-uninstallable SSU), isn't it?

dalchina said:

I only suggested one of those- that can be used offline i.e. Windows not running.

Ok, as you have a pending (not fully installed) Windows update try first deleting

C:\Windows\SoftwareDistribution

I'm not sure what the implications of the servicing stack error are in this situation.

Please advise if you have attempted to use DISM offline to repair your image.

I'm trying DISM offline now to see if that works. Finding the syntax a little confusing but I think I nearly have it figured out

Please see rule #4


https://www.tenforums.com/misc.php?do=showrules