Skip to content

Windows Known Issues Affecting Our Builds

The question it answers: Which active Windows release-health known issues affect Windows versions running in the fleet?

Microsoft’s Windows release-health known issues (the ones behind update safeguard holds), matched to the Windows versions running in your fleet. An active issue on a version you run explains helpdesk calls after Patch Tuesday before anyone has to troubleshoot.

Where in the appIntune › Endpoint Security & Readiness › Windows Known Issues
WorkloadIntune
KindTable
DataBuilt from the tenant data IntensiveReports keeps in memory and refreshes in the background, so it opens at once.
LicenceWindows Enterprise E3/E5 (or equivalent) for the Windows Update deployment service.
Report id (API and MCP)intune.endpoint.windows-known-issues
ColumnKeyType
IssueTitleLink
StatusStatusStatus
Windows versionProductNameText
Our devicesFleetDevicesText
ReportedStartDateTimeDate
UpdatedLastUpdatedDateTimeDate
ResolvedResolvedDateTimeDate
IdIdText
FilterKey (API)On when the page opens
Only active issues on versions we runactive-oursYes

Licence: Windows Enterprise E3/E5 (or equivalent) for the Windows Update deployment service.

Application permissions on the IntensiveReports app registration (all permissions):

PermissionAPIWhat it allowsNote
WindowsUpdates.Read.AllMicrosoft GraphRead all Windows update deployment settings
DeviceManagementManagedDevices.Read.AllMicrosoft GraphRead Microsoft Intune devices
Data sources it reads
  • GET /beta/admin/windows/updates/catalog/entries (quality updates)
  • GET /beta/admin/windows/updates/products/FindByCatalogId(catalogID='...')?$expand=knownIssues
GET /ir-api/v1/reports/intune.endpoint.windows-known-issues?size=100
GET /ir-api/v1/reports/intune.endpoint.windows-known-issues?filter=active-ours

An AI assistant reads it with the MCP tool get_report and the id intune.endpoint.windows-known-issues. The client needs the Read grant for Intune. See Using the API.