Windows 11 Update 22H2 Failure and Problems

Hi Greg

Many thanks for the reply. Sorry but I only just saw it. However, I am going to follow your suggestions and will reply (probably by editing this response, if possible) with any outcomes.

The help is much appreciated.

Regards.

Hi Greg.
I am replying to you because the problems I am having began as above so it seems sensible to update and follow from there. SO. this is what has happened...

1. My HP Laptop advised me of a Windows 11 update 22H2 awaiting installation but the install failed (as already described).
2. I read your suggestions. It seemed the best option was to not install any update until required to, so I waited.
3. After a few days, the laptop blue-screened (first tie ever for this laptop). The only solution that I could find was to reinstall Widows in Repair Mode, so I did that. I retained my own files.
4. After a couple of days, the laptop ground to a halt. Problem was 100% disk usage. The internet suggested various solutions: I disabled sysmain, I disabled search indexing, I disabled all the apps in Startup that were unnecessary (apps I'd installed, if they appeared in Startup). The laptop worked fine.
5. After a few days, the laptop would not boot. It displayed the HP logo but never went beyond that in the boot cycle, I entered repair ode (switched off 3 times). I tried to automatically repair startup but the repair made tried and said it couldn't repair it.
6. I restarted repair mode and selected to revert to a previous working restore point. The restore point successfully installed. Reboot worked and I had a visible desktop. It then took a long time for everything to continue loading. I opened the Task manager. there was 100% CPU usage. I waited and after about 5-10 minutes CPU usage returned normal but Disk Usage hit 100% and stayed there. It never lowered. I tried opening the Start menu so as to disable sysmain and follow other suggestions to fi the disk usage. However, while the start window would open, the 100% disk usage prevented me typing anything into the start window. I tried closing processes in the Task Manager but none would close, the close button was just ignored. I went back into repair mode. I selected Safe Boot. It took a long time to get to it but when it eventually tied to safe boot (after I clicked on the option number for Safe Boot), the laptop reported that a problem had been encountered and it would have to restart automatically.
7. The laptop restarted in Automatic Repair ode and I' staring at a window that has the HP logo and the words "Automatic Repair Mode" but it's been stuck on that for at least 20 minutes and obviously isn't getting anywhere.
8. Additional attempts at Safe Boot simply cause a failure and forced Restart. The automatic repair remains accessible.
9. Startup Repair cannot repair the system.
10. It won't Reset either from the internet or locally.

I have no idea what ore I can try short of reinstalling Windows AGAIN (requiring me to reinstall all y apps again!!!)

I am having the same issue after installing 22h2 last night.

I also was unable to update to update the 22H2 on my HP Spectre 360 from Windows 11. Reading posts on HP forums, it seems others are having similar issues attempting unsuccessfully to update.

In my case, it corrupted my SSD. All I had left was the X: drive and unable to boot. Ended up taking to a computer service shop where they also were unable to recover or access anything on the drive. Had to replace the drive and reinstalling windows/apps.

Not sure where issue is - HP or Microsoft but definitely not looking to try this update anytime soon. I have never had issues with updates in the past but this one is one to stay away from.

Wish I could get rid of the constant update reminder icon in the tray because this isn't going to happen.

Has anyone received an answer on what is wrong with 22H2 update? 4 computers, each tried to download 3+ times...... it never happens.

Thx.

I had the same problem on my Pavilion laptop.

As it was still under warranty (only 6 months old) and after 2 weeks working with tech support, I had to send it back to HP who formatted the hard drive and reinstalled Windows.

Now, after a couple of weeks, the notification to install 22H2 reappeared. I thought that was what HP had installed since the notification wasn't there when I first got it back.

I like to keep the system up to date but am extremely hesitant about installing 22H2.

If anyone has had this problem and then been able to successfully install 22H2 on a subsequent attempt, it would be good to hear your experience.

same thing here. says i'm totally up to date but that windows 11 version 22H2 is available. now, when i did try to update to this new version a month ago, it crashed my computer and wouldn't start at all and i was panicked. somehow i did a forced hard restart back to the the old version of windows 11 and got my old computer back and its working fine. this is why i don't like doing upgrades to operating systems (OS) and instead prefer to just buy a new computer with the latest thing on it and just use that. and your experience confirms my better judgment to not try to ever install the OS update(s) again. i suggest somehow force hard restarting your computer back to the old version of windows 11. google it as to how. sorry that so many are experiencing all this and good luck!

Appreciate the feedback however I’ve been upgrading OS’s for at least 30 years on various computers since days of DOS including mainframes.

I cannot remember an OS that crashed a HD or SSD during upgrade.

There is something wrong here - just wish someone from HP or Microsoft would take the issue serious enough to develop a fix. MS states they are not aware of any issues but obviously they don’t pay attention to the many posts of people crashing machines trying to apply this update…..

You've been lucky.

I did this for 45 years before retiring. never a problem on the mainframes and large-scale servers.

For PC's we had enough problems with OS upgrades that it was decided to set up a dedicated lab to test just OS upgrades before rolling them out to the application test lab.

We were big enough to get Microsoft to work with us when we reported problems, but they don't seem to pay much attention to individual issues like this.

I actually think this problem is related to Bit Locker on the drive. Disabling this in the BIOS let me get further into the recovery process by entering the key manually, but still never far enough to get the machine back.