" Subject: Technical explanation regarding the relation between KB5087544 (0x80073701) and Legacy Hardware (Z270 Chipset) The relation to the specific hardware is established through the UEFI Secure Boot DBX (Forbidden Signature Database) update mechanism included in this specific cumulative update. Here is the technical breakdown of the conflict: NVRAM Write Failure: This update (KB5087544) attempts to update the Secure Boot revocation list (DBX) by writing new variables directly to the motherboard's NVRAM via UEFI Runtime Services. Outdated Firmware (BIOS): My motherboard (MSI Z270 Tomahawk) is running on the latest available BIOS version from July 26, 2018 (7A68v17). This firmware predates the 2026 security protocols and lacks the necessary logic or storage capacity (NVRAM space) to handle the size of the modern DBX payload provided by Microsoft. The 0x80073701 Error: While Windows Update shows a generic "SXS_ASSEMBLY_MISSING" error, in this specific hardware context, it signifies a failure in the Secure Boot handshake. The OS is unable to commit the required security certificates to the hardware's permanent storage. TPM 2.0 Conflict: Although the system has a functional TPM 2.0 (via Intel PTT), the TPM cannot act independently of the BIOS when it comes to Secure Boot database modifications. Without a 2026-ready BIOS update from the vendor (MSI), the hardware physically rejects the write operation initiated by the Windows Update process. In summary, the hardware/software relation is a firmware-level incompatibility where the legacy motherboard's NVRAM cannot process or store the modern security certificates mandated by the May 2026 update. This is a well-documented issue for older chipsets (like Z270) that have reached their End-of-Life (EOL) for BIOS support."
Next time maybe type this info, the screens contain a language that is not english I don't have systems that enforce secureboot (my most modern system is a i9 11900 on a Asrock z590 Taichi mainboard), my second main is a i7 11700 on a Asrock z590 Phantom Gaming Velocita mainboard and my oldest system (i use on a daily base) is a i7 8700 on a Gigabyte B360-HD3P mainboard (all selfbuild). All run IoT Enterprise 2021 LTSC.
I run 11 on ancient first gen i3 laptops, just for testing but they accept 11. The i7 8700 was running 26H1 up to a week or two ago but i decided to go back to old(er) builds for that hardware
Why does W10UI now give an NT Version error when trying to assemble the latest W11 iso? I'm using latest W10UI_10.59b version.
Please show the full integration progress, that will give so much useful info. And when updating a win 11 iso please ask in the win 11 hotfix thread.
"Thanks for the confirmation. Since the logs show no OS-level corruption or missing system files, it clearly points to the hardware/firmware limitation we discussed. The presence of the STATUS_INSUFFICIENT_RESOURCES error during the UEFI variable write phase confirms that my 2018-era BIOS simply cannot handle the new Secure Boot DBX payload. I will hide the KB5087544 update for now and continue with my stable April 2026 build. It's good to know that my Windows installation is healthy and the issue is purely a hardware-firmware mismatch. I appreciate the help!"
Friends, my problem is solved. I think the problem was caused by excessively restricting telemetry with ntLite.
Indeed, it looks like those latest SecureBoot updates on W10/W11 may require some kind of telemetry. Programs such as O&O Shutup might also need to be temporarily reset to default settings to avoid problems. Maybe someone can pinpoint which exact telemetry points are necessary?
Setting the TimeBrokerSvc (Time Broker) registry value to Start = 4 (Disabled) causes severe system breaks in Windows 10 following the KB5087544 cumulative update. The Problem The TimeBrokerSvc manages background permissions for Universal Windows Platform (UWP) apps, the Start Menu, and Windows Settings via RuntimeBroker.exe. Update KB5087544 tightly integrates core Windows shell components with this service. If it is completely disabled (4), the following critical issues occur: The Start Menu and Taskbar freeze or crash. The Windows Search bar becomes unresponsive. The Windows Settings app refuses to launch. The system suffers from extreme login delays or black screens. The Fix: Re-enable the Service You must change the startup type back to its default value of 3 (Manual).