Error 0x8000ffff in Windows 11 & 10: Store, Update, System Restore and File Copy Fixes

Error 0x8000ffff means "unexpected failure", sometimes shown as Catastrophic failure. It is Windows' generic code for "something went wrong that the program did not expect", so the fix depends entirely on where you see it. In the Microsoft Store, run wsreset.exe and check the date and time. In Windows Update, reset the update components and repair system files with DISM and SFC. In System Restore, run the restore from Safe Mode or the recovery environment. When copying or moving files in File Explorer, restart Explorer and check the file and destination. The common thread most guides miss: the code itself does not identify the cause; the place it appears does. Find your situation in the table below and start there.

Ethan's aunt saw "0x8000ffff" in the Microsoft Store when updating a photo app, and searched the code. The first article told her to reset Windows Update; the second to edit the registry; the third to download a repair tool. None helped, because none were about the Store. At Jake's shop the fix took one minute: the laptop's clock was three days behind after a dead battery, so the Store's secure connection failed with this generic code. Jake set the time to automatic, ran wsreset, and the update installed. A month later the same code appeared when she tried to copy photos to a USB stick, and that time the cause was completely different. This page sorts out every case.

None of the fixes below delete your personal files. Where a step resets an app or clears a cache, it says so, and the app's data is recreated automatically.

Where you see 0x8000ffff, and where to start

Windows uses 0x8000ffff the way a doctor might say "you are unwell": true, but not a diagnosis. The location narrows it down; the steps below do the rest.

0x8000ffff and the codes it gets confused with

If your message shows one of the more specific codes instead, use its fix; the generic ones, 0x8000ffff and 0x80004005, are the only ones where the surrounding context matters more than the number.

0x8000ffff in the Microsoft Store

1. Fix the date and time. Open Settings > Time & language > Date & time, turn on Set time automatically and Set time zone automatically, and click Sync now. A wrong clock breaks the Store's secure connections, as on Ethan's aunt's laptop.
2. Check your region. Under Settings > Time & language > Language & region, make sure Country or region is where you are; a mismatch can block downloads.
3. Reset the Store cache. Press Windows + R, type wsreset.exe, and press Enter. A blank window appears for a while, then the Store opens. Your apps and purchases are not affected.
4. Sign out and back in. In the Store, click your profile picture, sign out, restart the PC, and sign in again.
5. Repair or reset the Store app. Settings > Apps > Installed apps > Microsoft Store > three dots > Advanced options > Repair, then Reset if Repair does not help.
6. Run the Store troubleshooter. Settings > System > Troubleshoot > Other troubleshooters > Windows Store Apps.
7. Check the Store's services. In services.msc, make sure Microsoft Store Install Service and Background Intelligent Transfer Service are not Disabled.

If a single app fails to update with 0x8000ffff while others work, uninstall that app and reinstall it from the Store; its own package may be damaged.

Microsoft Store will not open at all

If the Store closes immediately or never opens, run wsreset.exe first. If it still fails, re-register it: open Terminal (Admin) and run Get-AppxPackage -AllUsers Microsoft.WindowsStore | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}. Red text about packages already in use is normal; restart and try the Store again. On current Windows 11 versions, wsreset -i in an administrator Terminal reinstalls the Store app itself in the background, which helps when the Store has been removed or badly damaged; give it a few minutes before checking Start for the Store icon.

If the Store opens but shows a blank page, check the internet connection, then try switching between Wi-Fi and a wired or phone connection; a blank Store often means it cannot reach its servers rather than a damaged app.

Store downloads stuck on "Pending"

Downloads that sit on Pending or Starting download before failing with 0x8000ffff are usually waiting on something else: another app's update ahead in the queue, Windows Update downloading in the background, or a metered connection. Open the Store's Library (Downloads on older versions), pause other downloads, and retry. Check Settings > Network & internet for a metered connection and turn it off, or allow app downloads over metered connections in the Store's settings. If Windows Update is busy, let it finish first. A restart clears stuck queues more often than anything else.

