Where Is the Windows Pending Servicing Queue?
Pending servicing operations queue in Pending.xml, the file behind update reverts and reboot loops.
Last updated
Windows queues servicing operations in an XML file that tracks every pending install, removal, and transaction. Update reverts and reboot loops both start with this queue.
The file is write-only in practice. Reading it confirms which update wedged, but editing it by hand breaks the transaction log further. DISM and the update troubleshooter exist precisely because this file must only change through servicing itself.
Where Windows stores this, by platform
C:\Windows\WinSxS\pending.xml
Pending servicing transaction queue. Read to identify wedged updates, but repair with DISM rather than hand edits. Admin rights required.
Frequently asked questions
An update is stuck reverting. What do I check?
Read it only to confirm what servicing planned, then repair with DISM and SFC. Hand-editing the queue corrupts it further; the supported fix is completing or reverting the operation.
Notice an outdated path? Let us know.