New
#11
Hmmm - either the replacement didn't happen properly, or the error is actually in the registry.
I'll do some research and see what I can find out about the registry end of things.
Hmmm - either the replacement didn't happen properly, or the error is actually in the registry.
I'll do some research and see what I can find out about the registry end of things.
Thank you, Noel.
In the meantime, do you think it is safe to use this computer for more secure activities, like ordering from Amazon?
Before I came to this forum, I looked at some sites that suggested the problem could be malware. I ran Emsisoft, MalwareBytes, SuperAntispyware, and SpyBot without any serious problems found, although free Emsisoft was finding things with Behavior Blocker that mostly looked like cookies, until I disabled the search for PUP's. Some indicated that the behavior was similar to a backdoor vulnerability, but when I disabled the PUP selection, nothing whatsoever showed up after that. I had been using free Avast for protection, but uninstalled it temporarily, and also uninstalled free Emsisoft, and installed the trial of the full version of Emsisoft protection. Since using the new full-protection Emsisoft installation, nothing is showing up as a threat in Behavior Blocker, or otherwise. (I will probably return to Avast once the trial period for Emsisoft full protection is over.)
I also ran online Bitdefender and ESET with no threats found.
Then after I came to this forum, I ran MalwareBytes, SuperAntispyware, and CCleaner again, as well as adwcleaner, as recommended in post #4, with no enlightening results.
Another suggestion found online that I implemented was the possible need to download and run the Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package MFC Security Update, as well as the Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update, as I mentioned in my initial post.
(There was still another suggestion that it could be the need for drivers to be updated. I checked the drivers and did update a couple of them, with no change to the problem.)
So my best guess is that the computer is likely safe from malware, but I wonder if you concur with that, as I am hesitating to use it for more secure activities.
Thanks so much for your help, Noel.
You've used some of the best malware tools around, so if they are consistently saying the system is clean, I'd tend to believe them.
Back Later
Thanks, Noel. I was hoping I wasn't missing anything re: checking for malware. I can run the replacement again, if you think it would be worth a try?
Am still watching BG and I don't know what Noel thinks but personally I would run this as it doesn't involve Windows staring up and scans just about everything plus it doesn't take long.
Download Kaspersky Rescue Disk 10 a little more info at
Kaspersky Rescue Disk 10
There are other rescue bootable disks but this is usually the one to use - or at least I do.
Running the fix I posted again may work - make sure that you use the correct drive letter, and make a note of any error messages received in the process.
Thanks IC and Noel.
I ran the fix again today - twice, actually. (Newest CBS Log is attached.) But the scannow results still gave the msg about being unable to fix corrupt files. (I'll run that Kaspersky scan next.)
I copied the following from the Repair My Computer command prompt window, after viewing the C drive Not Found message and then typing "DIR D:\bg1aa":
X:\windows\system32>DIR D:\bg1aa
Volume in Drive D has no label
Volume Serial Number is DC08-C659
Directory of DIR D:\bg1aa
12/10/2014 12:19 PM <DIR> . < that's one dot to the left
12/10/2014 12:19 PM <DIR> .. < two dots to the left
12/10/2014 12:19 PM <DIR> bg1aa
0 File(s) 0 bytes
3 DIR(s) 93,593,608,182 bytes free
I don't know if the above information is of any use, but there it is, just in case....
I'm also still wondering if there might be anything to the unusual possible fix I found and pasted to post #5 - what do you think?
Thanks again for helping me with this!
You need to use this command while in the Repair environment - you seem to have got an extra level into the folder structure...
XCOPY D:\bg1aa\bg1aa D:\windows\winsxs /y /i /s /v /h
Here's the new CBS log. "Windows Resource Protection did not find any integrity violations."
So I guess ATL80.dll is now found! Maybe the problem is resolved completely? If so, do you know how the problem could have happened?
Thank you so much... I will test the areas where the problem popped up and let you know how that works.
Great - with any luck your error message will have gone as well.
There's no errors in the CBS data at all currently.