Check patch levels now!
The certificates used by Windows devices to establish a trusted connection to Windows Update will expire on May 17, 2027, and June 19, 2027. Without the replacement certificates, a device will lose access to Windows Update after the respective date and will no longer receive updates.
Microsoft continues to deliver replacement certificates silently through the monthly security updates. Therefore, a currently patched and supported device requires no further action.
The catch lies with the stragglers. Devices with outdated patch levels or running an unsupported version slip through the cracks. The timing of the issue depends on the Windows version, which is why it's worth staggering the minimum requirements:
- Windows 11 25H2 and later: No action required.
- Windows 11 24H2 and Windows Server 2025: September 2025 security update or later before June 19, 2027.
- Other supported Windows 11 and Windows Server 2022 versions: July 2026 security update or later before June 19, 2027.
- Supported Windows 10 versions: July 2026 security update or later before June 19, 2027.
- Windows 10 Enterprise 2019 LTSC, Windows Server 2019, and 2016: July 2026 security update or later before May 17, 2027.
- Devices receiving updates via WSUS are not affected by this change.
Check patch status on individual devices
A quick query on the individual device shows you the version and the most recently installed updates. This is sufficient to quickly classify a suspicious client.
Get-ComputerInfo -Property OsName,OsDisplayVersion,OsBuildNumber,OsHardwareAbstractionLayer
Get-HotFix | Sort-Object InstalledOn -Descending |
Select-Object -First 5 HotFixID,Description,InstalledOnThe OsHardwareAbstractionLayer property returns the full build number including the revision, i.e., exactly the version you compare against the required minimum update.
Evaluating the Assets
You don’t need to check the patch level device by device across the fleet. If you’re in Intune, you can see via Windows Update for Business Reports which devices still don’t have the required minimum update. Using Graph PowerShell, you can pull the devices with their version and last sync to isolate the stragglers.
Connect-MgGraph -Scopes "DeviceManagementManagedDevices.Read.All"
Get-MgDeviceManagementManagedDevice -All -Filter "operatingSystem eq 'Windows'" |
Select-Object DeviceName,OSVersion,LastSyncDateTime |
Sort-Object OSVersion |
Export-Csv -Path .\windows-patchstand.csv -NoTypeInformation -Encoding UTF8For a straggler that missed the update, you retrieve the appropriate security update from the Microsoft Update Catalog and deploy it using your usual management tools. Devices on an unsupported version should be upgraded to a supported version first—otherwise, even the certificate won’t help.
The topic may be unspectacular, but it affects every fleet. Those who patch their clients and servers monthly anyway are on the safe side. The real work lies in tracking down the devices that haven't had a complete patch status for months.
further links
| Microsoft-Nachrichtencenter | https://mc.merill.net/message/MC1491763 |
| Windows-IT-Pro-Blog | https://techcommunity.microsoft.com/blog/windows-itpro-blog/vorbereitung-auf-die-zertifikatsrotation-fuer-windows-update-2027/4562463 |
💬 Comments
0 KommentareSei der Erste und starte die Diskussion mit einem hilfreichen Beitrag.
Leave a comment
Dein Beitrag wird vor der Veröffentlichung kurz geprüft — fachlich, respektvoll und auf den Punkt ist hier genau richtig.