Share via

Windows 11 not receiving feature updates from Intune

Edmore Muchabaiwa 0 Reputation points
2026-01-06T12:28:50.1266667+00:00

Issue: Windows 11 feature updates are not being offered or deployed via Intune, despite the device meeting all eligibility requirements and being properly managed. Quality updates are downloading and installing without issue.

All local troubleshooting has been exhausted.

Current Status:

• ✅ Device is Intune-managed, Azure AD joined, and compliant.

• ✅ Windows 11 hardware requirements are fully met.

• ✅ Intune policies are correctly assigned and configured.

• ✅ All Windows Update services are functional.

• ❌ Windows 11 feature updates do not appear in Windows Update scans.

Timeline of Issue:

Ongoing since at least November 11, 2025, with repeated failed update scans and no feature update detection.


🔍 2. Detailed Issue Description

The device is running Windows 11 23H2 and is targeted for an upgrade to Windows 11 24H2 via Intune Feature Update policies. Despite meeting all prerequisites:

• Windows Update scans return “0 updates” for feature updates.

• Quality updates download and install normally.

• No error codes are displayed; the update simply does not appear.

• The issue persists across multiple forced syncs, service resets, and policy refreshes.


📝 3. Troubleshooting Steps Completed

Phase 1: Initial Diagnostics & System Reset

Step Action Result

1.1 Full Windows Update reset (stopped services, renamed SoftwareDistribution & catroot2) Services reset, cache cleared – no change

1.2 Reset BITS and Windows Update service security descriptors Services restored – no change

1.3 DISM /Online /Cleanup-Image /RestoreHealth and sfc /scannow No component store corruption detected

1.4 Enabled detailed Windows Update logging via registry Logs captured – no errors in detection

Phase 2: Intune Policy Verification

Step Action Result

2.1 Verified Intune Update Rings policy – Windows 11 target enabled Policies correctly configured

2.2 Confirmed Feature Update profile for Windows 11 24H2 is active and assigned Profile assigned to correct device group

2.3 Checked compliance policies for update blocks No compliance blocks found

2.4 Forced Intune device sync via PowerShell and Settings Sync successful – no policy conflicts

Phase 3: Network & Group Policy Adjustments

Step Action Result

3.1 Attempted to set network to Private via PowerShell BLOCKED by Group Policy “Network List Manager Policies”

3.2 Applied registry fix: AllowDownloadsOverMeteredNetwork = 1 Registry updated – quality updates worked, feature updates still missing

3.3 Exported Group Policy results (gpresult /h) No conflicting Windows Update policies found

3.4 Reset network stack (winsock, IP reset) Network connectivity intact – no change

Phase 4: Advanced Diagnostics & Validation

Step Action Result

4.1 Verified Windows 11 eligibility (TPM 2.0, CPU, Secure Boot) Device fully eligible

4.2 Checked Intune Management Extension service Service running normally

4.3 Ran dsregcmd /status Device properly Azure AD joined

4.4 Forced update detection via usoclient StartScan and StartInstall Scans completed – no feature updates detected

4.5 Exported Windows Update event logs (last 50 events) Logs show successful quality update downloads, no feature update activity

4.6 Created and ran monitoring script for available updates Script returns “0 updates” for feature updates

Phase 5: Security & Service Health

Step Action Result

5.1 Checked Windows Defender status Defender services disabled – re-enabled post-troubleshooting

5.2 Verified no third-party AV conflicts No conflicts detected

5.3 Ensured no pending reboots or update holds System ready for updates

Windows for business | Windows 365 Business
0 comments No comments

1 answer

Sort by: Most helpful
  1. Harry Phan 20,535 Reputation points Independent Advisor
    2026-01-06T14:09:07.3733333+00:00

    Hello Edmore,

    From what you’ve documented, the device is fully compliant, Intune sync is clean, and there are no Group Policy or registry conflicts preventing updates. The fact that quality updates are downloading and installing but feature updates are not being offered points to the servicing channel configuration rather than a technical block. Windows 11 feature updates are controlled by Windows Update for Business policies in Intune, specifically the “Feature update deferral period” and “Feature update version” settings. If those are set to defer or lock the device to a particular release, the update scan will return zero feature updates even though the device is eligible.

    You should confirm in the Intune portal under Devices > Update rings for Windows 10 and later whether the ring assigned to this device has a deferral period configured or is pinned to a specific version. Also check if a Feature Update deployment profile is targeting the device, as those override the update ring and can hold the system at a given build. If neither is present, then the device is simply not being offered the feature update yet because Microsoft staggers rollout based on telemetry and safeguard holds. Safeguard holds are invisible in gpresult and Intune compliance, but they block feature updates until Microsoft clears the condition.

    At this point, the system is behaving as designed. If you need to force the upgrade, you can either assign a Feature Update deployment policy in Intune specifying the target Windows 11 build, or manually initiate the upgrade using the Windows 11 Installation Assistant or ISO. If you prefer to stay within Intune policy, the cleanest approach is to configure a Feature Update profile to the desired release and let the device pick it up.

    I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

    Harry.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.