Large games and apps also need free space for the download plus the installed files, often twice the listed size during installation; check the target drive before retrying a stuck download.

Microsoft account and Store sign-in problems

The Store needs a working Microsoft account sign-in for paid apps and some free ones. If the account shows a warning in Settings > Accounts > Your info, such as a request to verify your identity, complete it. Make sure you can sign in at account.microsoft.com in a browser. Family members with child accounts may need a parent's approval for downloads, which can appear as a generic failure if the request was not approved. Signing out of the Store and back in, then restarting, refreshes the license information that many 0x8000ffff Store errors depend on.

0x8000ffff in the Xbox app and games

Game installs through the Xbox app and Microsoft Store rely on a component called Gaming Services. When it is damaged, installs fail with generic codes including 0x8000ffff. Update Gaming Services from the Store's Library first. If that does not help, remove and reinstall it: in Terminal (Admin), run Get-AppxPackage *gamingservices* -AllUsers | Remove-AppxPackage -AllUsers, restart, then install Gaming Services again from the Microsoft Store and try the game install once more. Also check the drive you are installing to has enough free space; game installs need room for both the download and the unpacked files.

VPNs, proxies and the Store

The Store and Windows Update talk to Microsoft's servers, and VPNs, proxy settings or DNS filtering can interrupt those connections in ways that show up as generic errors. Disconnect the VPN and try again. Check Settings > Network & internet > Proxy for a manual proxy you do not use, and turn it off. Home network blockers such as Pi-hole can also block Store addresses; check their query log while retrying the download.

Corporate VPN clients on personal PCs are a common culprit, because they route all traffic through the office network, where the Store may be blocked by policy. Disconnect before using the Store at home.

Install Store apps with winget when the Store fails

When the Store app itself is the problem, the Windows Package Manager can install many Store apps from the command line. Open Terminal and run winget search "app name" --source msstore to find the app's ID, then winget install --id ID --source msstore. It uses the same Store catalog and licenses without the Store's interface, which makes it a useful workaround while you repair the Store, and a quick test of whether the problem is the Store app or the connection behind it.

If winget also fails with a connection error, the problem lies in the network, proxy or clock rather than the Store app, and the Store section's time and VPN fixes apply. If winget succeeds, the Store app itself needs the repair, reset or re-register steps.

Store app dependencies

Store apps rely on shared framework packages, such as Microsoft.VCLibs, Microsoft.UI.Xaml and Microsoft.NET.Native. If one of these is damaged or removed, often by a debloat script, several apps fail to install or open with generic errors. Updating all apps from the Store's Library usually reinstalls missing frameworks. If not, the in-place repair or Fix problems using Windows Update restores them with the rest of Windows.

To see which frameworks are installed, run Get-AppxPackage *VCLibs* or Get-AppxPackage *UI.Xaml* in Terminal. Several versions side by side is normal; different apps need different versions, so never remove the older ones to tidy up.

0x8000ffff in Windows Update

1. Restart and try again; a pending operation may simply need finishing.
2. Run the Windows Update troubleshooter: Settings > System > Troubleshoot > Other troubleshooters > Windows Update.
3. Reset the update components: in Terminal (Admin), stop wuauserv, bits and cryptsvc with net stop, rename C:\Windows\SoftwareDistribution and C:\Windows\System32\catroot2 by adding .old, then start the three services again with net start.
4. Repair system files: DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow.
5. Install the update manually from the Microsoft Update Catalog by its KB number, if one specific update keeps failing.
6. Pause third-party antivirus during the install if the above do not help.

Our guides to "We couldn't connect to the update service" and error 0x80070005 walk through the reset and repair steps in more detail; they fix 0x8000ffff in Windows Update too.

If one particular update keeps failing while others install, note its KB number from Update history; searching that number shows whether it is a known problem update and whether Microsoft has released a fixed version or a workaround for it.

"Fix problems using Windows Update" (Windows 11)

