othersteve
Member
- Reaction score
- 14
Hey guys,
Taken from my blog here:
So following the disinfection of certain rootkits (such as Rootkit.Boot.SST.a, which is associated with the Windows Recovery rogue), you may find that your Windows boot configuration data has been totally corrupted. Worse yet, the usual steps to remedy (such as those described in my earlier post about TDL4 and the resulting blue screen) all fall apart when you reach the bootrec /RebuildBCD command, which returns the message:
I actually managed to solve this problem earlier today, and I'm quite sure that no one else has yet posted the solution anyplace on the internet. If you're running into this problem, check out my most recent blog post for the full scoop on how to correct it:
http://triplescomputers.com/blog/?p=81
This is becoming more common thanks to some of the more recent rootkits. I hope this helps someone!
Taken from my blog here:
So following the disinfection of certain rootkits (such as Rootkit.Boot.SST.a, which is associated with the Windows Recovery rogue), you may find that your Windows boot configuration data has been totally corrupted. Worse yet, the usual steps to remedy (such as those described in my earlier post about TDL4 and the resulting blue screen) all fall apart when you reach the bootrec /RebuildBCD command, which returns the message:
I actually managed to solve this problem earlier today, and I'm quite sure that no one else has yet posted the solution anyplace on the internet. If you're running into this problem, check out my most recent blog post for the full scoop on how to correct it:
http://triplescomputers.com/blog/?p=81
This is becoming more common thanks to some of the more recent rootkits. I hope this helps someone!
