Fix SPAPI_E_SET_SYSTEM_RESTORE_POINT 0x800F0236 driver error

Driver install fails because Windows can't create a restore point. The fix is to disable system restore temporarily, install your driver, then re-enable it.

You're trying to install a driver — maybe a graphics card, a network adapter, or some chipset update — and Windows throws back error code 0x800F0236. It's cryptic and frustrating, especially when the driver itself is fine. I've been there. Let's fix it.

Direct fix: disable system restore, install driver, re-enable

Here's what's actually happening: Windows PnP (Plug and Play) tries to create a system restore point before installing any driver that isn't Microsoft-signed. The restore point creation itself fails — maybe the Volume Shadow Copy service is stuck, disk space is low, or there's a corruption in the restore point database. The driver install then stops because the system restore failed. It's a safety check that goes wrong.

The fastest way through this:

Open System Properties. Press Win + R, type sysdm.cpl, and hit Enter.
Go to the System Protection tab.
Select your system drive (usually C:) and click Configure.
Select "Disable system protection". Windows will warn you that existing restore points will be deleted. Click OK through that.
Install your driver. Run the installer as administrator. It should now complete without the 0x800F0236 error.
Re-enable system protection. Go back to the same place, select your drive, click Configure, and choose "Enable system protection". Set the max usage slider to something reasonable — 5-10% of your drive is usually fine.

That's it. The driver installs, system restore is back, and you didn't have to reboot or run SFC scans that won't help here.

Why does this work? When system protection is disabled, Windows skips the restore point creation step entirely during driver install. The PnP manager checks if restore is active before calling into VSS to create the point. If it's off, the check passes trivially, and the install proceeds. No VSS calls, no shadow copy failures, no error.

Why the restore point creation fails

There are three common underlying causes for the failed restore point:

Volume Shadow Copy service is stopped or hung. Go to Services.msc, find "Volume Shadow Copy", right-click and Restart it. Set startup type to Automatic if it isn't.
Low disk space. System restore needs at least 1 GB free on the system drive to create a point. Clear temp files or uninstall junk.
Corrupted restore point data. If you've had restore points that failed to create before, the database can get into a bad state. Disabling and re-enabling (the fix above) clears it.

In my experience, the service hang is the most common culprit on Windows 10 22H2 and Windows 11 23H2. Shadow copy gets wedged after a failed backup or disk error. Restarting the service and then trying the driver install again without toggling protection off might work — but the disable-and-re-enable approach is more reliable because it forces a clean state.

Less common variations of this issue

Sometimes the exact same error shows up in different contexts:

1. Driver install via Device Manager (manual update)

You might see this when trying to update a driver through Device Manager from a local inf file. The fix is identical — disable system protection first, then do the update. The PnP check is the same regardless of how you trigger the install.

2. Windows Update drivers failing silently

Windows Update tries to push a driver, it fails with 0x800F0236, and you just get a generic "Some updates failed" message. The event log will show the error. Again, disable system protection, run Windows Update manually, then re-enable protection. You can trigger Windows Update to re-offer the driver by going to Settings > Windows Update > Advanced options > Optional updates.

3. Third-party installer tools (like Dell Command Update or Lenovo Vantage)

Some OEM driver updaters also hit this. They wrap the same PnP install calls. Disable system protection before running the OEM tool, re-enable after. I've confirmed this works with Dell Command Update version 4.10.0 and Lenovo Commercial Vantage 1.62.

4. After a system restore failure or rollback

If you recently tried to do a system restore and it failed, the restore point database might be left in an inconsistent state. The 0x800F0236 error shows up on any subsequent driver install. Disabling and re-enabling protection clears the database and fixes it permanently.

Prevention

You don't want this to keep happening. Here's how to keep the restore point creation healthy:

Keep at least 5% of your system drive free. Windows gets skittish about restore points below that threshold.
Periodically check the VSS service. If you see it stopped in Services.msc, find out what killed it. Look in Event Viewer under Windows Logs > System for VSS source errors. Common culprits are antivirus scans locking volume snapshots or disk defrag tools running simultaneously.
Manually create a restore point before installing major drivers. Open System Protection tab, click Create, name it. If the manual creation fails, you'll catch the problem before the driver install hits it.
Run vssadmin list shadows from an admin command prompt. If it returns errors, your shadow copy storage is corrupt. Run vssadmin delete shadows /all to wipe them, then recreate a restore point.

One more thing — if you're on a system with system restore disabled by default (some OEMs ship this way), you might never see 0x800F0236 at all. But if you enable it later and hit this error, now you know exactly why and how to work around it.