0X00000663

Fix ERROR_PATCH_PACKAGE_OPEN_FAILED (0X00000663) on Windows

Windows Errors Intermediate 👁 1 views 📅 May 29, 2026

This error means Windows can't open an update or patch package. Corrupted download or bad permissions are the usual culprits.

Quick answer: Delete the corrupted update cache in C:\Windows\SoftwareDistribution\Download and run sfc /scannow + DISM /Online /Cleanup-Image /RestoreHealth.

This error pops up when Windows Update or a standalone installer (like an MSU file from Microsoft Catalog) tries to open a package and fails. I've seen it most often after a partial download gets interrupted — maybe your PC rebooted mid-download, or a network drop killed the transfer. The package header is missing or corrupt, so Windows doesn't know what to do with it. Another common trigger: trying to install an update while the Windows Update service isn't fully started.

Step-by-Step Fix

  1. Stop the Windows Update service. Open Command Prompt as administrator and run:
    net stop wuauserv
    net stop bits
    net stop cryptSvc
    net stop msiserver
    These services hold locks on the update cache. Stopping them lets us clean it.
  2. Wipe the download folder. Run:
    del /f /s /q "%windir%\SoftwareDistribution\Download\*.*"
    Or just navigate to C:\Windows\SoftwareDistribution\Download manually and delete everything inside. Don't delete the SoftwareDistribution folder itself — just the Download subfolder contents.
  3. Restart the services. Back in the admin command prompt:
    net start wuauserv
    net start bits
    net start cryptSvc
    net start msiserver
  4. Scan for system corruption. Run these two commands in order. First:
    sfc /scannow
    Let it finish — takes 5-10 minutes. Then:
    DISM /Online /Cleanup-Image /RestoreHealth
    DISM pulls fresh system files from Windows Update, so you need internet for this.
  5. Reboot and retry the update. Restart the PC, then go to Settings > Update & Security > Windows Update and check for updates again. Or re-run the standalone installer if that's what triggered the error.

If That Doesn't Work

Sometimes the problem is a permissions issue on the SoftwareDistribution folder itself. Check that the SYSTEM account and Administrators group have Full Control. Right-click the folder > Properties > Security tab. If SYSTEM isn't listed or has limited rights, that's your problem. Reset it from an admin command prompt:

icacls "%windir%\SoftwareDistribution" /reset /t

If you're on a domain-joined machine and using WSUS, the update could be corrupted on the server side. In that case, try downloading the update directly from the Microsoft Update Catalog as a standalone file. That bypasses your WSUS server entirely.

I've also fixed this by temporarily disabling third-party antivirus — especially McAfee and Norton — before running the update. They sometimes quarantine or block the installer temp files.

Prevention

Don't kill Windows Update processes during downloads. Let them finish. If you're on a slow or unreliable connection, use the Microsoft Update Catalog to download updates with a download manager that supports resume. Keep your system healthy with regular sfc /scannow runs — I do it monthly on my own machines. Also, set Windows Update to notify you before downloading if you're on metered connections, so a sudden cutoff doesn't leave a half-downloaded package behind.

This fix has worked for me across Windows 10 21H2 through Windows 11 23H2. If you still see 0X00000663 after these steps, you're probably dealing with a deeper system file corruption that needs a repair install (keep apps and files) using the Windows 11 ISO installer.

Was this solution helpful?