Avast WEBforum

Other => General Topics => Topic started by: merckxist on March 23, 2016, 09:02:30 PM

Title: Avast, Win 10 and System Restore
Post by: merckxist on March 23, 2016, 09:02:30 PM
I tried asking about a tip in Tips Tricks and Other Helpful Advice in regards to System Restore but the advice was:

@Mertchxist, (sic)
I suggest that you start your own topic. :)

So perhaps I got too detailed or off the OPs original intent so let me try again from a slightly different angle.

The Tip, https://forum.avast.com/index.php?topic=164936.msg1284599#msg1284599, showed how to create a reliable System Restore point by disabling Avast self-defense module before the SR point was generated. Based on my experience with SR and prior versions of Avast and Windows, I thought this was validation that the Avast self-defense module could have an impact on the chances of getting a clean recovery from the SR point and that it was a smart idea to take these steps. So now I'm wondering how to integrate this process with the Windows 10 "automatic update" feature.

Based on other posts I've seen here it may be possible to get a good recovery by running SR in a Windows RE mode regardless of whether Avast self-defense was enabled when the SR point was TAKEN (as opposed to applied). Anybody test or confirm that? That's a bit more cumbersome than self-defense off/on, but gets around self-defense ON when Windows automatically updates.

Otherwise, I guess one is left with the "restore from backup option" if the SR point from a MS update can't be completed because Avast self-defense was enabled while Windows updates were being installed.

Any other options for getting a clean recovery of a Windows update gone wrong by using its SR point with Avast in the mix?
Title: Re: Avast, Win 10 and System Restore
Post by: bob3160 on March 24, 2016, 11:12:06 PM
I have noticed that Avast no longer creates a restore point prior to updating it's program ???
I'm reporting this post to Avast in order to get a reply directly from them on this issue.
(The issue had been reported as fixed some versions back.
Apparently it's again surfaced it's ugly hat.  :(