This careless and ridiculous if not malicious damage by the Spybot people: Safer Networking, ranks their program with the worst Malware. I've 'phoned all my family and friends and told them to get Spybot off their computers immediately and to pass the word on to everyone they know. It's the least I can do. For them.
I'm programming a new PC from scratch (it's taken weeks) and fortunately I've been creating backup images of the drive with Acronis.9 at regular intervals. I was nearly finished and put it online last night to update Nod32, Adaware & Spybot and then ran them all in that order. Then I spent hours trying to fix it after using Spybot. I gave up and deployed my last image losing another few hours of recent programming. But because of that I'm one of the lucky ones. I won't have time to get back to my project till Sunday and then only enough time to re-do the work I did last night. *%$#@#$$%
I was hoping to be tuning my firewall and taking it for a test run on the digital superhighways by then.
Spybot's name is mud at the moment. Who will be game to use it again?
Would you? Who've been screwed? You really, really messed up BIG time. *I* suspect someone with a vengeance/grievance :devil: at Safer Networking has added a malicious bit of code to the update files(?). What will it be next time?
"format c:" ?
Bye Bye.
PS
you cannot even supply/check proper information for fixing this:
http://forums.spybot.info/blog.php?b=14
"The required default value and data:
Code:
for Windows XP
Userinit=c:\windows\system32\userinit.exe,
for Windows 2000
Userinit=c:\windowsnt\system32\userinit.exe, " <- win 2000 would be .......c:\WINNT\system32\userinit.exe,
Tut tut.
Please check the information you are providing to your users to end the suffering you have sent them.
olice:
I've seen posts by your 'Team Members' (kid brother/sister?):cowboy: advising to try booting safe mode. Duh? These poor people are locked out. No doors and the 'Windows' are bolted from the inside. I'm guessing you 'Safer Networking' people use Linux when you're at home? So you would know grief as much as windows users. I see one or two forlorn victims crying 'Mac for me' after this fiasco. Another pretty desert island but with very little 'cargo'. Only good thing about Winblows is heaps of garbage washes up and occasionally you find something good. Spybot was a find
but now, as I said, it's got covered in mud :sad:.
I suggest you remove all update files from your servers and replace them with a text file only containing a warning, an apology and promises that whatever bums are actually on seats at 'Safer Networking' are really working to make the program 'Safer...'. Right Now.
I got bitten but I half blame myself. I unchecked a couple entries Spybot had marked for deletion which were obviously programs I had recently installed. I hesitated about 'userinit.exe' but, trusting the program and being a little tired and bleary eyed, I pushed the button.
Damn damn damn damn damn damn damn damn damn damn damn damn damn.
I'm programming a new PC from scratch (it's taken weeks) and fortunately I've been creating backup images of the drive with Acronis.9 at regular intervals. I was nearly finished and put it online last night to update Nod32, Adaware & Spybot and then ran them all in that order. Then I spent hours trying to fix it after using Spybot. I gave up and deployed my last image losing another few hours of recent programming. But because of that I'm one of the lucky ones. I won't have time to get back to my project till Sunday and then only enough time to re-do the work I did last night. *%$#@#$$%
I was hoping to be tuning my firewall and taking it for a test run on the digital superhighways by then.
Spybot's name is mud at the moment. Who will be game to use it again?
Would you? Who've been screwed? You really, really messed up BIG time. *I* suspect someone with a vengeance/grievance :devil: at Safer Networking has added a malicious bit of code to the update files(?). What will it be next time? "format c:" ?
Bye Bye.
PS
you cannot even supply/check proper information for fixing this:
http://forums.spybot.info/blog.php?b=14
"The required default value and data:
Code:
for Windows XP
Userinit=c:\windows\system32\userinit.exe,
for Windows 2000
Userinit=c:\windowsnt\system32\userinit.exe, " <- win 2000 would be .......c:\WINNT\system32\userinit.exe,
Tut tut.
Please check the information you are providing to your users to end the suffering you have sent them.
olice:I've seen posts by your 'Team Members' (kid brother/sister?):cowboy: advising to try booting safe mode. Duh? These poor people are locked out. No doors and the 'Windows' are bolted from the inside. I'm guessing you 'Safer Networking' people use Linux when you're at home? So you would know grief as much as windows users. I see one or two forlorn victims crying 'Mac for me' after this fiasco. Another pretty desert island but with very little 'cargo'. Only good thing about Winblows is heaps of garbage washes up and occasionally you find something good. Spybot was a find
but now, as I said, it's got covered in mud :sad:.I suggest you remove all update files from your servers and replace them with a text file only containing a warning, an apology and promises that whatever bums are actually on seats at 'Safer Networking' are really working to make the program 'Safer...'. Right Now.
I got bitten but I half blame myself. I unchecked a couple entries Spybot had marked for deletion which were obviously programs I had recently installed. I hesitated about 'userinit.exe' but, trusting the program and being a little tired and bleary eyed, I pushed the button.
Damn damn damn damn damn damn damn damn damn damn damn damn damn.
Last edited by a moderator:
