Windows not upgrading from 23H2 to 24H2 Enterprise done the following troubleshootings but still no luck.

Ranjith U 75 Reputation points
2026-09-22T11:00:06.79+00:00

Checked the following and all set as expected, any recommendations would be helpful.

Facing this issue on multiple device, Microsoft Intune is the patching tool with feature update rolledout as required - Immediate. Thanks

  • Telemetry Check: No issues were identified.
  • Telemetry Registry Setting: Verified the following registry path: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DataCollection
    • AllowTelemetry: Set to 1.
  • Windows Update Service: Service was stopped and restarted successfully without any issues.
  • BITS Service: Service was stopped and restarted successfully without any issues.
  • Windows Update Cache: The following cache folders were renamed successfully, with no issues identified:
    • C:\Windows\SoftwareDistribution\SoftwareDistribution
    • C:\Windows\System32\catroot2\catroot2
  • Registry Target Version: Configured as required under: HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
  • Target Feature Update: Configured as required under: HKLM:\SOFTWARE\Microsoft\PolicyManager\current\device\Update
    • Target version: 24H2
  • Windows Update Sync: No issues were identified.
  • Windows Updates: The latest monthly and current-month patches have been successfully installed.
  • Autopatch Profile: Confirmed that the device has received the appropriate Autopatch profile and is not pointing to SCCM/WSUS.
  • GPO Validation: No Group Policy restrictions or blocks were identified.
  • Intune Feature Update Policy: No conflicting Feature Update policies were identified in Intune.
  • Hardware Compatibility: The device hardware has been validated as compatible with Windows 24H2.
  • Driver Validation: No driver updates are required for this specific device model.
  • Custom Drivers: No specific custom drivers need to be manually pre-installed for the Windows 24H2 upgrade on the affected device.

Regards,

Ranjith

Windows for business | Windows Client for IT Pros | Devices and deployment | Install Windows updates, features, or roles
0 comments

3 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Jason Nguyen Tran 27,210 Reputation points Independent Advisor
    2026-09-29T05:55:27.7366667+00:00

    I’m following up to check whether the issue has been resolved. Feel free to reply if you need further information. If the information provided was helpful, please click "Accept Answer" to help others in the community. Thank you!

    Was this answer helpful?

    0 comments
  2. Jason Nguyen Tran 27,210 Reputation points Independent Advisor
    2026-09-22T11:55:56.65+00:00

    Hello Ranjith,

    Based on everything you've already validated, you've covered most of the common configuration and policy-related causes that would prevent a 23H2-to-24H2 upgrade. Since the issue is occurring across multiple devices and Intune Feature Update policies appear to be configured correctly, I would recommend focusing on Windows Update for Business deployment safeguards and upgrade compatibility holds.

    A key next step is to check the Windows Update logs and the Update Compliance reports for any safeguard hold IDs or compatibility blocks. Even when hardware meets the published requirements, Microsoft may temporarily block 24H2 on specific device models, drivers, applications, or configurations until compatibility issues are resolved. You can also review Event Viewer > Applications and Services Logs > Microsoft > Windows > WindowsUpdateClient and Setup logs for any feature update evaluation failures.

    Additionally, please run SetupDiag on an affected device and review the output for hidden upgrade blockers. I would also check whether the devices are reporting a safeguard hold by running Get-WindowsUpdateLog and reviewing the Update Orchestrator entries. If the devices successfully scan against Windows Update but never receive the feature update offer, that is often a sign of a compatibility hold rather than an Intune policy issue.

    As a validation step, try performing an in-place upgrade manually using the Windows 11 24H2 installation media on one affected device. If the manual upgrade is blocked, the setup logs will usually reveal the exact reason. If the manual upgrade succeeds, then you can narrow the investigation to the Windows Update for Business deployment process.

    I hope the response provided some helpful insight. If you find this answer useful, please hit “accept answer” so I know it addressed your concern.

    Jason

    Was this answer helpful?

    0 comments

  3. AI answer

    2026-09-22T11:00:27.9766667+00:00

    Given the checks already completed, the next supported path is to verify whether a compatibility safeguard hold or app/driver compatibility risk is preventing 24H2 from being offered or installed.

    1. Check for a safeguard hold on the device.
      • On Home or Pro devices, open Settings > Windows Update and review any Learn more message shown there.
      • For managed environments, check Windows Update for Business reports for safeguard holds.
      • One known 24H2 safeguard is for devices with the sprotect.sys driver. Affected devices are not offered Windows 11, version 24H2 through Windows Update. For admins using Windows Update for Business reports, this issue is tracked as safeguard ID 56318982.
    2. In Intune, review device readiness and compatibility risk data.
      • Open the Windows feature update device readiness report.
      • Check the device’s Readiness status, Sys req issues, App issues, and Driver issues.
      • Open the device details and review the Applications, Drivers, and Other tabs. The Other tab can include compatibility risks tied to device configuration or settings, including some safeguard holds.
    3. In Intune, review the compatibility risks report for blocking items.
      • If an app is marked The application isn't compatible with the new OS version and will block the upgrade, remove that application before upgrading.
      • If a driver is marked Driver won't migrate to new OS, check with the hardware vendor or OEM for a compatible driver, or allow Windows Update to install a newer driver during upgrade when applicable.
      • If an app is marked May block upgrade, test application, validate it during upgrade and remove it if it blocks the process.
    4. Confirm the device is scanning the correct update service.
      • Since Autopatch and Intune policy look correct, verify the device is scanning Windows Update and not another endpoint such as WSUS, because scanning a different endpoint can result in different update behavior.
    5. If the issue is specifically with expedited quality updates, verify Microsoft Update Health Tools is installed.
      • The documented install path is C:\Program Files\Microsoft Update Health Tools.
      • It can also be checked with: 
             Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -Match "Microsoft Update Health Tools"}
      • This is required for a device to receive an expedited quality update.
    6. If 24H2 is being offered but installation stalls or fails late in setup, check basic upgrade prerequisites.
      • Ensure free disk space meets the documented minimum: 16 GB for 32-bit OS or 20 GB for 64-bit OS.
      • If installation gets stuck between 51% and 99%, run Check for updates again or run the Windows Update Troubleshooter.
    7. If no compatibility risk or safeguard is identified, collect support data.
      • Collect logs using TSS for deployment-related issues before escalating.

    Important: if a safeguard hold applies, do not try to force 24H2 with the Windows 11 Installation Assistant or media creation tool until the hold is resolved.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.