Avast 2015 preventing system restore?

I am not able to do a system restore. After trying to do a restore that was unsuccessful, Avast did not start. I tried to undo the restore and it was not successful. Avast did not start again. Disabled file shield and tried. Still no success with system restore, but Avast did turn on.

Do I have to uninstall Avast to do a system restore?

I am replying to my own post. I tried several ways of doing a system restore with Avast enabled, partially enabled and turned off and could not get a successful system restore. I uninstalled Avast and the System Restore worked fine. I did not have this problem with Avast 2014, so I think this is another issue Avast needs to deal with in the new version. I liked the protection, but having to restart after a temporary disable and now an uninstall to do a system restore is a bit too much.

I hope the Avast staff takes note of this issue.

You need to disable avasts self protection before doing a restore, personally I’d being doing weekly image backups rather than restores anyway as it’s much more complete and reliable.

What do you mean by disabling Avast’s self protection? I disabled the shields. Is there something else I should have done.

See this thread: https://forum.avast.com/index.php?topic=160448.msg1151663#msg1151663
BTW…even though Avast team asked for feedback in linked thread they never ever responded.
To me, system restore and Avast working with it seem an important function and I think they would want to understand.
While there are a lot of great Super Posters here that help solve problems the involvement of the Avast Team is limited. :frowning:

Also, FYI…there are posts where using NG has caused problems with System Restore.
Personally, while I think the “'concept” of NG is great the current implementation is suspect/buggy and takes WAY too many PC resources. The combo of that and that people have had issues corrupting System Restore I’ve disabled from the installer.

As I said… disable Avasts self protection in settings ( no need to disable shields ).

A ludicrous state of affairs where you have to go through this hoo-haa with an AV to get System Restore to work or to ensure the AV still functions properly afterwards.

What happens if you do a System Restore (offline) in Safe Mode which is what I would suggest should be standard practice? Do the same problems occur?

Avast doesn’t run when in safe mode as far as I know.

The task of first disabling avasts self protection before performing a restore has been that way for a few years now, it should be common knowledge by now but I do agree that one shouldn’t have to jump through hoops just to do a simple restore though I recommend a system image as a much better option and it doesn’t require disabling avasts self protection first.

Well it is news to me and consequentally useful info.

I agree that using one of the many good, free backup programs available to create a full backup system image is safer practice. However I think that tools like that should be seen as safety nets and not the first go to solution. For me that is letting AVAST off the hook.

Windows System Restore is the OS system’s provided restore tool and AVAST’s default features/settings should not be preventing it working properly or be messed up when it is used.

So I’d still be interested to know 100% for sure that if you use System Restore offline in Safe Mode, as I suggested, that these issues with AVAST won’t arise.

What kills me is that since A/Vs like Avast are becoming more and more intrusive in the O/S that Avast Team has no response to this “common knowledge” issue of System Restore. As you guys stated, a offline image backup is best but I think Avast should work with System Restore as a fundamental no-brainer.

So, my disappointment with Avast aside on the subject…I can tell you that I’ve had no issues with System Restore working but Avast is corrupt afterwards…unless I disable the self protection module. So, my guess (only a guess since I have no real knowledge of this) is that the SPM is monitoring things that fundamentally a system restore mucks up. So, as you put it will it work in Safe Mode ?..I can only hazard a guess that it would since Avast is not running and would think neither is SPM. However, with this all said…if I have to do a System Restore I turn off all A/V & MBAM Pro Shields, and disable Avast SPM. Have not had to do a System Restore (knock on wood) in a long time but in my experience this is solid. Worst case in my experience a clean un/re-install of Avast is needed I this does not work.

What I “really” worry about is that people have had the new NG “feature” of Avast cause issues with the System Restore itself. Personally, I only use the Avast Shields…no Tools EVER do I install. However, I think NG IMHO will be a great A/V feature for Avast in the future but for me I think it is too early and has too many issues for the benefit. I draw the line as an early adopter of new features that pose more risk to the stability of my PC than they protect. As they say, there is “leading edge” and “bleeding edge”. :slight_smile:

Windows 7, 8 and 8.1 all have built into the OS the ability to create system image backups.

I use it all the time and it is a whole lot better than system restore.

