cd /d %windir%system32net stop vssnet stop swprvregsvr32 /s ole32.dllregsvr32 /s oleaut32.dllregsvr32 /s vss_ps.dllvssvc /registerregsvr32 /s /i swprv.dllregsvr32 /s /i eventcls.dllregsvr32 /s es.dllregsvr32 /s stdprov.dllregsvr32 /s vssui.dllregsvr32 /s msxml.dllregsvr32 /s msxml3.dllregsvr32 /s msxml4.dllvssvc /registernet start swprvnet start vss
Once you have re-registered the VSS components, close CMD and try to create the restore point again.
If a problem in VSS components is causing the problem, restarting the components will fix the problem.
In some cases, conflicting background processes can also prevent the System Restore utility from creating a successful restore point. The best way to make sure there are no apps or programs running in the background interrupting System Restore's functionality is to try creating a restore point in Safe Mode.
This mode launches Windows with a minimal set of drivers and services, which can help isolate problems and prevent any possible conflicts in normal mode. Here's how you can boot into Safe Mode:
After entering Safe Mode, try creating a restore point again and check if the problem is resolved.
The System Restore utility itself may be experiencing corruption errors that prevent it from working properly. To repair any corrupted system files, you should use the System File Checker (SFC) and Deployment Image Servicing and Management (DISM) tools. SFC works by scanning protected system files for potential problems. If an issue is detected, it will replace the corrupted file with the error-free cached version.
DISM, on the other hand, works by repairing corrupted system images. TipsMake has a guide on how to use SFC and DISM in Windows that you can refer to for the right steps.