jtr1962
Flashaholic
On March 18 my machine suddenly refused to run cmd or regedit from the run window. Cmd worked by renaming the .exe to something else but regedit didn't work no matter what. I also noticed that my Google searches were being redirected to various ad sites. I ignored this at first, attributing it to some new campaign by Google to link to ads related to your search terms. Recently however I started doing Google searchs using the term "Regedit, cmd not working, google searches being redirected". Boom-I was getting loads of hits of people experiencing the same problems. Moreover, all their antimalware scans using various softwares were coming up negative, just like mine. I figured somewhere down the road some vital part of my O/S perhaps got trashed, maybe from the hard shutdown I had to do immediately before the problem started. After all, my system was clean, wasn't it? Or at least that's what about 10 different trusted antimalware programs said.
Well, turns out no. This is a new Trojan, termed "Trojan.Win32.Agent.byab", which no antimalware software was aware of until recently. My fix was actually beautifully simple. I downloaded a program called Regalyzer as Regedit wasn't working. Then I went to the key HKLM/SOFTWARE/Microsoft/WindowsNT/CurrentVersion/Drivers32/aux. Sure enough, the data referred to some junk filename. I changed it to wdmaud.drv as it's supposed to be. I restarted the system (for some reason it didn't want to shut down so I ended doing another hard reboot). Problem solved.
Now all I need is to find the person(s) responsible so I can test my late Dad's Louisville Slugger on them. :devil:
Hope this helps anyone who may be experiencing a similar problem. I'd guess the major symptom for most people would be the Google redirects as not too many use regedit or cmd on a regular basis.
Well, turns out no. This is a new Trojan, termed "Trojan.Win32.Agent.byab", which no antimalware software was aware of until recently. My fix was actually beautifully simple. I downloaded a program called Regalyzer as Regedit wasn't working. Then I went to the key HKLM/SOFTWARE/Microsoft/WindowsNT/CurrentVersion/Drivers32/aux. Sure enough, the data referred to some junk filename. I changed it to wdmaud.drv as it's supposed to be. I restarted the system (for some reason it didn't want to shut down so I ended doing another hard reboot). Problem solved.
Now all I need is to find the person(s) responsible so I can test my late Dad's Louisville Slugger on them. :devil:
Hope this helps anyone who may be experiencing a similar problem. I'd guess the major symptom for most people would be the Google redirects as not too many use regedit or cmd on a regular basis.