I have a hard drive dock and can add/remove a drive to back up to just like you used to add/remove a floppy.

http://www.howtogeek.com/howto/4241/how-to-create-a-system-image-in-windows-7/

Avast needs to warn users about this problem!

I spent almost two full days trying to fix System Restore failures on Win8.1 64-bit that were apparently caused by Avast, though Microsoft diagnosed the problem as, “This is due to the system boot files are missing or corrupted.” (http://tinyurl.com/qf4nlnm). I eventually reinstalled Win8, restored a System Image backup, and when I found that System Restore still didn’t work I completely removed Avast and finally System Restore worked again.

This was so time-consuming because:

  • Early in the process I googled “system restore 0x80070005 site:avast.com” but didn’t come across this post or anything definitive
  • MS said boot files were the problem
  • Attempting System Restore in safe mode also failed, and I expected Avast to be disabled in safe mode
  • Disabling Active Protection shields appears to disable avast, but apparently doesn’t

KevTech’s suggestion to use System Image Backup makes sense, but it’s not at all obvious, buried as a small icon in the lower left corner of the “File History” Control Panel item. The “Enable Avast self-defense module” check box isn’t at all obvious either under Troubleshooting.

Why should avast warn users about this?
It is not avast that is causing the problem, but Windows.
Users should learn what system restore is.
It is just as it says…
It restores (some) system settings/files.
Nothing more, nothing less.
avast is not part of the system (Windows) which MS means with system.

Eddy,

Does System Restore work without Avast installed? - Yes
Does System Restore work with Avast installed, even in safe mode or with all Avast shields disabled? - No
Will eventually and painfully discovering that System Restore’s failure began with an Avast update cause some users to blame Avast? - I’d guess yes

Why not at least allow Avast shields control to temporarily disable the self-defense module, if that allows System Restore to work? Avast breaking System Restore may not be unavoidable or even undesirable, but it is unexpected and time-consuming for users to identify, with uninstalling Avast likely an immediate and obvious solution for some users.

Curious, did you ever go into Settings>Troubleshooting and disable Self Defense Module and then try a System Restore ? …was wondering if it worked for you ?

I also agree with you that an A/V should not be corrupting a System Restore…frankly Avast should monitor this and put in hooks to shut down things it needs to in order not to corrupt. Granted, it may be a security hole but when you disable Avast SDM you’ll get a message about being sure…Avast can simply put that hook in if a System Restore is chosen…perhaps not simple but since they are already are mucking around with VM via NG they should be able to figure something out.

Cattledogit

Thanks for the helpful information.

Your right - Avast is the cause of the problem. They are aware of it, but I you probably won’t get an immediate response from them. They have had problems off and on with system restore for years.

https://forum.avast.com/index.php?topic=155852.msg1130180#msg1130180
https://forum.avast.com/index.php?topic=159770.msg1150270#msg1150270
There have also been discussion about this problem in sections of this Forum that many users don’t have access to.
I am still waiting for a fix and still follow the procedure of turning off the self protection mode of avast prior to creating
a system restore point and prior to restoring from a system restore point.

I’m still on 2014/V9 because waiting for 2015 to have more stabilized release.
For 2014 on W7 64-bit I can have System Restore create a Restore point and I “can” restore to that point all with SDM on but Avast is corrupt.
If I disable SDM before restore then Avast is OK.
…but in both scenarios above SDM was “on” when restore point was created.
However, regardless I think your comment about disabling SDM before a restore should always be done.
I think we are seeing/saying different things on Restore Point Creation with SDM…or perhaps you are only talking 2015 ?

This is a continuing problem and has been around long before the current version release.

Just had this issue today. Wasted hours on it.
Did system restore. Didn’t work and I stupidly didn’t read the error and so tried again at a different restore point.
Didn’t work again saw that it said it was Avast causing the issue. No problem will do it in safe mode.
Tried again in safe mode. Didn’t work.
So I came on here and saw some folks say disable defence mode. Tried that and yet again nope it failed.
The restore didn’t work until I removed Avast completely. You shouldn’t have to unstall it to do a simple restore.
I do image my system as well but I just wanted to revert back to one piece of software I had updated earlier that I didnt think much of once it had upgraded.

@Eddy how can you say its not an Avast problem if its Avast that is causing the issue?