Forum Discussion
nekoboinick
Aug 05, 2021Copper Contributor
Windows 11 Upgrade 10.0.22000.120 BSOD Process1_Initalization_Failed upon reboot
So I recently switched to the Windows Insider Beta build. And when I go to restart to upgrade to Windows 11 the computer goes into the "Upgrades are applying" screen before it reboots at 100%. When it tries to start back up it goes to a black BSOD with the error PROCESS1_INITIALIZATION_FAILED. Then reboots to a constant black screen until I hold down the power button to turn it off and back on. Which then it reboots to Windows 10. I can attach my Memory dump file if needed.
Error code: 0xc1900101
Note: Works fine when installing it on a hypervisor from Windows 10.
I should probably note: I did have a Hyper-Visor VM running Windows 11 prior to installing the update, which had shut down the host computer upon hitting start>power>shutdown. Which I though weird and that I must've seen my screen wrong. But upon booting back up prior to the update and logging in my computer BSODed with a "Service_Start_Exception" stop code. And then restarting it was fine afterwards.
- this 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.
- GamerToTheMaxCopper Contributor
I have the same problem as of right now, It was caused from upgrading from windows 10 straight to the 22000.120 Build which had a corrupted SafeOS update and it corrupted the winre.wim File which is responsible for the windows recovery enviroment which includes reverting updates, reseting, Startup repair. Microsoft needs to fix this fast
- WerewolfheroCopper Contributor
https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewiso
Choose the .120 win11 build and the channel you're in (dev or beta) and download/create a usb drive with that, It should let you install straight to that build. If your current build of windows is still somewhat useable you may be able to do an upgrade in order to keep your existing files/programs
- WerewolfheroCopper ContributorFailed to install (kept saying there was something wrong and would roll back the update before booting back to windows) on my desktop despite it being in compliance for Win11 (TPM and all) but my old laptop which I threw windows 11 on for fun (which is way too old for win11) 120 updated with no problem at all.
- schm1dtCopper ContributorBy any chance, has anyone here tried using BCDBoot to repair their boot entries? I suspect that they are what's causing these shenanigans, especially regarding the Windows Rollback entry, which from what I've seen points to the wrong path for it's WinRE image.
- nekoboinickCopper ContributorI got mine to work after waiting a few days while out of insider. When I went to go back to insider Windows downloaded update 10.0.22000.100 instead of 120 and it actually worked. So I am not sure if what you suggested was a good fix or not.
- schm1dtCopper Contributor
nekoboinick Ah, you had issues with it while upgrading right. My idea was mainly targeting people stuck on 120 already who get the same BSOD when trying to rollback to 10, including me. For people who had upgrade issues they should hopefully be fine now that MS has pulled the crap that is build 120.
- foxx1337Copper ContributorI just restarted the system and Windows update is now giving me 22000.100 which installed just fine.
- tristanfergusonBrass Contributoryep it installing the older version on my pc as well. safe to say they realise the call and many others who did the same. thanks to all who make Microsoft aware of it. Good job to all.
We need to keep this up to make sure that when the public version is up and ready.
- fggIBSteel Contributor
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:
- sylveonCopper ContributorAm also getting the same. Joined the beta branch today and then tried installing 22000.120 (which is weird, I thought beta was still on 22000.100, but whatever), I keep getting this error after rebooting to install Windows 11. Custom build with Ryzen 3700X, CSM is off and TPM is on. Have Hyper-V/HVCI installed and enabled.
- foxx1337Copper ContributorAlso experiencing this while upgrading from 20H2 to 10.0.22000.120.
- moxiejeffCopper Contributor
I just tried installing Windows 11 Beta for the first time, and getting the exact same error, twice. So frustrating.
- tristanfergusonBrass ContributorPlease read message from Aug 06 2021 06:01 AM.
- aj006Copper ContributorGetting the same error on a Ryzen 7 machine with Hyper-V installed and running. Tried installing the latest Windows 11 build from the Beta channel, BSODed on reboot for installation, but rolled back to Windows 10 on reboot after the BSOD.
- tristanfergusonBrass Contributor
the CMS kick in and stop the install from bricking your pc. The pc did the right thing and you should be fine.
They ask users not to install it so they can fix the issue. that what was discussed on the phone call with a microsoft tech support member.the user above this reply manage to install it so I think he got lucky. But it isn't recommended. I did my part for the insider and I love the look feel and UI design. the control panel is not being removed and is confirmed removing it would distory the OS.
- tristanfergusonBrass Contributorthis 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.- nekoboinickCopper ContributorSo I have to say I probably see that that could be the case. WhyNotWin11 says my computer is fully compatible. But I would like to see if you could reply if they ever contact you again that it works by chance.