System Restore Point Error 0x80042308 Fix

System Restore Point error 0x80042308 on Windows 10 usually appears when the Volume Shadow Copy Service (VSS) cannot create a snapshot, often due to insufficient disk space or a corrupted shadow copy storage. The fix involves freeing up space, checking the VSS service, and sometimes deleting existing restore points or adjusting the shadow storage size.

What Does Error 0x80042308 Mean?

Error 0x80042308 is a Windows error code that maps to ERROR_VSS_MAXIMUM_DIFFAREA_SIZE_REACHED. In plain terms, the Volume Shadow Copy Service (VSS) has run out of the space it is allowed to use for storing shadow copies—the underlying technology that System Restore uses to create restore points. When you try to create a restore point manually or automatically, VSS attempts to allocate space for the snapshot, but the configured limit (or the actual free space on the drive) is too small, so the operation fails and you see 0x80042308.

Why Does This Error Happen?

System Restore relies on VSS to take a point-in-time snapshot of your system files, registry, and installed programs. To do this, VSS needs a contiguous block of storage on the same volume, called the “shadow storage” or “diff area.” Windows sets a default maximum size for this storage, usually around 5% of the total drive size or 10 GB, whichever is smaller. If the drive is nearly full, or if the shadow storage has already reached that cap, new restore points cannot be created, and you get error 0x80042308.

Common triggers include:

• The system drive (usually C:) has very little free space (less than a few GB).
• The shadow storage maximum size has been manually set too low.
• Many large restore points have accumulated, filling the diff area.
• Another backup program (like a third-party imaging tool) is using VSS and consuming the same storage.
• Corruption in the VSS configuration or the System Volume Information folder.

How to Fix Error 0x80042308

Work through these steps in order. Most users resolve the issue with the first two steps.

1. Free Up Disk Space

VSS needs at least a few gigabytes of free space on the system drive to create a restore point. Delete temporary files, empty the Recycle Bin, or use the built-in Disk Cleanup tool. To open it, type cleanmgr in the Start menu, select the system drive, and choose “Clean up system files.” Also consider moving large files (videos, ISOs, etc.) to another drive.

2. Check the Volume Shadow Copy Service

VSS must be running and set to manual startup. Press Win + R, type services.msc, and press Enter. Scroll to “Volume Shadow Copy.” If it is not running, right-click it and select Start. Double-click it, set Startup type to Manual (or Automatic if it was already set to that), and click OK. Also check the “Microsoft Software Shadow Copy Provider” service—it should also be set to Manual and running.

3. Delete Existing Restore Points

If you have many restore points, deleting some can free up shadow storage. Open the System Protection dialog (search for “Create a restore point” in the Start menu), select the system drive, click Configure, and then click Delete. This removes all restore points for that drive. You can also use the vssadmin command in an elevated Command Prompt:

vssadmin delete shadows /for=C: /oldest

This deletes the oldest shadow copy. Repeat if needed, or use /all to delete all (but be careful—this removes all restore points).

4. Adjust Shadow Storage Size

If the diff area is capped too low, you can increase it. Open an elevated Command Prompt (right-click Start, select “Command Prompt (Admin)” or “Windows PowerShell (Admin)”) and run:

vssadmin resize shadowstorage /for=C: /on=C: /maxsize=10GB

This sets the maximum shadow storage to 10 GB. Replace 10GB with a value that suits your drive (e.g., 15GB). If you get an error saying the storage is already in use, you may need to delete some shadows first (step 3).

5. Rebuild the VSS Configuration

If the error persists, VSS may be corrupted. In an elevated Command Prompt, run the following commands one by one:

net stop vss
net stop swprv
regsvr32 /s ole32.dll
regsvr32 /s oleaut32.dll
vssadmin list providers

If the provider list is empty or shows errors, you may need to re-register the VSS DLLs. A more thorough approach is to run the System File Checker:

sfc /scannow

This checks for corrupted system files and repairs them. After that, restart the VSS services with:

net start vss
net start swprv

6. Check for Other Backup Software

Third-party backup tools that use VSS can consume the same shadow storage. If you have such software, check its settings to see if it uses VSS and whether it has its own storage limits. Temporarily disabling it can help diagnose the issue.

How to Prevent This Error in the Future

• Keep at least 5-10 GB of free space on the system drive at all times.
• Set a reasonable shadow storage max size (e.g., 10 GB) to avoid hitting the default cap too quickly.
• Regularly delete old restore points manually if you create them frequently.
• If you use disk cleanup tools, avoid cleaning the “System Restore and Shadow Copies” option unless you intend to delete all restore points.

Common Misconceptions About Error 0x80042308

One common myth is that this error means your hard drive is failing. While a failing drive can cause VSS errors, 0x80042308 specifically points to a storage space limit, not hardware failure. Another misconception is that disabling System Restore and re-enabling it will fix the error—this can help if the configuration is corrupted, but it deletes all existing restore points, so it should be a last resort. Also, some users think that increasing the shadow storage size is always the solution, but if the drive is simply full, increasing the cap won’t help.

Frequently Asked Questions

Can I fix error 0x80042308 without deleting my restore points?

Yes, you can try increasing the shadow storage size first, or free up disk space. If those don’t work, you may need to delete some older restore points, but you can keep the most recent ones by using the vssadmin delete shadows /for=C: /oldest command repeatedly until you have enough space.

Does this error affect system performance?

Not directly. The error only prevents new restore points from being created. However, if your drive is nearly full, that can slow down your system, and the lack of recent restore points means you have less protection against system issues.

Is it safe to delete all restore points?

Yes, it is safe in the sense that it won’t harm your files, but you will lose the ability to revert your system to an earlier state. Only do this if you have another backup method or if you are comfortable with the risk.

Will this error occur on Windows 11 as well?

Yes, the same error code can appear on Windows 11 because the underlying VSS mechanism is the same. The fixes are identical.

Can I use Command Prompt to create a restore point instead of the GUI?

Yes, you can use wmic.exe /Namespace:\\root\\default Path SystemRestore Call CreateRestorePoint "My Restore Point", 100, 7 in an elevated Command Prompt. This will attempt to create a restore point and will show the same error if the issue persists.

What if none of these steps work?

If you’ve tried all the steps and the error persists, you can try performing a system restore from a different restore point (if any exist) or use the “Reset this PC” feature in Windows 10, which reinstalls Windows while keeping your files. As a last resort, a clean install of Windows will definitely resolve the issue, but it’s a drastic step.

Related

• Disney Plus Error Code 86 Fix (Step-by-Step)
• Fix Choppy Apps at High Refresh Rate
• How to Set Up a New Microsoft Surface