Blue screen of death (UNSUPPORTED_PROCESSOR) after installing KB5062632 monthly Rollup July 2025 After installing the KB5062632 monthly Rollup July 2025 on VirtualBox version 6.1.50 I get a blue screen of death with the error message UNSUPPORTED_PROCESSOR as soon as I reboot. I've tested live OS integration as well as creating an updated image and a clean new installation which results in the same error. The processor is an AMD Ryzen 9 3900X I have for over a year and didn't have this problem before. Does anyone else have this problem with a newer processor?
Moin @ All! My July 2025 ESUpdate experience for Windows 7 Pro / Enterprise SP1 x64 systems: "Licensing method": KB4528069 & "new" BypassESU-v13f "Installing method": Manual download and installation via Microsoft®Update-Catalog KB5062065 (Security and Quality Rollup for .NET Framework 4.8) -> succesfully installed KB5062558 (Cumulative Security Update for IE 11 for Windows Server 2008 R2 x64) -> succesfully installed KB5062619 (Security Only Quality Update for Windows Server 2008 R2 x64) -> succesfully installed The current Security Intelligence Update was downloaded and installed by the auto-update function of MSE. @ abbodi1406: Great job & thx for your support!
I have the AMD Ryzen 9 3950X and have no problems with installing and using the KB5062632 Update. And you have the VirtualBox mode and not the standard mode; this can be the problem or you have not the lastest drivers or firmware´s installed; it can be that thing that makes your problem.
Thanks! I just want to be sure I understand, "licensing method" means manually download and install KB4528069 via Microsoft catalog? Then use bypassESU-v13f ?
Did anyone notice this months Internet Explorer 11 update is for Win 8, 2012 Server? Just curious... For 07-2025 KB5062558 Cumulative Security Update for Internet Explorer 11 for Windows Server 2012 for x64-based systems (file name has Win 8) windows8-rt-kb5062558-x64_79c0e7a571ed04b95983a45d6ff9f58b9565563d.msu Installed June 2025 KB5062558 Cumulative Security Update for Internet Explorer 11 for Windows Server 2008 R2 for x64-based systems (Win7 core) Cores changed from 6.1 to 6.2 with Win7 to Win8 & Server 2008 R2 to Server 2012... Windows 7 2012-08-01 6.1 Windows Server 2008 R2 2011-04-06 6.1 Windows Home Server 2011 2011-04-06 6.1 Windows Server 2012 2012-08-01 6.2 Windows 8 2012-08-01 6.2
I don't know if something happened with the June patch last month, but I've had to use the msu package to update as the Windows Update control panel applet was completely toasted for some reason (telling the service isn't running despite the service clearly is, the entry in services.msc shows the Windows Update service as running and the update history page is just blank) However, the July rollup was installed without issue (despite this one)
@ryegrass The Update worked fine on my AMD 9950X, are you using the 13f version of ESU Bypass? Yes, I'm using BypassESU v13f. @NewEraCracker It happened last month as well with Windows 11 on virtualized environments: borncity.com/win/2025/06/18/windows-11-server-2025-june-2025-updates-cause-bsod-in-proxmox-kvm-qemu Thanks for the tip, I'll check out the link. @peter4heppner And you have the VirtualBox mode and not the standard mode; this can be the problem or you have not the lastest drivers or firmware´s installed; it can be that thing that makes your problem. I always test monthly updates first in VirtualBox. I didn't realize that the virtual machine itself could be the problem. Thanks.
2025-07-11 Manually DOWNLOADED all update KB's... TURNED WU & AV & unneeded programs OFF B4 updating... Checked latest SSU; Already Installed in April 2025 KB5056456 Servicing Stack Update for Windows Server 2008 R2 for x64-based Systems Installed July 2025; Restarted KB5062065 (Security and Quality Rollup for .NET Framework 4.8) -> succesfully installed Installed July 2025; Restarted KB5062632 Full Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems Installed June 2025 in July 2025; Last Core 6.1 IE11 security updates offered; Restart NOT Required KB5062558 Cumulative Security Update for Internet Explorer 11 for Windows Server 2008 R2 for x64-based systems TURNED WU & AV ON after ALL updates & restarts completed... Updated AV & did Quick scan... WARNING July 2025 IE11 KB5062558 NOT Installed; Core is 6.2 (Win8); Not 6.1 (Win7)... KB5062558 Cumulative Security Update for Internet Explorer 11 for Windows Server 2012 for x64-based systems; NOT for Windows Server 2008 R2 for x64-based systems... Thanks for success & one month closer to full Linux system... ;>))
About the blue screen of death with the error message UNSUPPORTED_PROCESSOR after installing KB5062632 monthly Rollup July 2025. I also installed the KB5062632 monthly Rollup July 2025 on an older computer (AMD Phenom II X4) also running Windows 7 x64 as host with VirtualBox version 6.1.50 and got the same result, meaning a blue screen of death with the error message UNSUPPORTED_PROCESSOR as soon as I reboot. I followed the advice in this forum to change the virtualisation mode (System -> Acceleration Tab -> Paravirtualisation Mode) In VirtualBox 6.1.50 with these results. These paravirtualisation mode cause a blue screen Standard Hyper-V These paravirtualisation mode work No Legacy minimal KVM The installation of KB5062632 directly on the host computer without VirtualBox succeeded. Strange that I didn't have the blue screen of death with the previous montly rollups like the June update KB5061078.
I think all Windows 7 users have blue screen´s even with fully compatiblity of all hardware components(I mean myself, i have a|an windows 7 system with all the newest updates, firmware´s and drivers and software installed on; and i have also time to time blue screen´s)! If one find one windows 7 system have one windows 7 system; that have no problem´s; please let me know it, thank you so much^^ This is not your problem you have alone kukris, i have it too
I've never had a blue screen in Win 7, but I've always delayed the onboarding of updates. After awhile the company will take action on the defective update(s), presumably.