question

DougShobe-2137 avatar image
0 Votes"
DougShobe-2137 asked ·

Windows 10 2021-05 KB5003173 x86 Update Fails on 2nd boot restart / cold boot - NOT Edge Chromium Related

As stated in the Title: Win10 20H2 2021-05 KB5003173 update on an x86 (32bit) version of Win 10 Pro. Needed x86 for some 16 bit apps. Edge Chromium is (was) working fine and has NEVER been removed.

Once the update is installed and the system restarted it boots up - ONCE.

IF the system is restarted or shutdown and cold booted - It hangs at the Blue Windows icon (No Dot circles).

The Automated Repair does NOTHING. So something introduced in the May update is preventing a full normal boot. It is NOT Edge related in this case.

Intel i7 3770K / Z77 chipset (ASUS P8Z77i - ITX), 256GB Samsung 860EVO SSD. Tried with both 4GB (2 x 2GB) and 8 GB (2 x 4GB) Ram (All tested good). Tested with both On-Board Intel GPU and NVidia GT630 GPU. No difference.

Everything works fine if the update is removed or re-imaged with April updates restored. Boot cycles work as expected until KB5003173 is installed.

Since this is a MANDATORY update can someone at MS look into this?

Will MS ever get their AI diagnostics testing to work or will users forever dread the monthly updates that are anything but 'Quality' ? :-P

windows-10-generalwindows-10-securitywindows-10-hardware-performance
· 5
10 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Just chiming in with the same issue.

We have several Dell Optiplex 7010s running 32bit Windows 10 for legacy reasons.
Two have updated to 21H1 and are now freezing at the logo.

I was able to roll back the update and they're working normally, but I have had to suspend updates on all of our 32bit machines.

1 Vote 1 ·

Hi,
I am also suffering from Update KB5003173. Have also a Win10 32-bit PC. And yesterday that update has been installed though updates have been disabled until 30th of June.
Would like to get a solution for that.
Kind regards

0 Votes 0 ·

I've been noticing this on a number of Dell Optiplex 9010 and 9020 machines.

Initially I thought it was occurring on machines that had had KB5000802 and KB5001649 before the May update, using WSUS.
After frustrating tries to isolate the critical factor, I installed a fresh 20H2 x86 from USB media, then let Windows update itself.
There it is, unable to restart, with a logo and no spinning dots.
Some more information I have gleaned:
- It seems to be on restart, not a cold start.
- Holding down the power button for 4 seconds does not help. This seems to be like a restart. Removing electricity seems to work,
- Disable Fast Start using group policy or local settings. Fast start makes every startup a restart on the previous session. Disabling it means it has a pretty good chance for users every day who startup and shut down.

To disable Fast start:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Power
"HiberbootEnabled"=dword:​00000000





0 Votes 0 ·

OP here - On ALL our Win 10 systems x86 or x64 I have Fast Start and Sleep disabled wish I which Feature updates would PRESERVE.

I don't want our laptops power settings switched to Sleep due to company laptops in Sleep left in laptop bags over weekends overheating. Hibernate or OFF only.

