Any ideas why 22598.1 upgrade fails?

I am in the Insiders/Beta program. This is Windows Pro in a Parallels VM on an Intel-based MacBook Pro - I have run Windows 10, then starting last year Windows 11 without issues. The normal update failed 4 times despite closing Windows and Parallels, rebooting, etc. It failed in what I presume was the boot phase, when it would no longer be in Windows itself. Around 20% or so it would roll everything back and then give this error when back in Windows:



So I decided to try the UUDUMP route, and run the update that way. I get this:



Further information, I have 22598.1 running Windows Pro on an Apple M1 Max Pro MacBook Pro without issue - upgrade went perfectly. So I am wondering if something is in conflict with it or how to diagnose/correct the issue. I have posted in Parallel forums with no response yet for anyone.

Any ideas? Thanks!

Open Command Prompt with administrative privileges and execute below commands one at a time to repair system files.


Uninstall third-party antivirus programs if you are using Windows Defender disable it.

vmware workstation ：The same problem occurs when vm upgrading from 22593.1 to 22598.1
the log:
2022-04-14T00:49:51.495Z In(05) vcpu-0 Triple fault.
2022-04-14T00:49:51.495Z In(05) vcpu-0 MsgHint: msg.monitorEvent.tripleFault
2022-04-14T00:49:51.495Z In(05)+ vcpu-0 A fault has occurred causing a virtual CPU to enter the shutdown state. If this fault had occurred outside of a virtual machine, it would have caused the physical machine to restart. The shutdown state can be reached by incorrectly configuring the virtual machine, a bug in the guest operating system, or a problem in VMware

jackiexu said:

vmware workstation ：The same problem occurs when vm upgrading from 22593.1 to 22598.1
the log:
2022-04-14T00:49:51.495Z In(05) vcpu-0 Triple fault.
2022-04-14T00:49:51.495Z In(05) vcpu-0 MsgHint: msg.monitorEvent.tripleFault
2022-04-14T00:49:51.495Z In(05)+ vcpu-0 A fault has occurred causing a virtual CPU to enter the shutdown state. If this fault had occurred outside of a virtual machine, it would have caused the physical machine to restart. The shutdown state can be reached by incorrectly configuring the virtual machine, a bug in the guest operating system, or a problem in VMware

Click to expand...

I have updated my Windows 11 on VMware without problem many times.

FreeBooter said:

Open Command Prompt with administrative privileges and execute below commands one at a time to repair system files.

Code:

Dism /online /cleanup-image /restorehealth

Sfc /scannow

Uninstall third-party antivirus programs if you are using Windows Defender disable it.

Click to expand...

Thanks @FreeBooter I did all these steps, and I disabled Windows Defense using the first method at this web site:
https://hetmanrecovery.com/recovery_news/how-to-disable-windows-defender-in-windows-11.htm

and then rebooted, but I still get this from the normal Windows Update:

Awalt said:

Thanks @FreeBooter I did all these steps, and I disabled Windows Defense using the first method at this web site:
https://hetmanrecovery.com/recovery_news/how-to-disable-windows-defender-in-windows-11.htm

and then rebooted, but I still get this from the normal Windows Update:

View attachment 26860

Click to expand...

Several of us are getting this 1900101 error.

I ended up getting past it only by clean installing Windows 11 from an ISO. Blog post on that adventure here: https://www.edtittel.com/blog/clean-install-succeeds-where-beta-promotion-fails. Interesting and too-lengthy adventure, that!
=Ed=

Enable virtualization and it should install. I discovered this the other day gave MS feedback about it.

I use WSL2 so I have VirtualMachinePlatform enabled. I like to disable virtualization because when you have VirtualMachinePlatform enabled, windows essentially runs as a privileged VM. This robs gaming performance in some circumstances, up to 20% or more depending on the game. Some scenarios are affected more than others, probably depends on reliance on memory throughput or similar, not 100% sure I haven't dug in to that. But I turn virtualization (SVM in my case I have an R5 5600X) off unless I'm going to be actively using WSL2. 22598 will not boot unless virtualization is enabled, which causes it to fail during the installation procedure. I enabled virtualization and installed it properly. If I go back into the BIOS and disable it, it won't boot.

Hopefully they fix this as I don't want to run with virtualization, and as a consequence VirtualMachinePlatform, 100% of the time. I'll just switch to Linux full time if they end up going down this road. It's kind of a pain gaming on Linux, but Valve is making great moves to improve this all the time, which makes Windows less and less relevant for me every day. I basically use it as my personal recreation time daily driver because of the ease of gaming use. I use MacOS and Linux already full time for work related tasks (software engineering/devops). So I spend a lot of time on Windows, and pretty much recommend it to people that have gaming as a primary use case. Hopefully this is just a bug they fix.

I noticed a similar problem with the next Build update in the Windows Insider section of this forum.

jackiexu said:

vmware workstation ：The same problem occurs when vm upgrading from 22593.1 to 22598.1
the log:
2022-04-14T00:49:51.495Z In(05) vcpu-0 Triple fault.
2022-04-14T00:49:51.495Z In(05) vcpu-0 MsgHint: msg.monitorEvent.tripleFault
2022-04-14T00:49:51.495Z In(05)+ vcpu-0 A fault has occurred causing a virtual CPU to enter the shutdown state. If this fault had occurred outside of a virtual machine, it would have caused the physical machine to restart. The shutdown state can be reached by incorrectly configuring the virtual machine, a bug in the guest operating system, or a problem in VMware

Click to expand...

I have two virtual environments with Windows 11 Beta Previews. The oldest environment updated to the newest preview just fine, but the newest environment gets this same error as you. Have not figured any differences in the two environments except that I noticed that the environment that made it through the upgrade only had to reboot once, whereas the environment that does not update seems to error during the second boot sequence.

The update to 2598.200 failed under Parallels as well.

Having the same issue here with x.100 and x.200.