[German]I received reports in comments of my German blog, that users of Fujitsu systems are ending with bricked devices during installing the June 2025 security updates for Windows. Die Rechner starten nicht mal mehr ins BIOS/UEFI. Ursache ist wohl eine Aktualisierung der DBX-Records für den Secure Boot durch die Windows Updates. Lässt sich nur mit Tricks wieder korrigieren.
Advertising
Fujitsu Esprimo P556
I had a quick look at what is available on the Internet about the Fujitsu Esprimo P556. It is a desktop system that is available second-hand on many platforms and can probably be upgraded to Windows 10 – or with tricks to Windows 11.
According to the following German data sheet, the computers intended for office use came with Intel iCore i3-i7 CPUs and Windows 7 to Windows 10, but are labeled as openSUSE Linux-compatible.
User reports about bricked devices
In the context of the June 2025 Patchday at Microsoft, users have reported bricked devices in comments on the German blog post Patchday: Windows 10/11 Updates (10. Juni 2025). German user Nico startet with this comment by pointing out that the June 2025 Windows update round had bricked more than 20 Fujitsu Esprimo P556 computers. After the obligatory restart, the computer immediately freezes and only the Fujitsu logo is displayed. This bricked devices can't no longer access the BIOS or UEFI.
Advertising
Resetting the BIOS and then deactivating the TPM can help
German user Peter came with this comment, because he is running a P556 with Windows 11. He writes that he experimented a bit and was able to reset the BIOS (probably meaning the stored CMOS data). To do this, he removed the battery on the mainboard for a few minutes and also disconnected the device from the power supply (so that all capacitors were discharged).
His statement was that the problem with the computer hanging in the manufacturer's logo immediately reoccurs when the TPM module is activated (enabled) in the BIOS/UEFI. Without TPM enabled, the computer restarts. He concludes that there was something in the last update (or even before) that crashed the TPM. A test exchange of CPU and RAM did not help.
Another report: a DBX update has been shipped
Austrian user Gunnar also confirms the problem in this comment (thanks for the hint) and referred to his German article Fujitsu D3410-B Mainboard Recovery UEFI/BIOS-Flash nach SecureBoot DBX WindowsUpdate There he confirms that the DBX file for the Secure Boot of Windows is manipulated by the update, and that goes wrong.
He writes that, according to his analysis, the SBAT was not renewed. However, the DBX has grown from 8KB to 24KB. Therefore, he suspects that the memory space intended for processing/storage is exceeded and then the update goes wrong.
Gunnar outlines how he got out of the mess for his Fujitsu D3410-B by recovering the BIOS and preventing the changes from being reinstalled. The problem will be to find a suitable BIOS. In this comment, Nico mentions that he found BIOS versions at German vendor Kontron located in Augsburg. An anonymous reader writes in this comment that the files for the P556/557 BIOS version are still on the Fujitsu servers. He used a search with pattern like
https://support.ts.fujitsu.com/ D3410
where D3410 is the model number of the device, and was able to get search results with download URL of BIOS updates. Maybe it will help.
Reports on reddit.com
Gunnar also refers in his article to the reddit.com thread Dozens of P556 with corrupted BIOS after update, where users of Fujitsu Esprimo P556 are complained about broken devices. There a user describes his way to bring a Fujitsu D3410-B back to life. I definitely recommend going through the article by Gunnar (use deepl.com to translate) and on reddit.com.
Report in the Microsoft Answers forum
In this comment, German blog reader Paul refers to the post After installing update KB5060533 I believe on 2 pc neither will now start in the Microsoft Answers forum. There someone describes his problem with Fujitsu computers and documents the hanging startup screens with photos.
A search for "kb5060533 fujitsu bricked" returns more hits (including some Italian-language results) where Esprimo P556 are affected.
Similar articles:
Microsoft Security Update Summary (June 10, 2025)
Patchday: Windows 10/11 Updates (June 10, 2025)
Patchday: Windows Server-Updates (June 10, 2025)
Patchday: Microsoft Office Updates (June 10, 2025)
Windows 11 24H2: Out-of-Band Update KB5063060
Windows 10/11: Preview Updates May 27, 28,2025
Attention: June 2025 Patchday closes vulnerability CVE-2025-33073 in Windows
Windows network vulnerability CVE-2025-33073 (Reflective Kerberos Relay Attack)
Windows 10: June 2025 update KB5060533 causes Surface Hub v1 boot error
Advertising