Current Windows 11 versions include a built-in repair that reinstalls the current version of Windows from Windows Update while keeping your files, apps and settings. Open Settings > System > Recovery and click Reinstall now next to Fix problems using Windows Update. It downloads a fresh copy of your Windows version and installs it over the top, which replaces damaged system files and update components in one go. It takes an hour or so and needs a working internet connection; if Windows Update itself is completely broken, use an in-place repair from an ISO instead.

Check free space first

Updates, Store downloads and System Restore all need working space on C:. When the drive is nearly full, they can fail with unexpected errors rather than a clear "not enough space" message. Open Settings > System > Storage and aim for at least 10 to 15 percent free. Use Cleanup recommendations and Temporary files to clear space safely, including previous Windows installations and the Delivery Optimization cache, then retry.

Remember that Store apps and games may install to a different drive set under Settings > System > Storage > Advanced storage settings > Where new content is saved; check free space there too, not just on C:.

0x8000ffff during System Restore

System Restore may fail with "An unspecified error occurred during System Restore (0x8000ffff)". The usual cause is that a program, often antivirus, has files locked, so Restore cannot replace them.

1. Pause or uninstall third-party antivirus, then try the restore again.
2. Run the restore from Safe Mode: boot into Safe Mode, press Windows + R, type rstrui, and choose the restore point. Fewer programs run, so fewer files are locked.
3. Run it from the recovery environment: hold Shift and click Restart, then Troubleshoot > Advanced options > System Restore. Windows is not running at all, which avoids locks entirely.
4. Try an older restore point if one specific point fails.
5. Check disk space on C:, since Restore needs room to work.

Restoring from the recovery environment is the most reliable of these and fixes the error in most cases. Our guide to System Restore covers creating and using restore points.

If every restore point fails, even from the recovery environment, the restore points themselves may be damaged. Create a new one once Windows is working, and keep a proper backup alongside System Restore; restore points protect system settings and programs, not your personal files, and they are deleted when disk space runs low.

Restore point creation fails with 0x8000ffff

Creating a restore point can fail with the same code. System Restore relies on the Volume Shadow Copy service. Open services.msc, make sure Volume Shadow Copy is set to Manual and is not Disabled, and that Microsoft Software Shadow Copy Provider is not disabled either. Then check System Protection is on for C: with some disk space allowed (5 to 10 percent is typical). Backup tools that use their own shadow copy providers can conflict; temporarily disabling them, or updating them, often resolves the failure. In Terminal (Admin), vssadmin list writers shows whether any VSS writer is in a failed state, which points to the program causing trouble.

"Error 0x8000FFFF: Catastrophic failure" when copying or moving files

File Explorer sometimes shows this dramatic-sounding message when copying, moving, pasting or renaming. It is rarely as bad as it sounds:

1. Restart Windows Explorer from Task Manager (Processes > Windows Explorer > Restart), then try again. Our guide to restarting Explorer shows how.
2. Copy fewer files at a time. Very large batches with long paths or unusual characters can trip Explorer.
3. Download cloud files first. Online-only OneDrive or other cloud files (cloud icon) must download before copying; right-click and choose Always keep on this device, wait, then copy.
4. Check the destination: a full USB stick, a drive formatted as FAT32 (which cannot hold files over 4 GB), a phone connected in charging mode, or a network share that dropped can all produce this error.
5. Check names and paths: shorten very long folder paths and remove odd characters from file names.
6. Try copying with Terminal: robocopy "source" "destination" /E often succeeds where Explorer stumbles, and reports exactly which file fails.

This was the second problem on Ethan's aunt's laptop: the USB stick was formatted FAT32 and one video was larger than 4 GB. Reformatting the stick as exFAT, after copying its contents elsewhere, fixed it.

If one particular file always triggers the error, the file itself may be damaged or locked by another program. Close apps that might be using it, such as photo or video editors, and try copying it alone. A file that never copies, even after a restart, may have unreadable sectors on the source drive; check that drive's health before relying on it.

Copying to or from phones and cameras

