I get error message:
the restore point could not be created...
insufficient storage available to create either the shadow copy... (0x8004231F)
I have 4 gb allotted for restore points on this partition, which is my C partition, and there are no existing restore points . So plenty of room. There are 75 gb free on the partition.
I just finished reformatting a different partition on a different hard disk, because the system volume information went beserk, it took up 170 gb, even though I had allotted 0 gb for restore points on that volume, but I couldn't get it to give me the space back. So I backed up my data and reformatted . Now it is behaving itself, but I suspect it is a related problem.
It is possible that there is not enough space, the system creates a snapshot in temporary storage and works from that to create a restore point so that you carry on working while the restore point is being created. Have you created separate partitions for pagefiles or temporary file locations and is it trying to use these?
I am using Rollback Rx, it creates snapshots of the system, on unused portions of the hard disk, in places that windows can't read. Maybe that is the problem?It is possible that there is not enough space, the system creates a snapshot in temporary storage and works from that to create a restore point so that you carry on working while the restore point is being created. Have you created separate partitions for pagefiles or temporary file locations and is it trying to use these?
truth is, I don't really care so much about the windows restore points, I never had much luck with them, and I prefer snapshots and system images to perform my restores. But I was concerned that maybe there is an underlying problem here.
As I mentioned on my original post, something went weird with my other hard disk (there are no snapshots active on it), so I'm a little worried about the health of my system.
You could be right.I am using Rollback Rx, it creates snapshots of the system, on unused portions of the hard disk, in places that windows can't read. Maybe that is the problem?
A Windows system restore point only helps if the system files get corrupted in some way and does nothing for program files or your own data files so a system image backup is much better and I would certainly make a system image backup every week or so.
If there is any underlying system problem you can check for this with the sfc /scannow command.
SFC Command - Run in Windows 10
that scannow command gives false messages about corrupt files in Windows 10, and Microsoft finally admits it:
Microsoft Acknowledges System File Checker Issue in Windows 10 Version 1511 | MalwareTips.comYou could be right.
A Windows system restore point only helps if the system files get corrupted in some way and does nothing for program files or your own data files so a system image backup is much better and I would certainly make a system image backup every week or so.
If there is any underlying system problem you can check for this with the sfc /scannow command.
SFC Command - Run in Windows 10
I suppose I could check out my theory next time I uninstall Rollback. I use it on a SSD, so I have to uninstall it every once in a while, and reboot, and then run TRIM. Then I can reinstall it.I am using Rollback Rx
I am aware of that and I usually check the cbs.log file. If the only problem item mentioned is the opencl.dll file I know that everything else is OK.that scannow command gives false messages about corrupt files in Windows 10, and Microsoft finally admits it:
Microsoft Acknowledges System File Checker Issue in Windows 10 Version 1511 | MalwareTips.com
I uninstalled Rollback, and I was able to create a system restore point.I suppose I could check out my theory next time I uninstall Rollback. I use it on a SSD, so I have to uninstall it every once in a while, and reboot, and then run TRIM. Then I can reinstall it.
