0X80000017

STATUS_EXTRANEOUS_INFORMATION 0x80000017 Fix

Windows Errors Intermediate 👁 6 views 📅 Jun 23, 2026

This error usually means a corrupted driver or system file. Here's how to fix it step by step.

Quick answer for experts

Run SFC /scannow, then DISM /RestoreHealth, check for driver updates, and test your RAM with Windows Memory Diagnostic.

What is STATUS_EXTRANEOUS_INFORMATION (0x80000017)?

This error pops up when Windows tries to read a file or driver and finds extra data it didn't expect. Think of it like a puzzle with an extra piece that doesn't fit. The system gets confused and throws this error. I've seen it most often after a failed Windows Update or a bad driver install. It can also show up when you're copying large files or running a game that needs a specific driver version. The real fix isn't always obvious — some folks try reinstalling Windows, but that's overkill if you follow these steps.

Main fix steps

These steps work for Windows 10 and 11. Do them in order. Don't skip any.

  1. Run System File Checker (SFC). Open Command Prompt as admin. Type
    sfc /scannow
    and press Enter. Wait for it to finish. It checks for corrupted system files and fixes them. Expect a message like "Windows Resource Protection found corrupt files and successfully repaired them." If it says it can't fix some files, move to step 2.
  2. Run DISM tool. Still in Command Prompt (admin), type
    DISM /Online /Cleanup-Image /RestoreHealth
    and press Enter. This fixes the Windows image that SFC uses. It takes a while — maybe 10 to 20 minutes. Don't close the window. After it's done, reboot your PC and run SFC again to catch anything leftover.
  3. Update all drivers. Go to your device manufacturer's website (Dell, HP, Lenovo, or your motherboard maker like ASUS or Gigabyte). Download the latest chipset, storage, and network drivers. Don't rely on Windows Update — it's often behind. Install them one by one, rebooting after each one. I've seen this error vanish after updating the storage driver (like Intel RST or AMD SATA).
  4. Check your RAM. Bad memory can cause weird errors like this. Search for "Windows Memory Diagnostic" in the Start menu. Run it and let it do a full test. It'll reboot and show results. If you see errors, replace the faulty stick. But if you don't have spare RAM, try removing and reseating the sticks first — sometimes it's just a loose connection.

Alternative fixes if the main one fails

If SFC and DISM didn't help, try these:

  • Perform a clean boot. Open msconfig, go to Services tab, check "Hide all Microsoft services", then click "Disable all". Go to Startup tab, open Task Manager, and disable all startup items. Reboot. If the error stops, turn services back on one by one to find the culprit. Often it's a third-party antivirus or a VPN driver.
  • Uninstall recent Windows Updates. Go to Settings > Update & Security > View update history > Uninstall updates. Remove the most recent update (usually KBxxxxxx). Reboot. If that fixes it, block that update from reinstalling with the Show or Hide Updates troubleshooter from Microsoft.
  • Test your hard drive. Open Command Prompt as admin and run
    chkdsk C: /f /r
    You'll get a prompt to schedule it for next reboot. Type Y and reboot. This scans for bad sectors. Warning: it can take hours on large drives. But if the disk is failing, you'll see errors in the report. Back up your data ASAP.

Prevention tip

Stop using Windows Update for drivers. Go to your PC maker's site and download drivers there. Also, set a system restore point before installing anything. It takes 30 seconds and saves you hours of headache. And if you're a gamer, keep your GPU drivers fresh — I've seen 0x80000017 from an old NVIDIA driver more than once.

Was this solution helpful?