This guide walks you through troubleshooting Windows quality updates that remain stuck in a “Pending” state in Microsoft Intune. You’ll learn the most common causes, step-by-step fixes, and how to prevent the issue from recurring. Before you start, ensure you have Intune admin access and local administrator rights on the affected device.
What You’ll Need
- Intune admin credentials (to review update policies and device status)
- Local administrator access on the Windows device showing the pending update
- Internet connection on the device (to download updates and reach Windows Update)
- Optional: a second device for testing if the issue is widespread
Step-by-Step
- Verify the update is actually pending. In the Intune admin center, go to Devices > Windows > Updates. Select the affected device and check the “Quality updates” tab. Note the exact update KB number and the “Last check” timestamp. If the device hasn’t checked in recently, that’s the first problem.
- Force a sync from the device. On the Windows device, open Settings > Accounts > Access work or school. Select the Intune enrollment entry and click Info, then Sync. Wait 5–10 minutes and re-check Intune. This often clears a stuck pending state caused by a missed check-in.
- Run the Windows Update troubleshooter. On the device, go to Settings > System > Troubleshoot > Other troubleshooters. Run Windows Update. Allow it to apply fixes and restart if prompted. Then force another sync.
- Check the Windows Update service state. Press Win + R, type
services.msc, and press Enter. Ensure these services are running (not disabled): Windows Update, Cryptographic Services, Background Intelligent Transfer Service (BITS), and Windows Installer. If any are stopped, right-click and select Start. Set their startup type to Automatic (or Automatic (Delayed Start) for BITS). - Clear the SoftwareDistribution folder. Stop the Windows Update service (from step 4), then open File Explorer and delete the contents of
C:\Windows\SoftwareDistribution\Download. Also clearC:\Windows\SoftwareDistribution\DataStore(optional, but helps). Restart the Windows Update service and re-sync. - Check for disk space. Quality updates require several GB of free space. Open This PC and verify the C: drive has at least 10 GB free. If not, run Disk Cleanup (search “Disk Cleanup” in Start, select C:, and remove temporary files).
- Review Intune update ring settings. In Intune, go to Devices > Windows > Update rings. Open the ring that applies to the device. Check that “Quality update deferral period” is not set to a high number (e.g., 30 days). Also verify that “Feature update deferral” doesn’t block quality updates. Lower the deferral temporarily if needed.
- Check for conflicting policies. If you have multiple update rings or Windows Update for Business policies, a device might receive conflicting instructions. In Intune, use Devices > Windows > Updates > Update rings and look at the “Conflicts” tab for the device. Remove or consolidate any overlapping policies.
- Manually install the update as a test. Download the specific KB from the Microsoft Update Catalog (search for the KB number). Run the standalone installer on the device. If it installs successfully, the issue is with Intune’s delivery, not the update itself. If it fails, the problem is local (e.g., corrupted system files).
- Run DISM and SFC. Open Command Prompt as administrator. Run
DISM /Online /Cleanup-Image /RestoreHealthand wait for completion. Then runsfc /scannow. Restart and re-sync. These tools repair corrupted Windows components that can block updates. - Reboot twice. Sometimes a simple double-restart clears stuck update states. After the first restart, wait 5 minutes, then restart again. Then force a sync.
- If all else fails, re-enroll the device. In Intune, delete the device from Devices > Windows > Windows devices. On the device, go to Settings > Accounts > Access work or school, select the account, and click Disconnect. Then re-enroll by signing in with your work account. This is a last resort but often resolves persistent update issues.
Common Mistakes
- Not checking the device’s last check-in time. If the device hasn’t synced for days, the pending status is just stale data. Always force a sync first.
- Deleting the entire SoftwareDistribution folder. Only delete the Download and DataStore subfolders. Deleting the root folder can break Windows Update permanently.
- Ignoring disk space. Many devices fail updates silently due to low storage. Always check free space before deep troubleshooting.
- Running multiple update rings. Overlapping policies cause conflicts that leave updates pending indefinitely. Simplify to one ring per device group.
- Skipping the manual install test. This step distinguishes between an Intune delivery issue and a local Windows problem. Skipping it wastes time.
Tips
- Set a regular sync schedule for devices (e.g., daily) to avoid stale pending states.
- Use Intune’s “Reports” to monitor update compliance and spot devices that haven’t checked in.
- Keep the Windows Update service startup type as Automatic – many third-party “optimizers” disable it, causing this exact issue.
- If you have a test device, apply the update ring there first to catch policy errors before rolling out broadly.
- Document any manual fixes you apply – they often recur after major Windows feature updates.
Troubleshooting
If the steps above don’t clear the pending state, try these additional checks:
- Check the Windows Update log. On the device, open Event Viewer (
eventvwr.msc) and navigate to Windows Logs > System. Filter for source “WindowsUpdateClient”. Look for error codes like 0x80070005 (access denied) or 0x800f081f (missing files). Search the error code online for a specific fix. - Verify network connectivity. Some corporate networks block Windows Update endpoints. Test by temporarily connecting to a mobile hotspot and forcing a sync. If it works, the issue is network filtering – work with your IT team to allow the required URLs.
- Check for third-party antivirus interference. Some security software blocks update installation. Temporarily disable the antivirus (if allowed) and try the manual install. If it succeeds, add an exception for Windows Update.
- Use the Windows Update Assistant. Download and run the official Windows Update Assistant from Microsoft’s website. It can force-install the latest quality update even when Windows Update is stuck.
- Reset Windows Update components manually. If the troubleshooter didn’t help, run the following commands in an elevated Command Prompt:
net stop wuauserv,net stop bits,ren C:\Windows\SoftwareDistribution SoftwareDistribution.old,net start wuauserv,net start bits. Then re-sync. - Check for pending reboots. Sometimes a pending reboot from a previous action blocks new updates. Restart the device fully and wait 10 minutes before re-syncing.
Frequently Asked Questions
Why does Intune show a quality update as pending when it’s already installed?
This is usually a reporting lag. The device hasn’t synced its status back to Intune yet. Force a sync from the device and wait 15 minutes. If it still shows pending, check the installed updates list on the device to confirm the KB is actually present.
How long should a quality update stay pending before I intervene?
Typically, a device should download and install a quality update within 24–48 hours of the update being released. If it’s been more than 3 days and the status hasn’t changed, start troubleshooting. Some deferral periods can extend this, so check your update ring settings first.
Can I force a quality update installation from Intune?
Intune doesn’t have a “force install” button for quality updates. You can only set deadlines via update rings. However, you can manually install the update on the device (as described in step 9) and then sync the status to Intune.
What does the “Pending” status mean exactly?
It means Intune has identified that the device needs the update, but the device hasn’t reported back that it has downloaded or installed it. The update may still be downloading, waiting for a restart, or blocked by an error.
Will restarting the device break anything?
No, restarting is safe and often necessary. Quality updates require a reboot to complete installation. If the device has been on for weeks, a restart might be the only fix needed. Just ensure no critical work is in progress.
Why does the update fail on some devices but not others?
Differences in installed software, disk space, or corrupted system files are common causes. Also, devices in different update rings may have different deferral settings. Use the manual install test to isolate whether it’s a device-specific issue.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Google Photos Backup Stuck? Fixes That Work
- Record Your Own Alarm Sound on Android
- Transfer Music from ZTE to iPhone: Full Guide
- Ways to Open Task Manager in Windows 10
- Convert Live Photos to Still Photos on iPhone
- Angel Investor vs Venture Capitalist: Key Differences