Main Forum > General Computer Support
Windows 7 Ult 64 bit trapped by BSD and can not get out.
FreeCat:
Howdy Bloggin and Satnow,
Yes I did run chkdsk 0 errors and I believe the /R was the parameter.
eSet still running (10+ hours so far) and 7 threats found. I hope these 7 threats are listed with some option to delete them when eSet is done. :|
So, I guess it is best to wait before proceeding with the other suggestions like attempting the uninstall of W7 updates.
BTW, I did have BitDefender and it worked too well interfering with my life streaming data. so I attempted to uninstall it over a year ago; some of it stopped working; but there was always a ghost of it running. I remember one was AVG and there were two more; what were the other two?
I will prolly try the other one you mentioned once I get out of this mess.
Yes, Jim is mailing me these hotfixes.
I will turn on system protection.
I just ran the new BitDefender un-install so hopefully it is now totally gone.
I do not understand the disk error you pointed out (volume 4?). As I said the chkdsk ran and said 0 errors as per the long printout from yesterday. I am pretty sure that the /R parameter was used. Is there way to tell from the log?
Does not the Tweaking all in one tool clean things up like the left over BitDefender scrap?
I am trying the uninstalls as soon as eSet is done.
FreeCat:
OK - eSat just ended so th's like 15 hours.
Good. But, after selecting all and delete selected eSet seems to be doing nothing - just sitting there no message that it is working, etc.
See attached screen and list of what it found.
BTW, WIREDTOOLS seems to be where most of the virus was. I tried to uninstall it and got message "program does not exist."
What do you suggest?
Boggin:
The chkdsk Event Viewer entry was some hours older to your last boot and it didn't reappear during the latest boot that was recorded but thought I should mention it.
It's been a while since I ran ESET but I think it should give you a box to check to uninstall the program on completion.
I'll run it on my Win 7 laptop and as I don't expect it to find anything, it could still run for an hour or so, but will get back to you on that.
I think the longest it has ran on mine was about 1¾hrs.
One of the boxes that you checked was to clean automatically, but I'll see how that goes on mine.
I should have said to also check the top button of those two options as well as those in the Advanced settings.
I can't advise what to do with ESET until it completes on mine.
This article which includes a download link will show you how to remove the WiredTools.dll using FreeFixer.
http://www.freefixer.com/library/file/WiredTools.dll-139610/
As for the ones in Program Files(x86) - go Start - click on Computer - double click on Windows (C: ) then double click on Program Files (x86) and scroll down to look for any folders with the name WiredTools - right click on them and select Delete.
Unless you had installed WiredTools, it could have been installed as an unwanted bundled program when you downloaded something else.
When downloading anything you should always look to see if there are any boxes auto checked before hitting Next or Install.
Windows Repair can repair damage caused by infections but not until the infection has been removed.
Boggin:
It's finally finished after 1hr 31mins with no threats found on a summary page with a box to Delete application's data on close.
If still nothing has happened for you, then use the X to close the window and see if it gives you a message.
FreeCat:
Howdy Bloggin and Satnow,
I did it all; I was confused at times but got thru all you suggested; I think. :)
the eSet ended after about 15 hours. It found 10 things --- all were related to Wiredtools; I do not remember installing any Wiredtools --- even (on my NAS I keep the install files for everything that I install in my "1 DOWNLOADS" folder --- nothing there). I selected remove all and ended eSet with remove files from quarantine and remove applications files. "Remove from quarantine" lead me to believe maybe put back where they came from; but, I guessed right, I am hoping.
Still could not go into protect mode and could still not run scannow, but I figured I might try after a reboot with the new instructions; but now, I am sending you all this up-to-date stuff before I loose track of it. So, doing that right after I send this.
I deleted the Wiredtools in the Program Files (x86) folder. Image attached.
Filefixer found an enormous amount of stuff. I got to believe that what it found is some kind of mistake. But, I dunno. I did not check any boxes.
I have zipped the collection of stuff which is attached along with the BSOD (still the win32k) that I can after running all this.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version