The problem exists if Hibernate is ON or OFF (Hiberfil.sys file does or doesn't exist).

The initial Restart after any April/May/June update is applied goes through.

The next subsequent Restart or Shutdown and the system will not boot up again unless the update is removed back to pre-April update.

Windows Logo - Frozen - NO DOTS appear !!

I have a deployment project requiring x86 that is now on indefinite HOLD until the patch team graces us with a working update. :-(

Cannot deploy any x86 going forward until this is resolved.

0 Votes 0 ·

I didn't catch whether you were in a domain. If so, you can use group policy to enforce the Fast Start and Sleep settings.
If not, I suggest you keep a folder of useful registry keys to apply when needed.

0 Votes 0 ·
TeemoTang-MSFT avatar image
0 Votes"
TeemoTang-MSFT answered ·

Please configure clean boot on your computer after KB5003173 installed, then restart computer to check boot state.
How to perform a clean boot in Windows (microsoft.com)
https://support.microsoft.com/en-us/topic/how-to-perform-a-clean-boot-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd
If still boot failed, uninstall KB 5003173 and pause update for 30 days from Update & Update->Advanced options->Pause updates. Wait the new update release.
One more thing, 21H1 version for Windows 10 Pro has released, you could upgrade to this version to check result, use Windows update assistant Download Windows 10 (microsoft.com)
https://www.microsoft.com/en-au/software-download/windows10


If the Answer is helpful, please click "Accept Answer" and upvote it.
Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


· 2
10 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Teemo,

As this initial post has now grown to nearly three pages, would it be possible to at least get an acknowledgement that the MS Patch team are now aware of the issue?

Three cumulative updates (April, May, June - 2021) and the 21H1 update ALL cause the boot issue on x86 installations across multiple vendors as reported.

I don't expect an immediate fix but ALL of us following this deserve to know that the Patch engineering team has been notified of this major issue on x86 platforms.

3 Votes 3 ·
KTG-8706 avatar image KTG-8706 DougShobe-2137 ·

As Doug suggested getting some type of confirmation from Microsoft that they at least know there may be a potential issue out there would go a long way. I don't suspect we are likely to see anything like that happen in this forum but it sure would be nice if it did.

The challenge I see is that so far this is the only forum I have come across where people with this issue have been coming together to report it. I suspect this is primarily the result of too small of a user base still running 32 bit Windows 10. As the issue does seem to affect a variety of PC manufacturers I am hopeful we can make enough noise to get some attention.

I am of the mindset that we simply can not update these machines moving forward until there is some type of acknowledgement of an issue. This is a viable short term plan but it certainly is not a viable long term plan for an OS that is supposedly still supported by Microsoft.

Any suggestions on how we can get some attention to the issue?

0 Votes 0 ·
DougShobe-2137 avatar image
0 Votes"
DougShobe-2137 answered ·

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.

10 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DougShobe-2137 avatar image
0 Votes"
DougShobe-2137 answered ·

Last bit of detail.

The boot-loader doesn't fire off completely (Circle Dots below the initial Blue Windows logo).

None of these services ever even get loaded to be an issue in the first place.

The x86 system is a standard MBR / Non-EFI loader.

System reboots and loads ONCE after the May '21 update is installed.

Then that is it. Only the Blue Windows logo, frozen keyboard, and NO boot-loader processing after.

· 2
10 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks for detailed troubleshooting thread. Seems to be a graphics adapter driver compatibility issue, i still suggest to uninstall KB003173 and pause update for a period of time. Let's wait for the next update.

0 Votes 0 ·

TeemoTang,
The June update KB5003637 does nothing to address it.
As detailed in my full reply, the problem exists in in a brand new 20H2 (or 21H1) OS Media install plus Windows Update patch.

We want to know that Microsoft cares about the 32 bit operating system they supposedly support.

0 Votes 0 ·
Martins-3859 avatar image
0 Votes"
Martins-3859 answered ·

The same issue for us - multiple Dell pc's with win10 x86 doing the same thing. Only for us it started at least 2 month ago, so for us KB5003173 is not root cause, it must be some other update. Latest preview update KB5003214 doesn't help.

10 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DougShobe-2137 avatar image
0 Votes"
DougShobe-2137 answered ·

A bit more detail as I have tested with two different GPUs.

Initially (As intended for deployment) is the integrated GPU from Intel on the Ivy Bridge (3rd Gen - i7 3770 @ 3.4 GHz).

Using the standard MS / Intel driver and a later / final release driver that works fine on the x64 version of Win 10 Pro.

Thinking it may have been graphics related I installed an NVidia GT-430 (Fermi series) using the last x86 NVidia driver for Fermi - v391.35 from NVidia.

Only do custom driver installs with NVidia - Graphics Driver, NVidia Audio, and Physix (No 3D garbage or the GeForce Experience bloatware). Simple and reliable.

So the May, 21 patch FAILS on the two most common GPUs for the era of the equipment. I don't use dual Graphics (like some laptops) so either Intel OR NVidia - not both.

If return to Safe Mode (Only way to boot the system after the patch) and uninstall the May, 21 update the system returns to normal. Rinse - Repeat.

Pausing for 30 days is only viable if WE know MS is going to triage and fix / re-release the patch. I miss the 180 day patch hold in earlier Win 10 versions now. :-P

I am NOT convinced it is graphics related as the boot-loader failure (Blue Win icon - No spinning dots) manifests immediately before the system has a chance to start loading much of anything driver wise. I think the issue is a bit lower on the ladder (Boot-loader, CPU stack, AHCI, etc.). GPU driver usually loads later in the cycle and the 'Spinning Dots' should be apparent by then.

The system is formatted as standard MBR (NTFS) - so in this instance it isn't running off an EFI boot as most x86 implementations won't work with EFI boot.

I deploy mainly x64 for the last several years (Win 10 and VMware Servers). So this x86 issue is irritating as I NEED an x86 Win 10 for this project for 16 bit sub-system.

For anyone else reading who wants to opine on trashing 'old' systems due to Meltdown / Specter vulnerabilities:

EVERY Intel CPU including 10th / 11th Gen is susceptible to these issues and requires physical access so it isn't as big a deal as made out to be. We still deploy Quad core i7 Haswell / Devils Canyon CPUs and there is NOTHING wrong with them. Devils Canyon - i7 (1st 4.0 GHz stock CPU) holds up and is actually a better platform than 5th / 6th Gen Intel desktop systems. If going NEW I would go AMD Ryzen 7 / 9 now and that would be a waste on x86 for this project.

10 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

NickGomes-8696 avatar image
0 Votes"
NickGomes-8696 answered ·

I am experiencing the same exact issue with some of our 32bit PCs. Something other things to add is I've tried updating to 21H1 and that either fails to install or if it does install it still freezes during boot/reboot. Trying to clean install 21H1 32bit via a media creation tool gives the error: 0xc0000359. The only solution I've found is roll back the May update and pause updates for as long as possible and hope it gets fixed.

The PCs that are freezing for us have Gigabyte H310M S2P 2.0 motherboards. We have a few with ASUS H110M-K motherboards and I can update those fully, both in 20H2 and 21H1, and I experience no issues at all.

10 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DougShobe-2137 avatar image
0 Votes"
DougShobe-2137 answered ·

My system is an ASUS P8Z77-i (The best Z77 ITX board made in that era - 2013). I have several identical systems that run x64 on Win 10 Pro with NO issues on the 20H2 May, 21 patch.

I haven't bothered with the 21H1 update - based on other posters here it would be a waste of time to do so. 21H1 is a minor update so whatever issue is in the May, 21 patch will be included in the 21H1 install and current updates for that release.

The problem system has 4GB (2 x 2 GB sticks) it was also tested with 8 GB (2 x 4 GB sticks). The identical x64 systems we have in service have 16 GB (2 x 8 GB sticks). All DDR3 RAM has been tested thoroughly so it isn't a ram issue in my case.

The ASUS P8Z77-i has a Broadcom WiFi / Bluetooth MSATA, Realtek LAN and Audio (Like the audio on the Gigabyte H310M S2P - Nick posted above).

Nick's H310M is significantly newer (8th / 9th Gen Intel CPU support - 2019 era).

10 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

NickGomes-8696 avatar image
0 Votes"
NickGomes-8696 answered ·

I have also had no issues with 64bit systems.

The systems (32bit) that work vs the systems that don't have the same processor Intel Celeron CPU G3900 @ 2.80GHz, both have one 4GB stick of memory, just different motherboards.

10 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DougShobe-2137 avatar image
0 Votes"
DougShobe-2137 answered ·

Nick,

Instead of trying to get the MCT utility to make an x86 Win 10 boot key, have MCT download the x86 as an ISO. Then Use Rufus (Free - Supported) and have it create the x86 as an MBR (non-UEFI Legacy Boot).

Some of the newer system boards and older boards that don't support Win 10 EFI properly cannot provide the x86 EFI tables that would allow the EFI Boot-loader to find the boot partition to load Windows.

In effect your system board would be in Legacy BIOS and a simple partition structure (2 Partitions in MBR - 4 Partitions in UEFI).

Secure Boot - disabled / CSM-ON in BIOS. On initial boot use (Shift-F10) and run DiskPart - (List Disk / Select Disk / Clean) before continuing to install Windows from the setup screens. MBR (NTFS) format (No EFI partions on the boot HD / SSD).

It is possible that the 20H2 / 20H1 May update has creamed the boot-loader on our x86 versions. It wouldn't be the first time...

10 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DougShobe-2137 avatar image
0 Votes"
DougShobe-2137 answered ·

Martins,

I saw your post earlier so I don't want you to feel ignored at our little party here. ;-)

I have Dell Servers (for our vSphere Hosts / Win Server back-end), and a few Inspiron gaming laptops (NVidia GPUs) for our Autodesk users.

Unfortunately I don't buy their desktops as I think they are junk (I treat HP the same in this regard). Too many proprietary cables, Power Supplies, goofy system board layouts, etc. So I just don't have much hands on with their desktops anymore.

All our Desktops use high quality components so having a 5 - 7 year old desktop still running 100% is not unusual in our facilities.

I am only having this one x86 issue (actually our ONLY x86 desktop I want to deploy - figures...), we are x64 on EVERYTHING else.

My team still builds our own desktops for specific tasks / departments. You should see our 128 GB Ryzen 9 desktops our Virtual Design group use. Built two for what Dell / HP / Lenovo would charge for one !! Otherwise I throw an Intel i5 NUC at any basic office PC stuff. Hoping AMD will get their Navi2 based APUs out soon for an AMD based NUC next release cycle.

10 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.