This article shows how to stop the Harddisk space usage of System Restore in Vista
How System Restore works
System Restore is designed to take snapshots, called restore points, of your system state before certain types of operations, such as installing new drivers or installing Windows updates, are initiated. That way if a problem results from those types of operations, you can revert back to the restore point and essentially recover, or restore, your system to the state that it was in before the problem occurred.
These snapshots are taken by the Volume Shadow Copy Service. In addition to taking care of creating the restore points, the Volume Shadow Copy Service also monitors data files for the Previous Versions feature.
In order to manage the Volume Shadow Copy Service and ultimately System Restore, you’ll use the VSSAdmin command-line tool — there is no GUI tool in Vista for configuring System Restore. In order to run VSSAdmin, you must launch an elevated Command Prompt window.
right-click on the Command Prompt shortcut
select the Run as Administrator command
When you encounter the UAC, you will need to respond appropriately.
You can now use the VSSAdmin command-line tool
to investigate and configure System Restore and the Shadow Copy Service.
For example, you can obtain a list of all the restore points currently saved on the system by using the command: vssadmin list shadows
You can see how much disk space is allocated to and used by System Restore and the Shadow Copy Service system by using the command:
c:\> vssadmin list shadowstorage
On the Vista system that was running out of disk space, the result of the vssadmin list shadowstorage command is shown in Figure A. As you can see the Maximum Shadow Copy Storage space settings was set to Unbounded, which means that there is no limit to the size it can grow and it was already at 40GB.
The Maximum Shadow Copy Storage space setting on the problem system was set to Unbounded.
On another Vista test system, running on an 80GB hard disk, the Maximum Shadow Copy Storage space setting was set to 11GB, as shown in Figure B. This was a much more reasonable value. Why the value on one of my test systems was set to unbounded while the others had specific maximum values, I’m not sure.
The Maximum Shadow Copy Storage space setting on another system was set to 11GB.
You can reset the value of the Maximum Shadow Copy Storage space setting using the command:
vssadmin resize shadowstorage /for= /on= [/maxsize=
e.g.. i will reset the Maximum Shadow Copy Storage space setting to 15GB using the
vssadmin resize shadowstorage /for=c: /on=c: /maxsize=15GB
Once the operation was complete, I restarted the system, and everything has been running normally since