If forced into SAFE mode it will boot - Using that to uninstall the May 21 update to restore system to a bootable state.
The issue is re-produceable with NVidia or Intel GPU drivers. It also happens if the system is in SysPrep - Audit mode (From a re-image) if the May 21 update is applied.
There are NO non-MS services running on the system.
Two Apps (Greenshot - excellent Printscreen Utility - FREE for Business and Personal), and the classic NVidia control Panel (with NVidia GPU installed - Non DCH) are the only auto running apps.
This issue isn't happening on our x64 platform(s).
Turning off / suspending the updates only guarantees this system cannot be deployed as a 30 day time bomb solves nothing.
How am I to assure our CEO emeritus that he won't have his system nuked afterward?
This was to replace a Win 7 system - I see NO reports about this issue (Only the Edge Chromium uninstalled / empty folder left - BEFORE the May update is applied and sporadic audio issues with oddball audio chips).
In the last 12 months a MAJORITY of Win 10 customers have been treated to:
VBA runtimes trashed (Causing Excel Macro failures - took 15 days to get a fix posted and tested).
Print Spooler bugs causing App Crashes and Blue Screens (Twice in 6 months - requiring hotfixes). Type 4 print drivers still stink.
Various Office 365 issues (Outlook to numerous to document here) from the constant untested updates.
I have been working with Windows NT since the original NT 3.1 through Win 10 / Server 2019. I used / supported WinXP-x64 for two years until Win 7 launched.
I want to make sure MS is aware that the x86 version of the May '21 patch needs a team to thoroughly check it out or PULL the x86 versions from the Update service.
If MS is going to support Win 10 x86 though EOL in 2025 they need to follow through.
Worst thing MS did was dismantlement of the Patch Team they had up to 2015. It is now apparent that the current patch testing system isn't working.