Currently, there is a risk that a known problematic application version is unintentionally deployed to some devices after updates have been paused.
Scenario:
An application update is deployed.
Issues are detected in Ring 1 during testing.
Pause Updates is enabled in Patch My PC to stop further deployments.
A newer application version becomes available in Patch My PC while updates are paused.
Pause Updates is later disabled and the catalog is synchronized.
Patch My PC automatically deploys the previously paused and known faulty version to the remaining update rings.
Problem:
Even though the problematic version is already known, it cannot be excluded from deployment once updates are resumed.
As a result, some devices unnecessarily receive a broken version until the assignment is manually removed in Intune.
Proposed Improvement:
Add an option to mark a specific application version as skipped or blocked.
The skipped version is never deployed to any update ring
Existing clients remain on the last known working version
Newer versions can still be evaluated normally through the regular update ring process
Benefit:
This would improve update control and stability by preventing the rollout of known faulty versions, while still allowing controlled testing and deployment of newer releases.