Phones and many cameras connect using a media transfer protocol rather than as a normal drive, and they are a common source of Catastrophic failure messages. Unlock the phone and keep it unlocked during the copy; set the USB mode on the phone to File transfer instead of Charging only; copy in smaller batches; and avoid copying straight from the phone into a cloud-synced folder that is busy syncing. If copies keep failing, use the phone's own sync app, or the Windows Photos app's Import, which handles these devices more gracefully than dragging files in File Explorer.

Copying to network shares and NAS drives

Copying to a NAS or shared folder can fail with this code when the connection drops briefly, when permissions on the share do not allow writing, or when file names contain characters the NAS does not accept. Check you can create a new folder on the share by hand; if not, it is a permissions problem on the NAS or server. For large transfers, robocopy "C:\Source" "\\NAS\Share\Dest" /E /Z resumes after network hiccups thanks to /Z, and lists any file that fails, which Explorer does not.

Mapping the share to a drive letter and copying again also helps some NAS devices that behave better with mapped drives than with network paths typed into the address bar.

USB stick and drive formats

Check a drive's format by right-clicking it in This PC and choosing Properties. To change it, copy its contents elsewhere, right-click the drive, choose Format, pick exFAT for a general-purpose stick, and click Start. Formatting erases everything on the drive, so the backup step is not optional.

Very old sticks or ones with errors may fail even after formatting. If a stick gives errors on several PCs, replace it; they are inexpensive, and a failing stick can damage the files you trust to it.

0x8000ffff when installing app packages

Installing an .msix, .appx or .appinstaller file can fail with 0x8000ffff when a dependency is missing or the App Installer app is outdated. Update App Installer from the Microsoft Store, then try again. If the package came from a developer's site, check whether they also publish it in the Store, which handles dependencies automatically. In PowerShell, Add-AppxPackage -Path "file.msix" shows a more detailed error message, including which dependency is missing.

Packages from outside the Store also need the correct architecture: an Arm64 package will not install on a standard x64 PC, and older x86-only packages may need extra framework packages. The developer's download page usually lists which file matches your PC.

Sideloaded packages also need Developer Mode or the Install apps from any source option on some managed or older configurations; check Settings > System > For developers if Windows refuses to start the installer at all.

0x8000ffff in many places: system-wide fixes

1. Repair system files: DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow, in Terminal (Admin).
2. Scan for malware: run a Microsoft Defender full scan and an offline scan.
3. Check the drive: chkdsk C: /scan, and look at drive health under Settings > System > Storage > Disks & volumes.
4. Clean boot to rule out a third-party service; our guide to a clean boot explains it.
5. Test a new user account: if the errors stop there, your profile is damaged.
6. In-place repair: run Windows setup from a current ISO and keep files and apps.

Run these in order and restart between them; each one fixes a different layer, from files to services to the whole installation.

Profile problems: when only one account is affected

If 0x8000ffff appears for one user but not for others on the same PC, the problem is in that user's profile, such as damaged app data or settings. Create a test account under Settings > Accounts > Other users, sign in, and try the same action. If it works, reset the failing apps in the original account, or move the person's files to a fresh account. Profile damage is uncommon, but this one test separates a system problem from a personal one in a few minutes.

If the test account works, you can also copy the affected user's documents into the new account and keep using it, which is often quicker than repairing every app in the damaged profile.

0x8000ffff when installing drivers

Driver installers occasionally report this code, especially when a previous version is still loaded or the installer cannot replace files in use. Restart, then run the installer again before opening any related software. If that fails, uninstall the current driver from Device Manager with Attempt to remove the driver for this device checked, restart, and install the new version. For stubborn cases, pnputil /enum-drivers in Terminal (Admin) lists installed driver packages, and the maker's clean-install option, where offered, avoids the conflict entirely.

Signed drivers from the PC or component maker install most reliably; avoid driver updater utilities, which sometimes install mismatched packages that cause exactly this kind of failure.

0x8000ffff in Office and other apps

When a specific desktop app shows the code, the app itself is usually at fault. For Microsoft Office, open Settings > Apps > Installed apps, find Microsoft 365 or Office, choose Modify, and run Quick Repair, then Online Repair if needed. For other apps, check for an update, use the app's own repair option if it has one, and otherwise uninstall and reinstall. Our guide to uninstalling programs covers stubborn removals.

