Fix Stub Received Bad Data Error in Windows 10

The “stub received bad data” error in Windows 10 typically appears when a program tries to access a system service or driver and the data returned is corrupted or malformed. The most reliable fix is to run the System File Checker (SFC) and DISM tools, then re-register the Windows Runtime components; if that fails, a clean boot or a repair install usually resolves it.

What Causes the Stub Received Bad Data Error?

This error is a generic Windows error code (0x8007000D) that means a data packet was malformed or corrupted during a system call. It commonly occurs in these scenarios:

• When launching or updating Microsoft Store apps (especially Mail, Calendar, or Photos).
• During Windows Update installation or when checking for updates.
• When using certain third-party software that hooks into system services (antivirus, VPN, or driver updaters).
• After a recent Windows update, driver update, or system restore that left files in an inconsistent state.

The underlying cause is almost always corrupted system files or a broken Windows component store, not a hardware failure. The error can also appear if a third-party program is interfering with Windows services, or if the Windows Update database is damaged.

How to Fix It: Step-by-Step Methods

Try these fixes in order. They range from least to most invasive, and most users resolve the issue with the first or second method.

Method 1: Run System File Checker (SFC) and DISM

1. Right-click the Start button and select Command Prompt (Admin) or Windows PowerShell (Admin).
2. Type sfc /scannow and press Enter. Wait for the scan to complete (may take 15-30 minutes).
3. If SFC finds issues but cannot fix them, run DISM: type DISM /Online /Cleanup-Image /RestoreHealth and press Enter.
4. Restart your PC and try the operation that triggered the error again.

If SFC reports that it found corrupt files but was unable to fix some, running DISM first then SFC again often completes the repair.

Method 2: Re-register Windows Store Apps

If the error appears when using Store apps, re-registering them often helps:

1. Open PowerShell as Administrator.
2. Type Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} and press Enter.
3. Wait for the command to finish (it may take a few minutes). Restart your PC.

This command re-registers all built-in Windows apps without deleting your data.

Method 3: Perform a Clean Boot

A clean boot starts Windows with a minimal set of drivers and startup programs. This helps identify if a third-party service is causing the error.

1. Press Win + R, type msconfig, and press Enter.
2. On the Services tab, check Hide all Microsoft services, then click Disable all.
3. On the Startup tab, click Open Task Manager, disable all startup items, then close Task Manager.
4. Click OK and restart your PC. If the error disappears, enable services one by one to find the culprit.

After identifying the problematic service, keep it disabled or update/uninstall the related software.

Method 4: Reset Windows Update Components

If the error occurs during Windows Update, resetting the update components often resolves it:

1. Open Command Prompt as Administrator.
2. Stop the Windows Update services by typing these commands one by one, pressing Enter after each:
   net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
3. Rename the SoftwareDistribution and Catroot2 folders:
   ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 Catroot2.old
4. Restart the services with:
   net start wuauserv
net start cryptSvc
net start bits
net start msiserver
5. Restart your PC and try Windows Update again.

Method 5: Repair Install (In-Place Upgrade)

If none of the above work, a repair install reinstalls Windows while keeping your files, settings, and installed apps. You need the Windows 10 Media Creation Tool:

1. Download the Media Creation Tool from Microsoft’s website.
2. Run it and choose Upgrade this PC now.
3. Follow the prompts; choose to keep personal files and apps when asked.
4. The process takes about an hour and will replace all system files with fresh ones.

This is the most thorough fix short of a full reset, and it resolves most persistent system file corruption issues.

What to Do If the Error Persists

If you’ve tried all the above and the error still appears, consider these additional steps:

• Check for pending Windows updates and install them manually.
• Run a disk check (chkdsk /f /r in Command Prompt as Admin) to rule out hard drive errors.
• Update your device drivers, especially chipset and storage drivers, from the manufacturer’s website.
• If the error occurs in a specific app, try reinstalling that app.

If the error only happens in one user account, create a new user account and see if it occurs there. If it doesn’t, the issue is with your user profile’s settings or files.

Common Misconceptions

Many users believe this error indicates a failing hard drive or RAM. While hardware issues can cause data corruption, the “stub received bad data” error is almost always a software problem. It’s also not caused by malware, so running a virus scan is unlikely to help unless you have a known infection. The error is not specific to any one app; it’s a Windows-level error that can surface in various contexts.

How to Prevent It in the Future

To reduce the chances of this error recurring:

• Keep Windows and drivers updated.
• Avoid force-shutting down your PC; use the Start menu’s restart option.
• Run SFC and DISM periodically if you notice system instability.
• Use reputable antivirus software and avoid third-party system cleaners that modify registry or system files.
• If you use a VPN or proxy, ensure it’s compatible with your Windows version.

Frequently Asked Questions

Does this error mean my computer is broken?

No. It’s a software error indicating corrupted system data, not a hardware failure. Following the steps above will almost always resolve it without replacing any components.

Will I lose my files if I do a repair install?

No. A repair install keeps your personal files, installed applications, and most settings. It only replaces Windows system files, which is exactly what’s needed to fix corruption.

Can I fix this error without admin access?

No. All the methods require administrator privileges. If you’re on a work or school computer, contact your IT administrator.

Why does the error only happen in the Microsoft Store?

The Store apps rely heavily on Windows Runtime components. If those components are corrupted, you’ll see this error. Re-registering the apps (Method 2) is the most direct fix.

Is there a way to avoid using the command line?

If you’re uncomfortable with Command Prompt, you can use the Windows Update Troubleshooter from Settings > Update & Security > Troubleshoot. It automates some of the same fixes, though it’s not as thorough as the manual methods.

Related

• Fix Dropbox Error 0x80070780 Access Issues
• Fix iTunes Error 2 on Windows: Step-by-Step Guide
• How to Save Pictures from Google Docs on Phone and PC