Windows Update Information Sources: Release Health, Hotpatch Calendars and Known Issues

Below is that map, plus details from Microsoft's own documentation on licensing and role requirements, notification limits, hotpatch timing and some troubleshooting.

The quick decision guide​

Microsoft's guide starts with a lookup table. Here's the same mapping in one place:

The table is the main value of the guide. Most problems with Windows information come from asking the right question in the wrong place, not from missing information.

Windows release health: start here​

Microsoft points to Windows release health as the place to start when you need authoritative status information. It covers rollout status for each release, known and resolved issues, safeguard holds, servicing milestones and other details for managing a fleet of devices. It answers questions like:

• What are the latest updates and servicing milestones?
• How far along is a feature update rollout?
• Is there a known issue affecting this version, and has it been resolved?
• Is a safeguard hold keeping certain devices from getting a feature update?

Public view vs. admin-center view​

Release health exists in two versions, and they are not the same. When Microsoft brought release health into the Microsoft 365 admin center, it said that because the admin center is built for IT admins, you will find greater technical detail about known issues, earlier reminders about important milestones like end of service, and more resources to help you plan for and deploy Windows updates. Microsoft Learn's current FAQ says the same: the admin-center version may show more issues, diagnostic details, mitigation steps and root cause analysis than the public page on Learn.

To get there, sign in to the Microsoft 365 admin center with an admin account, then go to Health > Windows release health. If Health doesn't show up in the left-hand menu, expand it with "Show All."

Know the tabs​

Microsoft Learn describes three views:

• All versions (the default) lists Windows products with posted known issues.
• Known issues shows active issues plus those resolved in the last 30 days.
• History shows resolved issues from up to six months back.

Each issue summary shows the title, the affected version, the status, the originating KB and the originating build. You can search by KB number, build number or keyword. If you open a support case, the advisory ID (the letters "WI" followed by a number) appears under the issue title in the Details pane.

Status labels, decoded​

Microsoft uses a fixed set of statuses, and they mean different things for planning:

• Reported: Microsoft has been told about it, but hasn't confirmed users are affected.
• Investigating: believed to affect users; scope, mitigation and root cause are being worked on.
• Confirmed: Microsoft has determined users are affected.
• Mitigated / Mitigated: External: a workaround exists. "External" means a third-party driver or app caused the problem.
• Resolved / Resolved: External: a fix has shipped, from Microsoft (documented in a KB) or from a third party.

One caution from Microsoft's FAQ: release health does not monitor your environment or collect information about it. All known-issue content goes to all subscribed customers. A listing tells you where to look; it doesn't prove that your devices are affected. The FAQ also says admin-center content is for licensed customers and isn't meant to be shared publicly, so think before pasting it into a public forum thread.

Section summary: Use the public release health pages to see what's known. Use the admin-center version for deeper technical detail. Treat both as information about Windows in general, not monitoring of your tenant.

Release information and release notes​

Sometimes nothing is broken and you only need facts: which versions are supported, which build you're on, when a version reaches end of updates. Windows release information pages cover servicing status and update history for supported versions. Release notes cover what's in one specific monthly update. Every in-market version of Windows client and Windows Server has its own update history page listing all release notes published so far.

In short, release information answers "which version or build am I looking at?" and release notes answer "what changed in this update?"

The hotpatch caveat​

If your organization uses hotpatch, Microsoft points to two more resources: the Windows 11 hotpatch calendar on the Windows 11 release information page, and separate hotpatch release notes.

Microsoft's Intune documentation explains the pattern. Baseline months are January, April, July and October. Those updates include security fixes and cumulative features, and they need a restart. Hotpatch months are February–March, May–June, August–September and November–December. Those updates are security-only and don't need a restart.

There are exceptions, and they're where things go wrong:

• Missed baseline: In a hotpatch month, a device that isn't on the latest baseline gets both the baseline (restart required) and the hotpatch.
• Version upgrades: Upgrading a hotpatch-enrolled device to a new Windows version during a hotpatch month moves it to standard updates, with restarts, until the next baseline. Upgrading during a baseline month keeps it on the hotpatch cycle.
• Eligibility: Virtualization-based security must be running. Arm64 devices must also have CHPE disabled. Devices that don't qualify get the regular cumulative update instead.
• Cross-OS calendars: Microsoft notes that one OS can have extra baseline months while another is in hotpatch months. Check the release notes for your specific product rather than assuming one calendar fits everything.

Section summary: The calendar shows when updates are planned. Hotpatch release notes show what shipped. Your device's baseline status determines whether it can skip the restart.

Known issues and safeguard holds​

Microsoft suggests checking known issues in two situations: when something is behaving oddly, and as a routine step before any feature or monthly update deployment. The second habit is the more valuable one.

