Safeguard holds – Probable and known issues when updating or upgrading to Windows 11 from MS explained

The official upgrade to Windows 11 22H2 (22621) is imminent. Then Microsoft also gets active and makes a few contributions for the IT administrators about how the upgrade works and how errors can be prevented. But even for us “normal people” such a contribution is sometimes very interesting.

The current post is about Safeguard holds, probable issues and known issues and how to find and classify them. As we know, Microsoft distributes a Windows upgrade in waves. Computers are scanned for probable problems. Microsoft calls it “pattern mining”. It uses machine learning that can automatically recognize patterns to prevent an upgrade.

This includes problems caused by programs, drivers or connection problems to audio, etc. The problems reported by users are also used for this purpose. These are then classified as a “probable problem” and applied during scanning. If a base rate of 3% is exceeded, it can be classified as a “known problem” and, in the worst case, a “safeguard hold” follows. Delivery of the upgrade is prevented on these devices until the error has been evaluated and resolved. If the probable problem is classified as “False Positive”, it will no longer be applied during scanning.

For some, this should also later answer the question of why computer A has already received the upgrade to the new version of Windows 11 22H2 and computer B has not yet. This protection is of course important for the company computers. Provided that IT has also set up the computers in such a way that Microsoft can also carry out “pattern mining”.

An upgrade works a little differently than a security update, for example. This will be distributed to everyone. If there are problems here, a Known Issue Rollback (KIR) can help afterwards, or the distribution of the update is suspended.

If you want to read the whole post: techcommunity/safeguard-holds-with-the-windows-update

Windows 11 tutorials and help

[related_posts_by_tax taxonomies=”post_tag”]