Depending on the diagnosis, select the appropriate resolution.
The most benign cause: A previous deployment or sync is legitimately still running. Synchronizing a large catalog (e.g., all Windows 10/11 updates, Office updates, and third-party patches) can take hours. | Cause | Explanation | |-------|-------------| | |
| Cause | Explanation | |-------|-------------| | | A software update synchronization (e.g., syncing with Microsoft Update) may take 30+ minutes depending on product categories and update volume. | | Unclosed WSUS session | The WSUS server may hold a lock due to an improperly closed API connection from a previous operation. | | Multiple admin actions | Another administrator or automated script started a deployment, publish, or cleanup operation simultaneously. | | Stuck background job | A failed or stalled publish/deployment process never released the lock. | | UI vs. console conflict | In older ConfigMgr consoles, closing the console mid-operation doesn’t cancel the server-side job. | | | Stuck background job | A failed
When the SMS Executive service or WSUS application pool crashes, it may not release the mutex. The lock persists in memory or as a registry key, tricking the SUP into believing an operation is active. or cleanup operation simultaneously.