Manual Removal Guide for VirusBurst

The following instructions have been created to help you to get rid of "VirusBurst" manually.
Use this guide at your own risk; software should usually be better suited to remove malware, since it is able to look deeper.

If this guide was helpful to you, please consider donating towards this site.

Threat Details:

Categories:

• pups

Description:

VirusBurst claims to be a antispyware solution and gets advertised by dubious popups. If it is installed on the computer, it finds some entrys as malware which are totally harmless. When the user tries to fix these problems he has to buy a licence and so the programs tries to frighten users by showing false positives.

Removal Instructions:

Autorun:

Please use Spybot-S&D, RunAlyzer or msconfig.exe to remove the following autorun entries.

• Entries named "VirusBurster" and pointing to "*".

Important: There are more autorun entries that cannot be safely described in simple words. Please use Spybot-S&D to remove them.

Installed Software List:

You can try to uninstall products with the names listed below; for items identified by other properties or to avoid malware getting active again on uninstallation, use Spybot-S&D or RunAlyzer to locate and get rid of these entries.

• Products that have a key or property named "Virus-Burst".
• Products that have a key or property named "VirusBurster".
• Products that have a key or property named "VirusBursters".
• Products that have a key or property named "VirusBurst".

Files:

Please use Windows Explorer or another file manager of your choice to locate and delete these files.

• The file at "<$PROGRAMFILES>\<$REGMATCH0>\blacklist.txt".
• The file at "<$PROGRAMFILES>\<$REGMATCH0>\uninst.exe".
• The file at "<$PROGRAMFILES>\<$REGMATCH0>\vir.dat".
• The file at "<$PROGRAMFILES>\<$REGMATCH0>\Lang\English.ini".
• The file at "<$PROGRAMFILES>\<$REGMATCH0>\vb.ini".

Make sure you set your file manager to display hidden and system files. If VirusBurst uses rootkit technologies, use our RootAlyzer or our Total Commander anti-rootkit plugins.
You will have to use a global search for files without a name specified. Be extra careful, because just the name might not be enough to identify files!

Important: There are more files that cannot be safely described in simple words. Please use Spybot-S&D to remove them.

Folders:

Please use Windows Explorer or another file manager of your choice to locate and delete these folders.

• The directory at "<$PROGRAMS>\<$REGMATCH0>".
• The directory at "<$PROGRAMFILES>\<$REGMATCH0>".

Make sure you set your file manager to display hidden and system files. If VirusBurst uses rootkit technologies, use our RootAlyzer or our Total Commander anti-rootkit plugins.
You will have to use a global search for files without a name specified. Be extra careful, because just the name might not be enough to identify folders!

Important: There are more files that cannot be safely described in simple words. Please use Spybot-S&D to remove them.

Registry:

You can use regedit.exe (included in Windows) to locate and delete these registry entries.