Safeguard holds need extra attention because they are often why a device silently isn't offered a feature update. According to Microsoft Learn, Windows Update for Business reports identifies safeguard holds by their 8-digit identifiers. For safeguard holds associated with publicly discussed known issues, you can find more details about the issue on the Windows release health dashboard by searching for the safeguard hold ID on the Known issues page for the relevant release. On unmanaged devices it's less clear: the Windows Update page in the Settings app displays a message stating that an update is on its way, but not ready for the device.

Subscribe to known-issue emails​

According to Microsoft Learn, the steps are:

1. Open Windows release health in the Microsoft 365 admin center.
2. Select Preferences > Email, then turn on email notifications about Windows release health.
3. Enter up to two email addresses per admin account and choose the Windows versions you care about.
4. Select Save. Changes can take up to eight hours to apply.

If one issue affects several versions you've selected, you get one email, not several.

"I don't see Windows release health." Common fixes​

• Licensing: Microsoft Learn lists Windows 10/11 Enterprise E3 or E5, or Education A3 or A5. These can come through some Microsoft 365 F3, E3, E5, A3 or A5 plans.
• Role: Most roles with "administrator" in the name work, including Helpdesk Administrator and Service Support Administrator.
• Cloud: Release health is available to GCC tenants but not to GCC High or DoD.
• Can't sign in at all: Check the Microsoft 365 service health status page for tenant sign-in problems.
• Mobile app: Microsoft says release health isn't in the Microsoft 365 Admin mobile app yet.
• Issue not listed: Microsoft says to go through your normal support channels.

For teams that want to automate this, Microsoft Learn says the Windows updates API in Microsoft Graph provides known-issue and product lifecycle data, including end-of-servicing dates. It's still on the beta endpoint.

Message center: the short-form channel​

Not every advisory needs a full article. The public Windows message center posts short notices about servicing, lifecycle milestones, known issues, upcoming changes and events. Admins with Microsoft 365 admin center access see Windows posts next to other Microsoft 365 services in the Microsoft 365 message center. Microsoft says those versions often include more detail on rollout timing, impact, recommendations and compliance.

To get a weekly digest that includes Windows, Microsoft's guide gives these steps:

1. In Message center, select Preferences.
2. On the Custom View tab, select the services you want to monitor, including Windows.
3. On the Email tab, select or add the address that should receive notifications.
4. Turn on the weekly digest for the services you selected, and include Windows.

You can also turn on same-day emails for major updates. Microsoft Learn's current documentation describes digest, major-update and data-privacy emails as separate checkboxes, and the exact labels vary between pages. Look for the purpose of each checkbox rather than matching the wording exactly.

Other details from the docs:

• Digests are on by default and go to your primary address. You can add up to two more addresses, separated by a semicolon.
• Digest emails are sent in English only, even though posts in the portal can be machine-translated.
• The Message center reader role lets someone read and share posts without other admin rights.
• Some roles have no Message center access at all, including Intune Service Administrator and Compliance Administrator. That can surprise endpoint teams.

@WindowsUpdate, now with more than links​

Microsoft says the @WindowsUpdate accounts on X and Bluesky are expanding beyond release announcements. They will also post guidance on monthly security update availability, release notes and videos, known issues, lifecycle milestones, changes that need action, and resources for deploying, securing and managing Windows. Microsoft describes the audience as developers and power users as well as IT pros.

Social feeds are good for alerts, but posts scroll away. Use them to learn that something happened, then confirm the details in release health or the documentation.

Blog for context, Learn for reference​

Microsoft draws a clear line here. The Windows IT Pro Blog explains why a change matters and how to plan for it. Microsoft Learn is the authoritative technical reference and is updated as things change. A blog post reflects what was true when it was published; the documentation is what you should keep coming back to.

If you're writing a runbook, base it on Learn, not on a blog post from eighteen months ago.

Videos and live expert sessions​

• Monthly Windows 11 release notes companion videos give a short overview of each month's update plus a tip.
• Ctrl + Manage covers what changed for IT admins in Windows management, why it matters and what to do next.
• Community events let you ask questions of the engineering and product teams behind Windows, Windows 365, Intune and Windows security. These include Windows Office Hours, Tech Community Live, Technical Takeoff and Ask Microsoft Anything sessions. To get notified about new events, sign in to the Tech Community and follow the Windows events page.

Bottom line​

None of these resources is new, and the guide doesn't announce a product. Its value is practical: it shows which channel answers which question.

A reasonable setup for most admins:

• Bookmark release health and check it before every deployment ring.
• Subscribe to known-issue emails for the versions you actually run.
• Include Windows in your Message center digest.
• Search safeguard hold IDs from Windows Update for Business reports on the Known issues page.
• Use Microsoft Learn as the reference for procedures.

Do you know which release health status your last update problem reached before it was fixed? Readers are welcome to share how they've set up their update-monitoring workflow in the forum.