I have Avast Premier, and a file that begins with \ ?? \ is preventing my attempts to return Window 10 back to an earlier date. Shields Control has no affect. Anyone know how to get around this … without removing Avast?
The correct link is:
https://forum.avast.com/index.php?topic=164936.msg1284599#msg1284599
Nothing you have sent seems to help. I continue to get the same message, but with different files beyond \Avast.
I have tried finding the file in question using command line with adm, with no success.
I am able to restore by using safe mode, but I’d like to know what is going on with Avast.
Nothing you have sent seems to help.Did you turn off avast self protection?
@ ginnjho
You don’t say exactly what avast version you are using, the latest version being 2016.11.1.2253, what is your version number ?
The reason I ask is that that version is meant to be more tolerant of system restore, but as mentioned, disabling the avast Self Defence Module should get round that.
Did you turn off avast self protection? Yes!
latest version being 2016.11.1.2253, what is your version number ?
Given that you have the latest version of avast and that you disabled the avast self defence module. I’m at a bit of a loss as to why this would be happening.
The strange location ??\ Volume{unique-string-of-characters} before what is an avast location, I just wonder if this isn’t something to d with the avast NG function. I can’t confirm this as I haven’t got the avast NG (Virtual Machine Protection).
@ essexboy
I wonder if essexboy can confirm or deny this (NG theory) ?
I need to turn on system restore in windows 10 as it is off by default
I was thinking more along the lines of with NG enabled you could check to see if that type of unique ID location present. Plus if there was any way to check what created it and if it is indeed protected by something else other than the self defence module.
https://msdn.microsoft.com/en-gb/library/windows/desktop/aa365248(v=vs.85).aspx
What we are looking at here is a guid being used instead of C so that the translation of that is C:\program files\avast…
A volume mount point is any user-mode path that can be used to access a volume. There are three types of volume mount points:A drive letter, for example, "C:\". A volume GUID path, for example, "\\?\Volume{26a21bda-a627-11d7-9931-806e6f6e6963}\". A mounted folder, for example, "C:\MountD\".</blockquote>Now as it is in the defs folder removal of self defense should allow restore to replace/delete the file/folder NG is not involved at all
Thanks for shining some light on that one.
Strange that even with the self defence off it still failed according to OPs attached image 1.
It also makes me wonder what system restore would be doing trying to restore the defs sub-folder.
I highly doubt that that image was taken of a restore point which was made after the self protection was turned off.
The image I sent was taken before I was asked to remove the self protection, but subsequent attempts with it off resulted in the same failure but different file reference … still with ??\ etc. in the location. If you need the file causing the problem I can generate another failure and send the message as before.
While I have your attention (I hope), I’d like to know how to reinstall Avast Premier by downloading the latest version.
Download Avast Uninstall Utility to your Desktop.
Download the correct version of Avast
Avast Free
Avast Pro
Avast Internet Security
Avast Premier
Disconnect from the net
Uninstall Avast via control panel
[]Run the uninstall tool and accept the reboot to safe mode
[]Once complete reboot your system
[*]Reinstall Avast
I’ve had to do the same thing numerous times, even to test restore. If you try and do a system restore without first using the Avast unistall tool, your system restore will not work.
Certainly not my experence:
http://screencast-o-matic.com/screenshots/u/Lh/1458732984831-67294.png
system restore also works flawlessly for me.
skinnypops
I think System Restore within Windows is a key feature and has gotten much better over the years.
It is not a replacement for a off disk (ie. USB HDD) “image” of your system…but it is a very useful recovery mechanism.
However, the history of Windows SR is marked with checkered past of issues with virtualization problems.
Thus, I can only speculate that the development and associated issues with Avast’s “NG” at best does not help, potentially causes problems.
So, with that said on my W7 & W10 machines I have Avast installed, Shields only (definitely no NG), and have no issue with System Restore.
I do sometimes have Avast corrupted after the restore but frankly a clean un-install and re-install of an A/V after a system restore is almost required…definitely recommended IMHO.
This “corruption” of Avast after a restore can happen even with the Avast Self Defense Module turned off prior to restore.
Anyway, my two cents.
That is what happens to me, so I just uninstall Avast and have no issues, even when testing system restore.