No system restore on Windows 10
-
I just checked and System Restore was configured for the main (OS) drive, so I clicked the button to create a new restore point and got this error: 'The restore point could not be created for the following reason: The writer experienced a non-transient error. If the backup process is retried, the error is likely to reoccur. (0x800423F4) Please try again.' :confused: :wtf: :( If the error is likely to reoccur, then why would I try again? :wtf:
"Go forth into the source" - Neal Morse
kmoorevs wrote:
non-transient
Permanent residency strikes again! Is this some pro-immigrant code?
#SupportHeForShe Government can give you nothing but what it takes from somebody else. A government big enough to give you everything you want is big enough to take everything you've got, including your freedom.-Ezra Taft Benson You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
-
I just read How to Enable System Restore (and Repair System Problems) on Windows 10[^] and I was absolutely flabbergasted. No more system restore unless you set it up. I use it to fix problems. Now my only option is to have to rebuild my system. Microsoft strikes again with more stupidity.
System Restore was introduced in what, the XP timeframe? By the time Windows 7 was getting old, System Restore still failed to provide anything of value any time I had to deal with a bad crash, so these days I leave it turned off on all the machines I put together. I use virtual machines rather extensively, and there's nothing of value on my VM host, so when I do backups, the virtual disks represent the whole of the machine, so I have a number of backups I can return to...
-
System Restore was introduced in what, the XP timeframe? By the time Windows 7 was getting old, System Restore still failed to provide anything of value any time I had to deal with a bad crash, so these days I leave it turned off on all the machines I put together. I use virtual machines rather extensively, and there's nothing of value on my VM host, so when I do backups, the virtual disks represent the whole of the machine, so I have a number of backups I can return to...
I used it a lot and was very happy with. Whenever something got installed on my computer I did not like, I used System Restore to fix the problem. Maybe did not work well for your crashes, but did extremely well at getting rid of unwanted applications that did not want to play nice in the sandbox.
-
I used it a lot and was very happy with. Whenever something got installed on my computer I did not like, I used System Restore to fix the problem. Maybe did not work well for your crashes, but did extremely well at getting rid of unwanted applications that did not want to play nice in the sandbox.
-
If the purpose of said sandbox is isolation, then I'll stick with VMs. I could just never tell with any certainty what it is System Restore would leave alone, and what it would roll back.
That is definately a good solution. Certainly makes testing easy since have a clean system to start with. Just not sure I want to always work with a VM. They are probably better now, but at one time there were some issues is planning to use as a desktop machine.
-
That is definately a good solution. Certainly makes testing easy since have a clean system to start with. Just not sure I want to always work with a VM. They are probably better now, but at one time there were some issues is planning to use as a desktop machine.
I've switched to VMs a few years back and I'm not going back to bare metal. Full system backups are trivial, and the ability to create a checkpoint, try something, then rollback everything back is a godsend as a developer. And since all the (virtualized) hardware looks the same to guest operating systems, I find support for Linux (if that's your thing) to work even better than installing it on real hardware and then fiddling with driver configuration files. Unless I had a need to directly talk to hardware, I couldn't see myself doing it differently.
-
I've switched to VMs a few years back and I'm not going back to bare metal. Full system backups are trivial, and the ability to create a checkpoint, try something, then rollback everything back is a godsend as a developer. And since all the (virtualized) hardware looks the same to guest operating systems, I find support for Linux (if that's your thing) to work even better than installing it on real hardware and then fiddling with driver configuration files. Unless I had a need to directly talk to hardware, I couldn't see myself doing it differently.
What do you run your VMs under?
-
What do you run your VMs under?
Hyper-V. I was first introduced to virtualization through VMware, but frankly for my own needs here at home, I just find Hyper-V easier to manage. I know some people claim VMware provides better physical hardware support (ie, accessing USB devices plugged into the host), but I've never really had a need for that.
-
Hyper-V. I was first introduced to virtualization through VMware, but frankly for my own needs here at home, I just find Hyper-V easier to manage. I know some people claim VMware provides better physical hardware support (ie, accessing USB devices plugged into the host), but I've never really had a need for that.
Very familiar with Hyper-V. In addition to what you point out is can be much better integrated with Windows since Microsoft controls both. Not sure VMWare would work as well, but maybe. The only other one I know of it the old 2005 Virtual Server I think it is called, and it is pretty old now.
-
Very familiar with Hyper-V. In addition to what you point out is can be much better integrated with Windows since Microsoft controls both. Not sure VMWare would work as well, but maybe. The only other one I know of it the old 2005 Virtual Server I think it is called, and it is pretty old now.
Somehow I doubt you could even install Virtual Server on a recent version of Windows. I remember using it along with Virtual PC back in the day. Never tried VirtualBox. I've had the misfortune of having to use VMware's ESX virtual server (running on bare metal). People at my office somehow managed to get it "disconnected" from the drives hosting the virtual machines at one point, and could never get it going again.