Forum Discussion
Windows 11 Upgrade 10.0.22000.120 BSOD Process1_Initalization_Failed upon reboot
- Aug 06, 2021this is the best answer I got. I manage to get a call from Microsoft. So the issue is the version 10.0.22000.120 is unstable and is unable to boot because of it. The reccomendation by Microsoft is not to install the new version and still used 10.0.22000.100 for the time being.
The version is failing to reboot because its corrupted. They will be looking into this and was helpful with the information i was able to give. This will be passed on to the Development team and keep posting on this community as they are watching and understand the frustration. They asked that everyone not to get upset over it and understand the concerns, they thank you all for posting this issue.
They are sorry to hear about the issues with the insider, and do say that once you sign up to the insider it under to soul dregession.
It is confirmed by a member of the tech team that it's recommended to buy a new laptop as most new laptops will have CMS and TPM 2.0 Enabled and it very rare for a laptop or desktop not to have these disabled. They say not to run windows 11 on laptops that are 5 years old as they are not optumise for the win11.
but they would like to say thank you to everyone that has used windows 11 insider and all the feedback send has been really helpful.
I see the same bug on Build 22000.120, never saw it on previous builds up to 22000.100.
Looks like the bug occurs when updating directly from Windows 10 19043,1151 to Windows 11 build 22000.120.
On Saturday 8/7/2021 Windows Update is now downloading in 2 steps.
1) Download and update to 22000.100
2) Download and update to 22000.120 as a second step.
This looks like a workaround that prevents the error.
When they updated the OS name to Windows 11 in 22000.120 they screwed up the (Shift + Restart) recovery function. The machines that do not fail still show Windows 10 in the Startup and Recovery, the machines that fail show the updated name Windows 11, evidently while updating the description they screwed up something else that causes the BSOD.
Machines not getting BSOD at 22000.120 show still Windows 10 here:
Machines getting BSOD at 22000.120 show Windows 11 here: