Windows – How to Prevent System Restore Point During Install

Show your actual VSS-Storage-limitations with vssadmin list shadowstorage.

Resize it with vssadmin resize shadowstorage /for=C: /on=C: /maxsize=10GB
For Maxsize you can use percentage (/maxsize=3%), unlimited (/maxsize=UNBOUNDED) or MB/GB (/maxsize=10GB).

Edit: you must at least specify 300MB for shadowstorage.

Update:
I think I found something that should work. According to this Blogpost you can stop the VSS-Service and configure it to start manually. That should prevent the System from doing Shadow-Copies. If you want to restore or create a System-Restore-Point, the service will be started automatically.

However Windows 7 creates System-Restore-Points periodically. If you don't want Windows to do this, you can modify the scheduled task like described on How-To Geek.

I hope that helps. Let me know if you've additional questions.

I will provide all the necessary steps to detect and resolve the problem.

• You should run basic tests such as disk check (chkdsk /f /r /v with a command prompt).
• Run sfc /scannow. It is possible both of these won't provide a negative result. In that case, jump to next steps.
• Make sure no third party backup software is preventing the process. Could be a driver installed by a third party software.
• Note that you can run vssadmin list writers command and check the status of writers.
• This could be a problem with reparse points. Reparse points pointing to wrong locations. To avoid issues, remove any fat partitions (DIR /AL /S command lists junctions with folders).
• You need to apply other system patches and service packs as well.

You have already tried these:

• In a command prompt, run the following commands.
• cd c:\Windows\System32
• net stop vss
• net stop swprv
• regsvr32 ole32.dll
• regsvr32 oleaut32.dll
• regsvr32 vss_ps.dll
• Vssvc /Register
• regsvr32 /i swprv.dll
• regsvr32 /i eventcls.dll
• regsvr32 es.dll
• regsvr32 stdprov.dll
• regsvr32 vssui.dll
• regsvr32 msxml.dll
• regsvr32 msxml3.dll
• regsvr32 msxml4.dll
• net start vss
• shutdown /r (reboot)

After rebooting:

• vssadmin list writers. Check whether the writers have any errors.

If the problem still outstanding:

You need to also check the hard disk by using either a live cd and performing disk checks (or with in built tools - computer manufacturer). You can also use tolls like hdtune or seatools (which is free). This could be an IO error or BIOS faulty configuration (RAID if used or SATA and power Raid or AHCI settings). Carefully examine the settings. All the firmware should be up to date. Make sure you perform a malware scan along with that. With that, check whether any process takes too much resources.

Make sure your BIOS is up to date and chipset drivers and graphics drivers are NOT raising any issues. Disk has to be formatted as NTFS. This can be easily found from using performance counters/reliability monitor and event viewer system logs. In case if you are using nVidia systems, use the drivers from nVidia (not from MS Updates. However, there were instances where default Windows or older drivers not resulting issues). Then examine the logs. If you encounter nvstor64 this is due to the driver issues or disk failures (future). Note that nvstor64 report errors related to RAID or Non-RAID devices.

How to configure Resource Monitor: Microsoft Resources