How to Remove Win32:Vitro Manually
I thought I should add a few more comments here, primarily because the steps outlined in the above post by Cerepukas, while in the first sense basically correct, are not to be taken up lightly. A pre-cautionary warning is necessary. Despite that pointers and guides to most of the above actions on the registry are readily available in Microsoft knowledge base (kb) articles. The Windows registry being a mainstay of MS operating systems going back to when Bill and his pals were putting together OS to load into the IBM PCs.
Learning the registry can be an immense asset when it comes to putting systems right when they have been infected, or have become corrupted, or have simply run out of good condition and need tuning up. But be warned, one mistake can alter the smooth running of your system forever. While it has never been easier to edit the Windows registry, such a resort is no longer regarded as necessary for the majority of computer users. Windows OS are comfortably run from application level with simple user interfaces covering all needed systems tools. MMC functionality in Administrative Tools is prime example of this. But if you do want to delve deeper, what you will need is patience and resourcefulness. You will need an eye for detail and a keen memory. You will need to be able to think and work fast in areas where one wrong click may put you further back than where you started from.
I first put major time into the registry taking out the damage caused by viral infections rather than taking out the viruses themselves, which thanks to avast were being knocked over not long after an infected PC came through the front door. But, very importantly, these viruses were hardly ever knocked over completely. So some tidy up was necessary most times, and edit of the registry was one part of that tidy up. Nowadays with all the changes taking place and the heightening of viral infestations through iframe and injekt exploits, I doubt whether there are any easy, black and white methods to take out malware anymore. To take out vitro through black and white deletion, you would not only need the patience of Job, but also the insight of Albert Einsten, coupled with the eye and attention of Tim Berners Lee. Nevertheless, the more you engage yourself in malware detection and removal, the more you will need to go to the registry for one thing or another. And bear in mind when you do go there, that the registry is readily accessible in Safe Mode.
Good practice for the registry - where I started - is after uninstalling a program with a removal tool, you might want to remove all remnants of the program from your system. You can do that in the registry as outlined in the post above by Cerepukas - put the program signature (most appropriate title - e.g AVG, Norton, and then next run, Symantec, etc.. - into the
Find function under the
Edit tab and start removing your finds one after the other - F3 will perform
Find Next on most computers). Take care, though, AVG will take you to AVGeneralNotification and AVGrabber, which are entries you do not want to delete. I spent months removing AVG fragments from registries after viruses had splattered themselves at will across supposedly defended systems. And I will never forget. AVG may have cleaned up its act, but I will never forget. Hence, the broadsides I throw at AVG antivirus every now and then. And I wasn't alone. There were a few of us batting it out at the time, when no thanks at all AVG was just getting bigger and bigger. But I digress. The registry. Don't go there. That's what I tell people. Best advice you could ever give them. But if you have to go there, good practice is to build time there by taking out remnants of Norton / Symantec (especially) after you've first used their removal tool. Get to know your registry editor and how to differentiate between parts of register (which is the record of your computer). There is lots of good stuff in Microsoft Help and Support (Explorer) as well as in kb articles and the like at microsoft.com (Internet Explorer). But you don't need all that to clean out remnants of uninstalled programs, what you need is not to make any mistakes, that's what you need. So learning removal routines is good practice. You will also need to learn about permissions, which Cerepukas has not mentioned in the steps above. Some entries will not delete unless you change permissions, and even then will not delete, so you try in Safe Mode, and then still will not delete, so you go to Safe Mode with command line (or Run, type
cmd in Normal Mode), in which case you are reaching the last resorts of the last resort that the registry has come to be rightly regarded as. Very good point above, though, where the use of command line has been outlined amongst the steps to take because you will sometimes need to resort to this final avenue when caught up with a particularly sticky file or registry entry. But all in all, do practice with removing leftovers of common programs that you have uninstalled, as a relatively safe way of getting to know the registry. I recently removed leftovers of the Nero suite after an uninstall, and that's quite an intensive task in itself. There are a lot of entries to work through and its all exhaustive manual work. And you don't need to do it. Many techs would tell you not to bother at all, what a cleaner doesn't get, doesn't really matter, your system just ignores all those leftover bits and pieces. Which is also true. (In some cases with antivirus programs, I believe manual clean of registry does matter. Obviously). But if you think you have to, then build up time in there bit by bit, and the best way to do that is through learning good practice as you go.
Other than that, I'm not so sure about this step --- How to stop Win32:Vitro processes:
Others in the forum may offer more guidance. I don't often edit through Task Manager, although I have done so, mostly following a directive from some Microsoft kb article or similar, where all the signals are proving correct. Usual I only check Task Manager to see whats up, or to see that changes I have made are working proper, and things are returning to normal. More to check performance, really. But others posting to the forum may offer more about Task Manager, or add something to anything else that I might have said in this post.
