How to resolve “themed32.dll not found” problem
If you got “themed32.dll not found” message during Windows startup – you was infected by “Themed32″ trojan.

Your computer could not boot because after clicking OK you will get the same error from Wininit.exe and your computer will hang.
What’s happened?
Recently your antivirus detected and remove %SysDir%\themed32.dll.
VirusTotal Report: themed32.dll
| Antivirus | Version | Last Update | Result |
|---|---|---|---|
| a-squared | 5.0.0.30 | 2010.06.24 | Packed.Win32.Katusha!IK |
| AhnLab-V3 | 2010.06.24.01 | 2010.06.24 | Packed/Win32.Katusha |
| AntiVir | 8.2.4.2 | 2010.06.24 | TR/PCK.Katusha.O.24 |
| Antiy-AVL | 2.0.3.7 | 2010.06.24 | Packed/Win32.Katusha |
The problem is that your antivirus does not good the cleaning.
Themed32 virus infects system DLL “%SysDir%\uxtheme.dll“.
It changes the import table of the uxtheme.dll for auto loading the Themed32.DLL.
The Themed32 virus uses this method for auto starting with Windows system.
The simple way for resolving the problem: use boot CD.
The good choice is “RegRun Warrior“.
You will find the “%SysDir%\uxtheme.dll~RF5bac.TMP” (or with similar name) backed up by virus .
Rename “uxtheme.dll~RF5bac.TMP” to the “uxtheme.dll”.
The Warrior boot CD includes the best file manager (Far Manager) that automatically displays hidden files.
Restart your computer and continue your good day!
Result: 17/40 (42.50%)
Antivirus
Version
Last Update
Result
a-squared
5.0.0.30
2010.06.24
Packed.Win32.Katusha!IK
AhnLab-V3
2010.06.24.01
2010.06.24
Packed/Win32.Katusha
AntiVir
8.2.4.2
2010.06.24
TR/PCK.Katusha.O.24
Antiy-AVL
2.0.3.7
2010.06.24
Packed/Win32.Katusha
Recommended: UnHackMe anti-rootkit and anti-malware
Premium software: RegRun Security Suite (Good choice for removal and protection)
Comments
One Comment on How to resolve “themed32.dll not found” problem
-
Gareth on
Sat, 3rd Jul 2010 10:45 pm
Thank you you genius!!! Absolutely fantastic and sorted out my problem quick smart (after 2 days fiddling around and getting hold of another copy of Vista to try and resolve things… – which it didn't… Resorted to booting up to the vista reinstall, going to repair and via the command prompt renaming the files as shown above… Thanks!)
Tell me what you're thinking...
and oh, if you want a pic to show with your comment, go get a gravatar!
You must be logged in to post a comment.