Office errors that mention a specific add-in point to that add-in; start the app in safe mode by holding Ctrl while opening it, and disable add-ins one at a time to find the culprit.

0x8000ffff right after a Windows update

If the errors began immediately after an update installed, that update may have a bug affecting your setup. Check Settings > Windows Update > Update history for the newest entry, search its KB number with "known issues", and if others report the same problem, uninstall it under Update history > Uninstall updates, then pause updates for a week while a fix arrives. Our guide to uninstalling a Windows update walks through it.

Pausing updates is a short-term measure. Resume them once a fixed version is released, so you do not miss security updates.

A pending restart can cause it

Windows sometimes holds changes until the next restart. While an update, driver or app install waits for that restart, related operations can fail with unexpected errors. If the Power menu shows Update and restart, or an installer asked you to restart and you postponed it, restart first. It is the simplest fix on this page and resolves a surprising number of one-off 0x8000ffff messages.

If restarting keeps asking to restart again, an update is stuck in a loop; our guide to updates stuck in a restart loop covers that specific case.

Why the clock matters so much

Many 0x8000ffff reports, especially from the Store, trace back to the date and time. Secure connections check certificates against the current date; if the PC's clock is days or years off, those checks fail, and some apps report the failure with this generic code instead of a clear "certificate" message. PCs left unplugged for months, laptops with a dead CMOS battery, and dual-boot setups that change the hardware clock are the usual suspects. Always check the clock first; it is the quickest fix on this page and the most often skipped.

To check quickly, look at the full date in the taskbar clock, not just the time. A PC set to the right time on the wrong day, or the wrong year, still fails every certificate check.

If the time drifts again after syncing, open Services and make sure Windows Time is set to start automatically; a disabled time service lets the clock wander until the errors return.

Third-party antivirus and security software

Security suites hook deeply into file operations and network connections, and an outdated or misbehaving one can make Store downloads, updates and restores fail unexpectedly. Update it first. If errors continue, pause its protection temporarily, try the failing action, and turn protection back on immediately. If that fixes it, reinstall the security product with its maker's clean removal tool, or rely on Microsoft Defender, which is built in and does not cause these conflicts.

Some suites also include their own firewall and web filter, which can block the Store's connections without obvious warnings; check their logs for blocked connections around the time of the error.

When testing with protection paused, disconnect from untrusted networks and avoid opening unknown files, then switch protection back on straight after the test, whether it helped or not.

What not to do

• Do not download "0x8000ffff fixer" tools from search ads; the real fixes are free and built in.
• Do not edit random registry keys suggested for this code; it is generic, so a registry change for one context rarely helps another.
• Do not reset the whole PC first. Each context has a quick fix; a reset is a last resort.
• Do not ignore it if it appears everywhere; that pattern points to system file damage or a failing drive, which deserve attention.

Keep notes of what you try. If you need help later, a short list of steps already taken saves time and avoids repeating them.

The 2017 Store error that started this page

This page began in 2017 as a fix for a Windows 10 Store bug, when many PCs showed 0x8000ffff while downloading apps after a feature update. Microsoft fixed that specific bug long ago. Today's 0x8000ffff reports come from the general causes above, which is why the old one-line fix no longer helps most people, and why this rewrite organizes everything by where the error appears.

If you arrived here from an old link with the 2017 instructions in mind, start with the table at the top; it covers the modern causes in the order that fixes them fastest.

Keep 0x8000ffff from coming back

• Keep the clock set automatically and replace a failing CMOS battery.
• Restart regularly, and always when an installer or update asks.
• Keep one security product, up to date, rather than several.
• Leave enough free space on C:, at least 10 to 15 percent.
• Use exFAT for USB sticks that carry large files.
• Keep System Protection on, so restore points exist when you need them.

None of these takes more than a minute, and together they prevent most of the situations where generic errors like this appear.

