Eight days ago I received a new desktop from Falcon Northwest and have been in the process of setting it up for general use and photoprocessing...not gaming. It is running windows 8.1, installed by Falcon. It has Windows Explorer but I am using Firefox. I am using Live Mail. Windows Defender is enabled and, about two days after I started using the machine, got MalwareBytes loaded.
Early-on I noticed that when using either browser the screen suddenly, randomly, became populated with various ads, warnings about my computer and offers of assistance if I would 'click here'...which I didn't. Some of these would step on the Pandora audio and intrude aurally. The machine seems to be running otherwise normally (though I have little feel yet for what constitutes normal). No blue screens or omnious warnings.
On 3/10 I did a full malware scan and 30 threats popped up. They were located in Memory Processes, Registry Keys, Folders and Files. Almost all were PUP.Optional, BetterBrowse, all were located on C:\ and all were said to be deleted and quarantined successfully. A full Defender scan showed nothing.
I thought that this would have taken care of the problem but it continues.
Today I ran another malware quick scan and it was clean. I next ran the ESET scan and it chowed 16 threats equally divided between D:\ and F:\ (a Drobo). These were all Win/32Adware.Vitrumonde.NEOapplication. ESET reported that they were deleted.
At that point I went back to #1 and used TFC. It seemed to get stuck and required Task Manager to halt it. But the second time I ran it it reported all folders emptied:0 bytes. It never saif to reboot or not but I did anyway.
I then turned malwarebytes back on, checked for updates, and ran a full scan again (of C;\, D:\ and F:\) and it was clean.
AdwCleaner was then downloaded but the first attempt to run generated a warning that "Windows protected your PC and prevented an unrecognized app from starting which might put your PC at risk...: Clicking for 'info' allowed an override. The Clean button was greyed out. We chose Scan instead and then Clean.
OTL was run without incident as was Security Check.
The final ESET scan was clean.
↧