• Delete the registry key "{05DDEB15-33E0-4DE3-B7CD-84E2E011D889}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{0B386DB3-239C-41D6-85CB-CA728F31F3FC}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{2E94C834-9EFA-4C46-B032-A185C69EBC53}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{34D2738B-701F-454A-9198-25924CF75E92}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{3863C215-13E6-4E29-9921-78CE0A6F272A}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{420EE180-CE72-40AC-83CB-B55DCB68CCF1}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{638C512D-C04A-4E06-A9A3-8127C4E5B4E7}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{63CA0A34-071D-4780-A5BD-28F0CFC3E512}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{73467269-7B9F-4F66-B381-D914A7ACECEB}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{7DF33004-9121-4FD5-93B6-6376060D2D3A}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{A7308DE2-D644-488D-80D5-071710F5B840}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{ABA193DF-6C52-4D02-975A-94A85B32DC3C}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{AFB40450-78FE-4F01-BE69-A76A8C396304}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{C793C7C5-E89F-48EC-83C9-06AC097E8CB9}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{CAD91BD2-75E7-4E5F-A939-4ECC2D512918}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{E120C137-922C-434C-8A02-2A8D27B3E2D2}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{728E63B0-5165-4E98-9C83-EF987EEB66C9}" at "HKEY_CLASSES_ROOT\TypeLib\".
• Delete the registry key "{CCFB2B33-F4DB-B63D-ABDC-C7384ED93B34}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{016859C2-97B6-45FC-816B-A3B91BA10A0F}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{03713ADE-819C-43D9-B138-67828D4C0405}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{0BDF8F38-347C-4810-BDA6-2F85C1050B26}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{18A1A6BB-8AE3-47E3-B9D4-75ABFE0CAC03}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{2D1254A1-4A1A-4339-9DE5-D05CADD5C44C}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{2F34C08C-E0AF-4EB2-AFCF-3A13DC489FA6}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{49D486E8-1932-492D-B1BD-B4D638BEBD84}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{49E2EB9D-A5E6-450E-9708-251876BF3E7F}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{68C625EA-B8E3-4FC1-9F6E-8A1B50AA9C8C}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{6F821290-E277-4F87-B4BD-AE48564EF21D}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{9BA6B541-EB04-44C9-9156-9573DB5345A5}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{A8718256-70C8-4914-8F64-B8B9C1A64AAA}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{C3A42538-303B-4541-915D-C79AD9C75EB8}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{C48AE974-0D27-47D6-A3E9-881CF3301F72}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{DA02B168-8841-4248-BF22-67E2EC5958C3}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{E505FB9B-6CB3-44C5-9F0E-B01121076CC9}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{00B3D2B1-1EAD-4611-A348-9ECBC4C565A7}" at "HKEY_CLASSES_ROOT\TypeLib\".
• Delete the registry key "{D6ECDA42-AD6F-F8C3-03EA-5834841ADEC3}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry key "{0065CDBC-2439-4365-A7E7-BF5B853BF49D}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{19DACF08-A207-4271-AA22-C138F512E787}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{3E37C978-9E24-42FA-B021-B56CAAFDB694}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{4130008C-5697-4EF5-9EDE-EF8F9F10D524}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{4F4A0564-17DE-4EB2-B29E-6D2E167A3BE0}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{6B067ED9-4AEC-474E-B67E-85EF417D68BA}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{9188A88D-3D41-4EB6-A7D8-0F6A5266F685}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{B660CDE9-526E-41FE-AB41-773D78BEE31E}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{BF8A0E53-F417-413A-B849-B5C0086EEF8A}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{C36464A1-2D2F-4804-AAF6-F5BD62536ADB}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{CA74BAFC-1F0C-49B1-8A76-5D55085E71FB}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{D0722752-35B5-44E1-A14A-E2A44C41F509}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{D648067C-E5D2-4BB8-AD86-A993B8793A52}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{EE2EAC90-8B01-49D4-B46C-8E02BDA1F3B4}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{F7F932D6-A6BE-4273-9950-ECBD72170DBF}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{FD34EB96-89FA-43CC-9C37-D1D5B099D28F}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{A569F6C9-29F0-43BC-80CF-6BA138C66108}" at "HKEY_CLASSES_ROOT\TypeLib\".
• Delete the registry key "{02313722-BB43-4C84-80A2-7CEDFC3F8560}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{0A03153E-AE2A-47FE-BBA3-3333C0EEEB86}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{13854DA2-8414-4007-9693-2B6E6002520E}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{1DF2A595-BB53-46D4-9EED-1343E066C2B0}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{21EFA4BF-6BAC-43E9-9465-9DDB4AC2967E}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{2CB87422-057A-4FFC-A518-6A728D6F5F65}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{52B75F3F-0016-4002-9A3A-B68BC9501ED1}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{6DDA751B-CA62-41C6-B622-EA4B4C2E51F8}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{88BDD61D-AC47-4D9E-A3ED-1CAA575593E6}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{A09DFAEF-BFA3-47CA-9479-D7EC79342146}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{B70B489C-F0D5-4DD9-A2BA-9B6DBCF5090A}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{B889DE48-EC10-4278-B3FF-76FEB7449215}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{C9CA446E-0484-4647-BBF0-3C129C42047C}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{D7DE2292-04DD-48FC-B250-5E9BFE6BB959}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{F9B659A0-6F32-4D69-A7D0-29A0B8CDDC16}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{FA13560C-D18C-4BE6-AE80-EBEFC6E5AD3C}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{ACF3DAB0-D308-4B7A-BFE3-E6C0FAFEB1E7}" at "HKEY_CLASSES_ROOT\TypeLib\".
• Delete the registry key "{0249BEB1-A2AA-45A3-9EC5-95D9C4A40A62}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{082DA6AF-F994-4C6C-A2B0-DFC3B3FF540A}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{0C9A71B1-8A8A-48A1-AA3F-0C83CE1C0BBD}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{0EF25077-DA22-4FF2-B6FF-6FC1C26F5740}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{20DC1F8E-4640-4FFF-9858-05E7B978CC71}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{2613CF74-4FC5-4251-9F48-260496364852}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{27D8CD06-82E3-4E1E-8917-86A9B3AE41F6}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{7CAEFBCD-55A9-4A68-AA02-E69B12B3BE57}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{898272CF-3ACE-4A7B-98FA-9EB8DB8B26DC}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{8CBF5BAC-E609-4863-ABC9-68A7BD13B1D0}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{9981DDEF-81C4-4CC8-A5F2-62A7912D8037}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{9CB68DF7-F336-45A2-BDE2-5DCA3998986F}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{B4BB620F-3AE7-4910-8171-F9FC8120D9EF}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{D838D7A3-1551-4B32-BF7A-7F4F769BB885}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{E1751F23-00E6-4F6C-AD78-CA7D8A96FD3E}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{ED639B1F-1B3F-473F-BD8D-6DE9C2D1972A}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{F83E8F99-AE49-45D6-92B4-59854BF0A759}" at "HKEY_CLASSES_ROOT\TypeLib\".
• Delete the registry key "{40dcff6e-af8d-4183-8ebe-a82270ac449e}" at "HKEY_CLASSES_ROOT\CLSID\".
• Delete the registry value "{40dcff6e-af8d-4183-8ebe-a82270ac449e}" at "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Explorer\SharedTaskScheduler\".
• Delete the registry value "{40dcff6e-af8d-4183-8ebe-a82270ac449e}" at "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\SharedTaskScheduler\".
• Delete the registry value "{40dcff6e-af8d-4183-8ebe-a82270ac449e}" at "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ShellServiceObjectDelayLoad\".
• Delete the registry value "{40dcff6e-af8d-4183-8ebe-a82270ac449e}" at "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\ShellServiceObjectDelayLoad\".
• Delete the registry key "{0354A901-C606-4DCC-8EA3-4F3383ECE67C}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{11ED5DDF-90D0-45C1-BE2B-C9C4F98CCFE2}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{1FEB28BA-21B6-46F3-948A-D7CA11654FE9}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{340B5D33-4A0C-4673-94FA-B88ECC48773E}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{453B991D-6B23-48CF-A3B0-2214F437CCB0}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{5AC65D7D-C00C-47A4-83F7-F81073C39B25}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{657D5DE0-6497-4040-B604-F38C9411F64D}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{8A7D5862-7B00-4270-B456-CDC6779A79DD}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{940664C7-DE44-4B8F-A05D-FD70CAB75F2C}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{B7512CD1-CFDE-4498-ADBD-14B38062A478}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{CABABC4B-5B0F-4297-9D85-72E93616ED55}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{CCA1E17E-2BEE-4D53-8D00-7ADB5B35145A}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{CF1D16BA-2CE6-429A-A63A-3CF44D81A950}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{E56B4B91-E548-4E89-97AC-E9630D22A2E2}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{FC105E0D-AE24-43F2-89AA-E8AB8F96EF6E}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{FD99520A-E900-4F8D-9092-22705622D2D2}" at "HKEY_CLASSES_ROOT\Interface\".
• Delete the registry key "{03F89BF1-127B-44F3-B6F4-5A18FEA674CD}" at "HKEY_CLASSES_ROOT\TypeLib\".

If VirusBurst uses rootkit technologies, use our RegAlyzer, RootAlyzer or our Total Commander anti-rootkit plugins.

There are more registry entries that cannot be safely described in simple words. Please use Spybot-S&D to remove them.

Final Words:

If neither Spybot-S&D nor self help did resolve the issue or you would prefer one on one help,

1. Please read these instructions before requesting assistance,
2. Then start your own thread in the Malware Removal Forum where a volunteer analyst will advise you as soon as available.

There are more files or system entries belonging to this product that <$SPYBOTSD> can remove, but that cannot be easily described in text. Please use <$SPYBOTSD> to make sure <$PRODUCTNAME> gets completely removed.