Aug 05 2021 01:54 PM - edited Aug 05 2021 03:20 PM
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.
Aug 05 2021 05:32 PM
Aug 05 2021 05:34 PM
Aug 05 2021 06:06 PM
Getting the above message. I have a fast Dell G5 5505, but now it is a brick and not booting.
Aug 05 2021 07:37 PM
Aug 05 2021 10:40 PM
Aug 06 2021 04:32 AM
Aug 06 2021 04:48 AM
Aug 06 2021 06:01 AM
SolutionAug 06 2021 10:06 AM
Aug 06 2021 10:59 AM - edited Aug 06 2021 11:27 AM
Further update - installed on an Azure Gen 2 VM, fresh Win 10 Pro and updated to Win 11, all fine.
"They say not to run windows 11 on laptops that are 5 years old as they are not optumise for the win11."
Only optimisation I can see is TPM. You can run Win 11 on low spec slow hardware that has TPM but not on much higher spec faster hardware with top-end components that just doesn't have TPM. Also what about desktops? My "old" Dell XPS desktop is a high spec system and very fast for my dev use (Visual Studio etc), just no TPM.
Or is this a way they've come up with to specify a generation of processors, likely that don't have Spectre/Meltdown vulnerabilites and thus the performance affecting mitigations? Except that doesn't add up as there are plenty of TPM PCs with those processors, and anyway a fast enough processor of that era is plenty fast enough.
I know MS say TPM requirement is about security, but that isn't optimisation so it's an odd thing for their support to say.
All said, the Azure VM running Win 11 now... meh. A new desktop theme basically.
Aug 06 2021 11:13 AM - edited Aug 06 2021 11:17 AM
What they mean is what i said. They did say it can run but not very well and some feature in windows 11 may not perform well. This doesnt mean you can't install win11, just not recommended.
So I got this right, you said you manage to inatall the 120 version?
Aug 06 2021 11:21 AM - edited Aug 06 2021 11:23 AM
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.
Aug 06 2021 11:22 AM
I just tried installing Windows 11 Beta for the first time, and getting the exact same error, twice. So frustrating.
Aug 06 2021 11:25 AM
Aug 06 2021 01:28 PM
Aug 06 2021 01:42 PM
Aug 06 2021 11:14 PM - edited Aug 07 2021 10:07 PM
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:
Aug 07 2021 07:43 AM
Aug 07 2021 08:15 AM
Aug 06 2021 06:01 AM
Solution