Finally, avoid debloat and tweak scripts that remove system components or disable services; they are behind a large share of persistent Store and update errors.

Find more detail in the logs

Because the code is generic, the logs often say more. Open Event Viewer and check Windows Logs > Application and System around the time of the error. For the Store, look under Applications and Services Logs > Microsoft > Windows > AppXDeploymentServer > Operational or Store. For updates, Get-WindowsUpdateLog creates a readable log on the desktop. For System Restore, the System log records SystemRestore events with more specific failure reasons. A more specific code or file name in these logs usually leads straight to the fix.

If an entry names a specific package, service or file, search that name together with the error; you will usually find the real cause much faster than searching the generic code alone.

Read the whole message before searching

Error dialogs often include more than the code: the name of the app, a file or update, or a short phrase such as "Unspecified error" or "Catastrophic failure". Take a screenshot with Windows + Shift + S before closing the message, and note what you were doing and the time. Those details turn a vague code into a specific search, and they are exactly what support staff ask for first.

If the dialog has a Details or More info button, open it before closing; many apps hide the specific cause there, beneath the generic code.

When to get help

If the error survives the fixes for your situation, a system file repair and a clean boot, it is time to ask for help. Bring the screenshot, the time it happened, what the Event Viewer entries say and what you already tried. Microsoft's support, the PC maker's support or a local repair shop can then skip straight to deeper checks rather than repeating the basics. For a PC under warranty, the maker's diagnostics can also confirm whether the drive or memory is involved.

For Store problems, Microsoft's support pages and community forums often list current known issues; checking them first can save hours if the Store is having a wider problem that day.

Is it safe to ignore 0x8000ffff?

A one-off 0x8000ffff that does not return after a restart is safe to ignore; generic errors happen occasionally. A repeating error is worth fixing, especially in Windows Update, because it can leave the PC without security fixes, and in System Restore, because it means your safety net may not work when you need it. Errors that spread to many places are the most important to act on, since they point to system damage, malware or a failing drive.

A useful rule: if the same action fails twice with this code after a restart, fix it using the section for that place; if it happens once and never again, move on.

Windows 10 differences

On Windows 10, the same fixes apply with slightly different Settings paths: troubleshooters are under Settings > Update & Security > Troubleshoot > Additional troubleshooters, and app repair and reset under Settings > Apps > Apps & features. wsreset, DISM, SFC and the update component reset are identical. Windows 10 reached end of support in October 2025; PCs on Extended Security Updates still receive updates, and the Windows Update fixes here apply to them.

The Windows 10 Store is older and occasionally needs the re-register command above more often than on Windows 11; it remains supported for app updates on ESU-enrolled PCs.

On older Windows 10 builds that have not updated for a long time, update the Store and App Installer first, since many 0x8000ffff Store errors there come from outdated store components rather than anything on the PC itself.

For IT admins: 0x8000ffff at scale

Store and apps. In managed environments, Store access may be restricted by policy; deploy apps through Intune or winget instead. AppX deployment logs on affected devices give the specific failure.

Updates. Clusters of 0x8000ffff on updates usually follow image or servicing-stack problems; repair the image with DISM from a known-good source and confirm servicing stack updates are current.

Restore. On shared machines, prefer re-imaging over System Restore; restore points are not a reliable fleet recovery tool.

Copy jobs. For large or scripted transfers between servers and NAS devices, use robocopy with logging rather than Explorer; its exit codes and logs make 0x8000ffff-style failures easy to trace.

Error 0x8000ffff: frequently asked questions

Ethan's aunt now has a simple rule for error codes: before searching the number, notice where it appeared. 0x8000ffff in the Store led to the clock; 0x8000ffff while copying led to the USB stick's format. Same code, different worlds. Generic codes are frustrating precisely because they look specific, and the articles that treat them as one problem waste everyone's time. Start from the place, use the matching fixes here, and this one is rarely more than a few minutes' work.

Revision note. Written October 2, 2026, rewriting our 2017 Store fix into a full guide for every place 0x8000ffff appears. May your next error code be your last.