System Restore error 0x80042302 appears when Windows cannot create a restore point, usually because the Volume Shadow Copy (VSS) service is stopped or the system volume lacks enough free space. The quickest fix is to restart the Volume Shadow Copy service and its dependencies, then increase the disk space allocated to System Protection. Below are the exact steps, the causes behind the error, and what to do if the basic fix does not work.
What Causes Error 0x80042302
Error 0x80042302 is a Volume Shadow Copy error, and it means the VSS service did not complete the snapshot operation. The most common triggers are:
- VSS service is stopped or disabled – System Restore depends on VSS to take a snapshot of your system files.
- Insufficient disk space – VSS needs a certain amount of free space on the system drive to create the shadow copy.
- Third-party backup or antivirus software – Some programs interfere with VSS operations.
- Corrupted system files – Damaged Windows components can prevent VSS from starting.
- Disk errors or a full System Protection storage limit – If the allocated space is already at its maximum, new restore points fail.
This error is not unique to a specific Windows version; it has been reported on Windows 10 and Windows 11, and the fix steps are essentially the same on both.
Step-by-Step Fix: Restart VSS and Dependencies
Start with the simplest solution, which resolves the error in most cases. You need to run the services with administrator privileges.
- Press Win + R, type
services.msc, and press Enter. - Locate Volume Shadow Copy. Right-click it and select Restart. If it is not running, choose Start.
- Set its startup type to Automatic by double-clicking it, changing the dropdown, and clicking OK.
- Repeat the same for these dependent services:
– Microsoft Software Shadow Copy Provider
– Remote Procedure Call (RPC) – this one is usually already running, but verify it is not disabled.
– System Event Notification Service - Restart your computer and try creating a restore point again.
If the service fails to start, note the error message – it may point to a deeper issue, such as a corrupted driver or a conflict with another service.
Increase Disk Space for System Protection
Even with VSS running, a full disk will produce the same error. Windows needs a minimum of about 300 MB to create a restore point, but 1–2 GB is safer for a typical system.
- Open Control Panel > System > System Protection.
- Select your system drive (usually C:) and click Configure.
- Under Disk Space Usage, move the slider to a higher value (e.g., 5% or more).
- Click Apply and then OK.
- Also check that the drive has at least 2–3 GB of free space. If it is below that, delete temporary files or move personal data to another drive.
If you have a separate data drive, you can enable System Protection on it as well, but the system drive is the one that matters for restore points that include Windows settings.
Run SFC and DISM to Repair Corrupted Files
If the error persists, corrupted system files may be the cause. Use the built-in Windows tools to repair them. These commands take a few minutes and require an administrator command prompt.
- Right-click the Start button and select Terminal (Admin) or Command Prompt (Admin).
- Run
sfc /scannowand wait for it to finish. This checks and repairs protected system files. - If SFC finds issues but cannot fix them, run
DISM /Online /Cleanup-Image /RestoreHealth. This repairs the Windows image itself. - Restart your PC and try creating a restore point again.
Note that SFC can take 15–30 minutes on a large drive. Do not interrupt it.
Check for Third-Party Software Conflicts
Antivirus programs, disk cleanup utilities, and backup tools that use VSS can cause error 0x80042302. A common example is a backup program that leaves a VSS snapshot in a pending state.
- Temporarily disable any third-party antivirus or backup software and try creating a restore point.
- If the error disappears, re-enable the software one by one to identify the culprit.
- For backup tools, look for an option to “clear pending snapshots” or “cancel current backup” – some tools get stuck and block new snapshots.
You can also check if there are any pending shadow copies by opening an admin command prompt and running vssadmin list shadows. If you see old snapshots, you can delete them with vssadmin delete shadows /all (this removes all restore points – make sure you do not need them).
If Nothing Works: Reset System Protection and Recreate the Restore Point
When all else fails, you can reset System Protection entirely. This clears all existing restore points, but it often resolves persistent VSS errors.
- Open System Protection as above.
- Select the system drive and click Configure.
- Click Disable System Protection and then Apply.
- Restart your PC.
- Go back to System Protection, select the drive, and click Enable System Protection.
- Set the disk space slider to your desired value and click Apply.
- Now try to create a restore point manually.
If the error still appears after this, the issue may be with the disk itself. Run chkdsk /f on the system drive (you will be prompted to schedule it for the next restart). Bad sectors or file system errors can prevent VSS from working.
Frequently Asked Questions
Does error 0x80042302 mean my system is corrupted?
Not necessarily. It usually means the Volume Shadow Copy service is not running or there is not enough disk space. Only if the error persists after restarting the service and freeing space should you suspect file corruption.
Can I create a restore point manually to avoid this error?
Yes. You can manually create a restore point by opening System Protection and clicking Create. But if the error occurs, the manual creation will fail with the same code. Fix the underlying cause first.
Will disabling System Protection free up disk space?
Yes, disabling System Protection deletes all existing restore points and frees the disk space they were using. However, you will lose the ability to undo system changes until you re-enable it.
Is error 0x80042302 the same as error 0x8004231F?
No. 0x8004231F means the shadow copy is already in progress, while 0x80042302 is a general VSS failure. The fixes overlap, but 0x8004231F usually resolves by waiting or restarting the backup program.
Can I ignore this error if I do not use System Restore?
You can, but System Restore is a useful safety net. If you never create restore points, you have no easy way to undo a bad driver update or registry change. It is worth fixing the error so the feature works when you need it.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- How to Get More Disk Space on Mac: 12 Fixes
- Wii Browser Games With a USB or Bluetooth Controller
- Delete Focus on iPhone: Quick Steps
- Access Your Computer From Anywhere: Step-by-Step
- Open System Configuration in Windows 10: 7 Ways
- How to Connect VPN: Step-by-Step Setup Guide