How to restore system after installing problematic driver

Ask your support questions in here

Moderator: Moderator Team

Post Reply
Posts: 34
Joined: Sun Sep 18, 2016 9:53 am

How to restore system after installing problematic driver

Post by matthiasbasler » Sun May 26, 2019 9:15 pm

My question to those testers with more experience is: Is there a way to restore a broken configuration without having to re-install ReactOS from scratch?

Testing drivers on real hardware is a very time consuming thing, because if something fails I cannot just revert to an earlier VM state. And things fail quite often, resulting in ReactOS not booting any more, showing BSOD and similar. Up to now I found no way except re-installing ReactOS from scratch. (Currently with CORE-15874 open every re-install requires me to take out the HDD and replace two files in order to get it booting at all, making this process even more frustrating.)

There is a "last known good configuration" option in the ReactOS F8 boot menu, but this does not seem to do what it claims to do. What's the state of this function in 0.4.12?
Any help is appreciated.

Matthias Basler

Posts: 532
Joined: Sat Dec 31, 2005 4:19 am

Re: How to restore system after installing problematic driver

Post by MadWolf » Mon May 27, 2019 12:39 am

I do not test real hardware but what about using something like Clonezilla then you can setup Reactos the way you want then Make a backup image and then you can restore that image when you need too

Posts: 251
Joined: Sun Jul 11, 2010 11:39 am

Re: How to restore system after installing problematic driver

Post by ThFabba » Sat Jun 08, 2019 8:06 am

If you need to make modifications to the system in order to get it to boot, simply build an ISO with those modifications already built-in.
Other than that, a good trick is to have two hard drives or partitions, storing the OS on one and any data or software on the other. That way you can reinstall and format without having to re-copy a lot of stuff.
Regularly breaking the OS and its filesystem is pretty much expected at this point and will only be "fixed" once we have things like journaling FSes, registry logs, a working chkdsk, SFC, system restore etc. Most folks don't bother with workarounds and just reinstall the OS when needed.

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest