Yes it was Avast--the install process required a reboot andwhen it came back up that's when I got the missing or corrupt file message. I mistyped in my previous post--it should have been as follows:This is C:\WINDOWS\system32\config windows registry folder...
C:\windows\system32\Config\ system missing or corrupt
Norton AV was installed at the time but I disabled it prior to the Avast install.Disable is not enough... NEVER WAS...
nope --it still produces the Winx XP missing or corupted file error messageYour registry files are corrupt... for sure avast does not do this... seems a physical error on the disk.
None of the recovery consule functions are fixing the problem Avast caused -fixmbr, fixboot. It will not even boot into safe mode or last working configuration mode.
AVAST really trashed something bad--
NO never used that program--never needed it!Well, for now on, you know how a registry backup/recovery tool is important.
None of the recovery consule functions are fixing the problem Avast caused -fixmbr, fixboot.These functions just help the 'boot' or the 'MBR - Master Boot Record' troubles.
It will not even boot into safe mode or last working configuration mode.This is the worst part... :'(
What else do you recomend I do. Have been working on solving problem for nearly 24 hrs now
To be honest, I think 4.7 is in the process of getting all the bugs ironed out as I feel it was released WAY too soon from BETA testing.Would you care to share on the bugs you mention ?
I reiterate my call (as I made earlier in this thread) to include a warning during the install phase of Avast about potential conflicts with other AV's. I don't think that would be too hard to program in.But this is already there... if you have a second on-access scanner (the major common ones: Norton, Kaspersky, NOD32, Antivir, AVG, etc.) avast will warn you about this.
But this is already there... if you have a second on-access scanner (the major common ones: Norton, Kaspersky, NOD32, Antivir, AVG, etc.) avast will warn you about this.I'm not sure at what point it checks for other AVs, but I get the idea that it is not prior to starting the install but during the install when it may disable elements of avast to try and avoid a conflict, it is at that point were you may be alerted.
I'm not sure at what point it checks for other AVs, but I get the idea that it is not prior to starting the install but during the install when it may disable elements of avast to try and avoid a conflict, it is at that point were you may be alerted.I agree... I wish this if this is possible.
If there was a routine that ran the check first and if found advise uninstall and boot of other AV and exit the setup process. If nothing is present continue the avast setup.
Yes it may be difficult to find every remnant of either a failed uninstall or registry keys, etc. left behind, but it may save this type of issue where nothing is uninstalled.
It is not so much about guilt and more about prevention.
Would you care to share on the bugs you mention ?
When I upgraded from 4.6 to the "public release" of 4.7, directly after the reboot, my internet connection went down to the tubes. I could get online but could not get web pages or e-mail to come up or work properly. And after I uninstalled Avast, everything worked fine again. Would that not be a "bug?" Or is it just a figment of my imagination?
I have a feeling Norton was, at least, partially the culprit here.I'm quite sure Norton IS the culprit here :P