Author Topic: System restore points not saved  (Read 8336 times)

0 Members and 1 Guest are viewing this topic.

Offline pandafoot

  • Newbie
  • *
  • Join Date: Aug 2014
  • Posts: 6
  • Karma: 0
    • View Profile
System restore points not saved
« on: November 30, 2016, 09:32:44 am »
 I ran Tweaking Windows 3.5.17 (latest) on WIN 10 system.  All repairs done via SAFE Mode thru the Tweaking interface.

Followed all tabs and did backups. Found later that the System Restore points did not save.
(After running all the repairs system didn't seem right so tried to return to earlier time.)

Ran Tweaking Windows again but it stopped at Step 2.
Ran scannow again but no problems found.

Had to restore an old Registry Backup from Tweaking to get system to work again.  Internet (wifi) did not work so could not connect.

Copy of log
03 - Reset Service Permissions
   Start (11/30/2016 10:34:47 AM)

   Running Repair Under Current User Account
   Running Repair Under System Account

The current repair has failed to start for over 30 sec.
Trying Again....

   Running Repair Under System Account

The current repair has failed to start for over 30 sec.
Trying Again....

   Running Repair Under System Account

The current repair has failed to start for over 30 sec.
 :smiley: :smiley:

Offline Willy2

  • Hero Member
  • *****
  • Join Date: Oct 2011
  • Posts: 1165
  • Karma: 18
    • View Profile
Re: System restore points not saved
« Reply #1 on: November 30, 2016, 01:41:37 pm »
- How much disk space have you allocated for System Restore Points (SRPs) ? If that amount is too little then Windows won't make a SRP at all. (Let Windows manage the size of the SRPs.)

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 10182
  • Location: UK
  • Karma: 122
    • View Profile
Re: System restore points not saved
« Reply #2 on: November 30, 2016, 02:51:48 pm »
It's not the first time that a WR created restore point has failed to save - I prefer to use the registry back up option which I have more faith in.

However, I'd advise against running WR on Win 10 for the moment because MS has made serious changes to the registry since the August Update that problems are being caused with Permissions and default apps.

I've aske one of the site Admins to see if he can add a caveat to that effect on the home page.

Hopefully, v4.0 which Shane is working on will address that.

What's your problem that you decided you to run WR - perhaps there's another approach we can take.

I quite often do a repair install if I'm not happy with the way things are running in Win 10.