If you’re seeing error 0x80246007 during Windows Update or Microsoft Store downloads, you’re dealing with a BITS transfer problem: Windows couldn’t download or stage the content it needs. This usually appears as “There were problems downloading some updates” or “Download error – 0x80246007,” and it’s critical to address because it blocks security patches, driver updates, and feature upgrades. This guide takes you beyond generic advice with structured, step‑by‑step troubleshooting, targeted health checks, and proven reset procedures to restore Background Intelligent Transfer Service (BITS) and Windows Update to full health.
————————————
Understanding the Error
What 0x80246007 means (plain language)
- 0x80246007 translates to WU_E_DM_NOTDOWNLOADED. Windows Update (or the Microsoft Store) asked the system to download content, but the download didn’t complete or couldn’t be found where expected.
- In practice, this often points to a BITS problem. BITS (Background Intelligent Transfer Service) is the Windows component that efficiently downloads updates and app content in the background. If BITS jobs are corrupt, the service is stopped, or networking/policy is blocking it, you’ll see errors like 0x80246007.
Typical scenarios
- Windows Update stuck at a percentage with 0x80246007 after a long wait.
- Microsoft Store apps failing to download or update with the same code.
- Updates fail repeatedly after a recent power outage, crash, or forced restart.
- Systems on VPN, proxy, or behind strict firewalls failing to download updates.
- Machines managed by WSUS/Intune receiving the scan list but not downloading content.
————————————
Quick Reference Table
| Cause | Symptom | Recommended Fix |
| — | — | — |
| BITS service stopped or misconfigured | Updates hang or error 0x80246007 | Start/verify BITS and dependencies; reset update components |
| Corrupted BITS job queue (qmgr.dat) | Repeated download failures | Delete qmgr.dat and reset BITS queue |
| Corrupt SoftwareDistribution or Catroot2 cache | Updates re-fail after each reboot | Rename SoftwareDistribution and Catroot2; rebuild |
| Proxy/VPN/firewall blocking | Error occurs only on corporate/VPN network | Reset WinHTTP proxy; bypass VPN; adjust firewall/AV |
| File system or component store corruption | SFC/DISM report errors | Run SFC and DISM; rerun update |
| Low disk space | Downloads never start/complete | Free up space (8–20 GB recommended for feature updates) |
| Incorrect date/time or TLS settings | “Couldn’t download updates” intermittently | Sync time; verify TLS/SSL; reset networking |
| Group Policy/WSUS misconfiguration | Enterprise devices won’t download | Review Windows Update/Delivery Optimization GPOs; reset WSUS client ID |
| Third-party antivirus/conflicts | Error appears with security suite alerts | Temporarily disable or uninstall conflicting tools |
| Network/DNS issues | Works on other networks but not this one | Flush DNS; change DNS; reset Winsock/WinHTTP |
————————————
Common Causes
- BITS not running or failing to start:
- Service disabled, stuck, or blocked. Dependencies like RPC must be healthy.
- Corrupted download queues:
- Damaged BITS job databases (qmgr*.dat) or corrupted Windows Update caches.
- Network configuration problems:
- Misconfigured WinHTTP proxy, restrictive firewall, VPN split-tunneling issues, or captive portals.
- Damaged system files:
- Corruption in the Windows component store or file system causes downloads and servicing to fail.
- Storage constraints:
- Insufficient free space for update payloads and temporary files.
- Policy and management issues:
- Group Policy or WSUS/MDM settings that inadvertently block downloads or throttle BITS excessively.
- Security software interference:
- Aggressive antivirus/EDR or filtering proxies terminating background downloads.
- Date/time and certificate issues:
- Out-of-sync system clock or SSL/TLS inspection breaking secure update channels.
————————————
Preliminary Checks
Boot to Safe Mode (if downloads consistently fail or you suspect conflicts)
- Windows 10/11:
- Start > Settings > System (or Update & Security) > Recovery > Advanced startup > Restart now.
- Troubleshoot > Advanced options > Startup Settings > Restart.
- Press F5 for Safe Mode with Networking.
- Or, from an elevated Command Prompt: bcdedit /set {current} safeboot network (remember to undo later with bcdedit /deletevalue {current} safeboot).
Back up important data
- Before deeper repairs, ensure your files are backed up (local copy or cloud). Resetting update components is safe, but general best practice is to have a backup.
Run basic health checks
- File system check (read-only online scan):
- Open an elevated Command Prompt and run:
chkdsk C: /scan
- Open an elevated Command Prompt and run:
- System file check:
- In an elevated Command Prompt:
sfc /scannow
- In an elevated Command Prompt:
- Component store health:
- In an elevated Command Prompt:
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
- In an elevated Command Prompt:
If SFC/DISM report fixes, reboot, then try Windows Update again.
————————————
Step-by-Step Troubleshooting
Follow these from easiest to most advanced. Test updates after each major step.
- Confirm time, space, and network basics
- Sync time and date:
- Elevated CMD:
w32tm /resync
- Elevated CMD:
- Free disk space:
- Keep at least 8–10 GB free for cumulative updates; 20 GB+ for feature updates.
- Test network:
- Temporarily disconnect VPN, try a different network or hotspot, and pause any bandwidth-heavy apps.
- Verify and restart core update services
-
In an elevated Command Prompt:
net stop bits
net stop wuauserv
net stop cryptsvc
net stop msiservernet start cryptsvc
net start bits
net start wuauserv
net start msiserver -
Or in PowerShell (Admin):
Get-Service BITS, wuauserv, cryptsvc, msiserver | Format-Table -Auto
Start-Service BITS, wuauserv, cryptsvc, msiserver
- Reset the Windows Update components and rebuild the BITS queue
-
Elevated Command Prompt:
net stop bits
net stop wuauserv
net stop cryptsvc
net stop msiserverDel /f /q “%ALLUSERSPROFILE%\Microsoft\Network\Downloader\qmgr*.dat”
Ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
Ren %systemroot%\System32\catroot2 Catroot2.oldnetsh winhttp reset proxy
netsh winsock reset
ipconfig /flushdnsnet start cryptsvc
net start bits
net start wuauserv
net start msiserver -
PowerShell alternative to clear BITS jobs:
Get-BitsTransfer -AllUsers | Remove-BitsTransfer -Confirm:$false
- Run the Windows Update troubleshooter
- Windows 10/11: Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run.
- It automatically checks BITS and Update components and applies known fixes.
- Repair the servicing stack and system files again
- Elevated Command Prompt:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow - Reboot and try updates.
- Re-register key Windows Update and BITS components (advanced)
- Elevated Command Prompt (silent registrations):
regsvr32.exe /s qmgr.dll
regsvr32.exe /s qmgrprxy.dll
regsvr32.exe /s wuapi.dll
regsvr32.exe /s wuaueng.dll
regsvr32.exe /s wups.dll
regsvr32.exe /s wups2.dll
regsvr32.exe /s wuwebv.dll
regsvr32.exe /s wucltux.dll
regsvr32.exe /s atl.dll
regsvr32.exe /s urlmon.dll
regsvr32.exe /s mshtml.dll
regsvr32.exe /s jscript.dll
regsvr32.exe /s vbscript.dll
regsvr32.exe /s msxml3.dll
regsvr32.exe /s softpub.dll
regsvr32.exe /s wintrust.dll
regsvr32.exe /s cryptdlg.dll
regsvr32.exe /s oleaut32.dll
regsvr32.exe /s ole32.dll - Note: Some DLLs may already be registered; no harm in re-registering.
- Check and fix proxy/VPN/firewall interference
- Show current WinHTTP proxy:
netsh winhttp show proxy - Reset proxy:
netsh winhttp reset proxy - If you use a corporate proxy:
- Ensure bypass for Windows Update endpoints or test off the corporate network.
- Temporarily disable third-party antivirus/firewall (or enable “allow Microsoft Update”). If disabling fixes it, add exclusions or update the security suite.
- Inspect Event Viewer for targeted clues
- Event Viewer > Applications and Services Logs > Microsoft > Windows > BITS-Client > Operational:
- Look for warnings/errors around the time of failure (IDs commonly 16392–16398).
- Event Viewer > Applications and Services Logs > Microsoft > Windows > WindowsUpdateClient > Operational:
- Errors with 0x80246007 or download failures point to queue/cache issues.
- If you see Access Denied or TLS errors, focus on permissions/security software or SSL inspection.
- Reset Windows Update client identity (WSUS/enterprise scenarios)
- Only if domain-managed and you suspect a stale WSUS identity (consult your IT policy).
- Elevated Command Prompt:
net stop wuauserv
REG DELETE “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate” /v AccountDomainSid /f
REG DELETE “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate” /v PingID /f
REG DELETE “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate” /v SusClientId /f
net start wuauserv
wuauclt /resetauthorization /detectnow
UsoClient StartScan - Then check for updates again.
- Update network adapter drivers and disable NIC power saving
- Device Manager > Network adapters > your adapter > Update driver.
- Power Management tab: uncheck “Allow the computer to turn off this device to save power.”
- For laptops: set power plan to Balanced/Best performance during updates.
- Clean boot to eliminate third-party conflicts
- msconfig > Services tab > Hide all Microsoft services > Disable all.
- Startup tab > Open Task Manager > Disable all startup items.
- Reboot, try updates. If it works, re-enable items in batches to find the culprit.
- In-place repair upgrade (last resort software fix)
- Download the latest Windows 10/11 ISO (Media Creation Tool) from Microsoft.
- Run setup.exe from within Windows and choose “Keep personal files and apps.”
- This refreshes Windows components while preserving data and installed programs.
Notes for Microsoft Store manifestations of 0x80246007
- Reset the Store cache:
wsreset.exe - In Settings > Apps > Microsoft Store > Advanced options:
- Repair, then Reset (you’ll need to sign in again).
- Ensure Delivery Optimization (DoSvc) is running: Services > Delivery Optimization > Start.
————————————
Minidump Analysis (Context and When It’s Relevant)
This specific Windows Update error 0x80246007 is not a BSOD, so Windows will not generate a minidump for it. However, if your system is also crashing with blue screens while trying to update, you can collect dumps to diagnose the underlying driver/hardware problem.
How to enable/find minidumps
- Control Panel > System > Advanced system settings > Startup and Recovery > Settings.
- Under Write debugging information, select “Small memory dump (256 KB).”
- Dumps are stored in C:\Windows\Minidump.
Using BlueScreenView or WinDbg
- BlueScreenView: Quickly lists affected drivers/modules at the time of crash.
- WinDbg (Microsoft Store: WinDbg Preview): Open dump, run:
!analyze -v
lm
kv - If crashes implicate storage, networking, or security drivers used during updates, update or roll them back accordingly before retrying updates.
————————————
Advanced Diagnostics
BITS administration and monitoring
- List and remove all BITS jobs (PowerShell as Admin):
Get-BitsTransfer -AllUsers | Format-Table -Auto
Get-BitsTransfer -AllUsers | Remove-BitsTransfer -Confirm:$false - Deprecated but still handy (CMD):
bitsadmin /list /allusers /verbose
bitsadmin /reset /allusers
Generate WindowsUpdate.log (Windows 10/11)
- PowerShell (Admin):
Get-WindowsUpdateLog - This compiles logs to Desktop; search for 0x80246007 and related download errors.
Event Viewer deep dive
- BITS-Client Operational log:
- Errors about transient errors, job cancellation, or access issues help pinpoint network or permission problems.
- WindowsUpdateClient Operational log:
- Look for download failures, service resets, or policy blocks.
Network tracing (advanced)
- Capture update traffic to validate proxy/firewall behavior:
netsh trace start capture=yes scenario=InternetClient maxsize=512
Reproduce the issue, then:
netsh trace stop - Analyze the ETL with Microsoft Message Analyzer successor tools or Wireshark for TLS/HTTP failures.
Driver Verifier (only if you are also seeing BSODs)
- Use Driver Verifier cautiously; it can induce BSODs to reveal faulty drivers.
- Launch:
verifier.exe - Choose “Create standard settings” > “Automatically select unsigned drivers” or “drivers built for older versions of Windows.”
- Reboot; if you hit a BSOD, use minidumps to identify the offending driver. Turn off with:
verifier /reset
————————————
Post-Fix Checklist
- Run Windows Update “Check for updates” and confirm downloads progress without 0x80246007.
- Event Viewer:
- WindowsUpdateClient and BITS-Client show no new errors during download attempts.
- Re-run health checks:
- sfc /scannow
- DISM /Online /Cleanup-Image /ScanHealth
- Verify services:
- BITS startup type: Manual (Delayed Start); status: Running on demand.
- Windows Update and Cryptographic Services running as expected.
- Microsoft Store can download and update apps normally.
- If on enterprise network, confirm with IT that proxy/WSUS policies are correct and no blocks were introduced.
————————————
When to Seek Professional Help
- Updates fail even after an in-place repair, and SFC/DISM repeatedly find corruption.
- Storage device shows SMART errors or frequent I/O timeouts in Event Viewer.
- The system crashes during updates with repeated BSODs implicating drivers you cannot update or replace.
- You’re in a managed environment (domain/WSUS/Intune) and policies are blocking downloads—coordinate with your IT administrator.
- You suspect malware or rootkits interfering with network traffic or update components.
————————————
Prevention Tips
- Keep drivers and firmware current, especially chipset, storage (SATA/NVMe), WLAN/LAN, and BIOS/UEFI.
- Maintain free disk space; clean up old Windows installations and temporary files periodically.
- Avoid “registry cleaners” or aggressive system tweakers that tamper with BITS, SoftwareDistribution, or cryptographic stores.
- Use reliable, updated antivirus; configure it to allow Windows Update and Delivery Optimization traffic.
- If you rely on a proxy or VPN, configure exceptions for Microsoft Update endpoints and test updates off-VPN when possible.
- Back up regularly (system image + files) so you can recover quickly if an update goes wrong.
- Monitor health: occasionally run SFC and DISM, and watch Event Viewer for early signs of servicing issues.
————————————
Conclusion
Error 0x80246007 is a Windows Update download failure commonly tied to BITS transfer problems, cache corruption, or network/policy blocks. In most cases, a structured approach—health checks, resetting update components and the BITS queue, fixing proxy and DNS settings, and verifying services—quickly restores normal operation. If deeper corruption or policy issues are involved, advanced diagnostics and, if necessary, an in-place repair will get you back on track. Stay systematic, test after each step, and you’ll resolve 0x80246007 in the majority of cases.
————————————
FAQ
What is Windows Update error 0x80246007?
It’s a download-related error (WU_E_DM_NOTDOWNLOADED) indicating Windows couldn’t complete or locate the downloaded update payload, often due to BITS issues, cache corruption, or network/proxy interference.
Is it safe to delete SoftwareDistribution and qmgr*.dat?
Yes. Renaming SoftwareDistribution and deleting qmgr*.dat (after stopping services) are standard, safe resets. Windows rebuilds these caches automatically on the next update attempt.
Will resetting BITS and Windows Update erase my files or apps?
No. These resets affect update caches and job queues only. Your personal files and installed applications are not touched.
Why does 0x80246007 appear only on my work network or VPN?
Corporate proxies, SSL inspection, or strict firewalls can block update content or background transfers. Reset WinHTTP proxy, test off VPN, and coordinate with IT to allow Microsoft Update and Delivery Optimization endpoints.
I’m still getting 0x80246007 after all steps—what next?
Run an in-place repair upgrade to refresh Windows components while keeping your apps and files. If that fails, suspect hardware (disk/network) or enterprise policy conflicts and seek professional/IT assistance.
You’ve got this. With the health checks and resets above, most BITS transfer issues and 0x80246007 errors can be cleared and updates will flow normally again.
