Forum Discussion
RDS stops responding after Sept. 2026 security updates
- Sep 26, 2026
Your symptoms match Microsoft’s documented September 2026 RDS issue from KB5123066, and Microsoft lists KB5129243 as the resolution. However, the repeated rollback plus DISM error 3017 means the machine now has an incomplete servicing transaction; it is no longer just an RDS configuration problem. Do not delete pending.xml, rename WinSxS, or force package removal, because those unsupported edits can make recovery harder. Preserve a VM checkpoint or backup and copy SQL backups and transaction logs to separate storage. Then open a Microsoft support case and provide CBS.log, DISM.log, the package-state output, rollback timestamps, and the release-health reference. Since this is a production Server 2012 R2 ESU system, the safest recovery path may be restoring the pre-update VM in isolation, applying the resolved update there, validating RDS and the application, and then recovering SQL data using the database procedure. KIR will not repair a servicing stack already stuck mid-transaction.
Your symptoms match Microsoft’s documented September 2026 RDS issue from KB5123066, and Microsoft lists KB5129243 as the resolution. However, the repeated rollback plus DISM error 3017 means the machine now has an incomplete servicing transaction; it is no longer just an RDS configuration problem. Do not delete pending.xml, rename WinSxS, or force package removal, because those unsupported edits can make recovery harder. Preserve a VM checkpoint or backup and copy SQL backups and transaction logs to separate storage. Then open a Microsoft support case and provide CBS.log, DISM.log, the package-state output, rollback timestamps, and the release-health reference. Since this is a production Server 2012 R2 ESU system, the safest recovery path may be restoring the pre-update VM in isolation, applying the resolved update there, validating RDS and the application, and then recovering SQL data using the database procedure. KIR will not repair a servicing stack already stuck mid-transaction.