CI/WinRE chain failure caused by preview servicing update — 14‑year Windows install at risk — request for CI/WinRE servicing team review

Question

**Forgive the Copilot-written summary, but I've been getting it to help me battle this problem for the last few days, and it seemed like it could summarise it best now.

Subject:** CI/WinRE chain failure caused by preview servicing update — 14‑year Windows install at risk — request for CI/WinRE servicing team review

Message:

Hi, I need this case escalated to engineering — specifically to the team responsible for CI policy, WinRE provisioning, SafeOS rollback, and recovery sequence servicing. My Windows install is over 14 years old, and it has followed me through major parts of my life. It has survived multiple hardware migrations (PSUs, GPUs, motherboards, CPUs, SSD/NVMe upgrades, and dozens of mechanical drives) and every major Windows version since Windows 8. This isn’t just an OS install; it’s a long‑running environment that has been stable and consistent for more than a decade. Losing it would be a significant disruption.

This failure was not caused by anything I did.

Windows attempted to upgrade me to 25H2 several times. Those upgrades failed, but the system continued running normally. Then Windows Update pushed a Servicing Preview LCU (build 26100.6725) to my machine even though I am not enrolled in the Insider Program. After a normal reboot — no update in progress — the system went straight to a black screen and a 0x21A stop code.

Since that reboot, Windows will only start if I go into Advanced Startup Options and choose “Disable driver signature enforcement.” If I don’t do that, it crashes with 0x21A every time.

After investigating:

• Windows RE is completely disabled — reagentc /info shows the GUID as all zeros.

The BCD recoverysequence is also zeroed out.

Secure Boot CI enforcement is off.

The CI/WinRE chain appears to have been removed during that reboot.

CI fails at boot unless DSE is manually disabled.

I did not modify anything manually.

This was triggered entirely by Windows Update.

This is not corruption or user error. This is a servicing failure caused by a preview update and a failed feature upgrade. My system was stable until Windows Update pushed a build it should never have offered.

I will be attempting a repair install using the 26100.1 GA ISO, but I need to know:

Why a retail system received a Servicing Preview LCU.

Why the CI/WinRE chain was removed on reboot.

Whether this is a known servicing failure pattern.

Whether any official remediation exists if the repair install does not restore CI/WinRE, short of wiping the system.

Given the age of this install and the severity of the failure, I am requesting direct engineering review from the CI/WinRE servicing team. This is not a typical support case — it’s a CI/WinRE servicing collapse triggered by Windows Update on a long‑running retail system.

I can provide logs, BCD output, WinRE state, and event viewer entries.

Please escalate this to the CI/WinRE servicing team.

Thanks.

Answer 1

Hello slick ochet,

Welcome to Microsoft Q&A forum.

Please note that this is a user-to-user support forum. Moderators, contributors including external Microsoft employees cannot directly intervene in Microsoft product features or access back-end systems. Our role is limited to providing technical guidance on reported issues, requests, or ideas. However, you can directly escalate this yourself using the Feedback Hub app.

Regarding your questions, I'd say an update might contribute to this, but I cannot be sure without looking at it directly, same goes with the Preview Update offer. Also, the easiest way to test now is using a repair install and see how much it can restore.

Thank you for your understanding.