Uninstalling Conduit SearchProtect deletes NTLDR making Windows XP Unbootable

Something a bit serious for XP users is the removal of Conduit SearchProtect.

If it is removed via add/remove programs it makes the machine unbootable.

Info can be found here including a safe way to uninstall this.

http://www.bleepingcomputer.com/forums/t/522327/uninstalling-conduit-searchprotect-deletes-ntldr-making-windows-xp-unbootable/

Well that's one way to ensure users don't remove your product.

Hiren's Boot Disk repairs NTLDR Missing.

One would think by now that antivirus vendors would automatically block the installation of that rubbish. And if it's damaging systems I smell a lawsuit that will hopefully make them non-existent.

Hiren's Boot Disk repairs NTLDR Missing.

Trouble is not many people know about Hirens boot disc or even how to use it. It's a must in any ones toolbox really.

The problem with Conduit SearchProtect at the moment is the badly coded uninstall routine. As to the programs legality, if people agree to its install it cannot be counted as malicious.

yeah, conduit is pretty dubious. Glad to see adwcleaner gets an honorable mention there though.

By the way...

As Windows Vista and newer versions do not contain any files in the C:\ folder that are required to start Windows, Windows is able to start normally.

.

This part of the article is WRONG. Win7 has got bootmgr and grldr both at the root folder. And I think Vista has got the same.

windows 8 has bootmgr and bootnxt there as well

Are they not in the system reserved partition?

my system reserved partitions are on vacation for some reason on my raid array, I really need to look into getting those onto my system drive.

I don't have a "system reserved partition". I prefer to have the system on an unique primary active partition.

are we getting confused with a system, primary, boot partition (which every PC has, and where bootmgr and bootnxt are found, except XP) and a system reserved partition (which is not created if Windows was self installed, and usually only created when using a factory restore feature)

let's see how right I am... :)

"system reserved partition" is a pain that you need to endure if you want Bitlocker to lock you out of your computer.

"system reserved partition" is a pain - your BIOS boots into this, and this SHOULD redirect control to Windows installation in another partition,

NOT ALWAYS THE CORRECT PARTITION.

I have an original multi-headed Windows on a HDD,

and subsequently an additional hydra-headed Windows on an SSD which became my default system drive.

One day I powered up and Windows was not quite how I remembered it -

I found the "system reserved partition" had transferred control to the wrong drive :o:angry: :angry:

I think a full Windows 7 installation will by default create "system reserved partition" if it is a version (e.g. Ultimate) that includes BitLocker capability,

and you have to override installation defaults to avoid the aggravation of an unwanted "system reserved partition".

I fully intend to undo the aggravation on my system,

but not yet - I am deterred by the thought that I will REALLY learn how to do this by the PAIN of my own mistakes :(

We should keep on topic and forget about the partitions thingy...

Thanks for the heads up, Hazelnut.

eL_P, looks like Bleeping is using the same removal tools you recommended earlier on this forum, if I remember that right?

:)

Yes, they are...