Can anyone think of a difference between a standard reboot and a reboot that happens when Patch Tuesday updates are installed?
I have an older system based on a 4th Gen Intel i7. Yes - I know that this is technically not supported on Windows 11 so I'll just note right now that I have the same issue with Windows 10 as well.
The issue is simple, but it's simply beyond me to explain why this happens. I can either reboot the system or shutdown and then power back on again and the system will come back up perfectly fine every single time. However, every single Patch Tuesday, when the system reboots to apply the updates, the system will fail to boot. The symptom is that rather than booting into Windows, it boots to a UEFI Firmware command prompt. When that happens, I power off the system, power it back on, and it will boot just fine to finish installing the updates and then go into Windows just fine.
Anyone have a firm grasp on the difference between these boots? Is Windows booting into some special mode to finish applying the updates?
I just feel like maybe, if I knew what the difference was, it might give me something to actually try troubleshooting.
Here are some system details:
Motherboard: MSI Mpower Max AC
CPU: Intel Core i7-4790K
TPM: Physical TPM 1.2
32GB DDR3 RAM
Boot device: Samsung XP941 M.2 SSD
Additional Drives: 1 x 4TB 3.5" HDD and 5 x 8TB 3.5" HDDs
NOTE: Fast Startup is disabled.
I have an older system based on a 4th Gen Intel i7. Yes - I know that this is technically not supported on Windows 11 so I'll just note right now that I have the same issue with Windows 10 as well.
The issue is simple, but it's simply beyond me to explain why this happens. I can either reboot the system or shutdown and then power back on again and the system will come back up perfectly fine every single time. However, every single Patch Tuesday, when the system reboots to apply the updates, the system will fail to boot. The symptom is that rather than booting into Windows, it boots to a UEFI Firmware command prompt. When that happens, I power off the system, power it back on, and it will boot just fine to finish installing the updates and then go into Windows just fine.
Anyone have a firm grasp on the difference between these boots? Is Windows booting into some special mode to finish applying the updates?
I just feel like maybe, if I knew what the difference was, it might give me something to actually try troubleshooting.
Here are some system details:
Motherboard: MSI Mpower Max AC
CPU: Intel Core i7-4790K
TPM: Physical TPM 1.2
32GB DDR3 RAM
Boot device: Samsung XP941 M.2 SSD
Additional Drives: 1 x 4TB 3.5" HDD and 5 x 8TB 3.5" HDDs
NOTE: Fast Startup is disabled.
My Computers
System One System Two
-
- OS
- Win11 Pro 25H2 (RTM+)
- Computer type
- PC/Desktop
- Manufacturer/Model
- Acemagic
- CPU
- Intel i7-14650HX
- Memory
- 32 GB
- Graphics Card(s)
- No GPU - Built-in Intel Graphics
- Sound Card
- Integrated
- Monitor(s) Displays
- Varies as machine will often be moved to locations with different monitors
- Screen Resolution
- Varies
- Hard Drives
- 1 x 1TB Gen 4 NVMe SSD
- PSU
- 120W Power Brick
- Keyboard
- Corsair K70 Max RGB Magnetic Keyboard
- Mouse
- Logitech MX Master 3
- Internet Speed
- 1Gb Up / 1 Gb Down
- Browser
- Edge
- Antivirus
- Windows Defender
-
- Operating System
- Win11 Pro 25H2 (RTM+)
- Computer type
- Laptop
- Manufacturer/Model
- Lenovo ThinkBook 13x Gen 2
- CPU
- Intel i7-1255U
- Memory
- 16 GB
- Graphics card(s)
- Intel Iris Xe Graphics
- Sound Card
- Realtek® ALC3306-CG codec
- Monitor(s) Displays
- 13.3-inch IPS Display
- Screen Resolution
- WQXGA (2560 x 1600)
- Hard Drives
- 2 TB 4 x 4 NVMe SSD
- PSU
- USB-C / Thunderbolt 4 Power / Charging
- Keyboard
- Backlit, spill resistant keyboard
- Mouse
- Buttonless Glass Precision Touchpad
- Internet Speed
- 1Gb Up / 1Gb Down
- Browser
- Edge
- Antivirus
- Windows Defender
- Other Info
- WiFi 6e / Bluetooth 5.1 / Facial Recognition / Fingerprint Sensor / ToF (Time of Flight) Human Presence Sensor
