Just my opinion

[justauser]

To whom it may concern,

 

Today once again I had to deal with the stupid conduit hijacker, It really does seem to come out of nowhere, I read an article that your software would detect and remove it, you offer a free trial which I have downloaded. It certainly detects many instances of the conduit entries but as soon as you hit remove the program crashes and will not respond, I have searched high and low for a fix for this and have only become more aggravated. 

 

Can anyone respond to this and explain why the program continually crashes?

[AdvancedSetup]

I'm sorry that you're having issues with the program.  More than likely you have multiple issues going on with the computer and it may require further assistance in detecting what's going on and cleaning up the computer and then doing some maintenance to help prevent a future infection.

 

I would suggest following the advice from the topic here Available Assistance for Possibly Infected Computers and having one of the Experts assist you with looking into your issue.

Thank you

[justauser]

Maybe I shouldn't do this but here is the log file that Malwarebytes came up with. As you will see it's not a long file and as I would certainly understand there may be more issues. This seems like a small number of findings. I appreciate the response and will check out the link you provided and work from there, I understand its difficult without having knowledge of my system environment, I hope you had a Merry Christmas and will have a great New Year, Thanks again for the help.

 

Windows Vista Service Pack 2 x64 NTFS

Internet Explorer 8.0.6001.19489

:: OFFICEPC [administrator]

 

Protection: Enabled

 

12/26/2013 9:38:35 AM

MBAM-log-2013-12-26 (09-47-00).txt

 

Scan type: Quick scan

Scan options enabled: Memory | Startup | Registry | File System | Heuristics/Extra | Heuristics/Shuriken | PUP | PUM

Scan options disabled: P2P

Objects scanned: 297434

Time elapsed: 4 minute(s), 56 second(s)

 

Memory Processes Detected: 0

(No malicious items detected)

 

Memory Modules Detected: 0

(No malicious items detected)

 

Registry Keys Detected: 0

(No malicious items detected)

 

Registry Values Detected: 0

(No malicious items detected)

 

Registry Data Items Detected: 0

(No malicious items detected)

 

Folders Detected: 5

C:\Users\nameremoved\AppData\Local\Temp\ct3306061 (PUP.Optional.Conduit.A) -> No action taken.

C:\ProgramData\Conduit\IE (PUP.Optional.Conduit.A) -> No action taken.

C:\ProgramData\Conduit\IE\CT3306061 (PUP.Optional.Conduit.A) -> No action taken.

C:\Program Files (x86)\Connect_DLC_5 (PUP.Optional.Conduit.A) -> No action taken.

C:\Users\nameremoved\AppData\Local\VisualBeeExe (PUP.Optional.Visualbee) -> No action taken.

 

Files Detected: 0

(No malicious items detected)

 

(end)

 

What interesting about this is that if I perform a "regedit" search I can find conduit key's....

[AdvancedSetup]

Well the log you posted shows that you did not tell MBAM to remove it.  You need to tell it to remove what it found.

 

That said Conduit is often ever changing and may require an Expert to help you fully remove all traces of it.

 

Thank you again and Happy Holidays to you as well.

 

Cheers

[justauser]

so... as my original post stated, when I asked MBAM to remove it, that is when the program became unresponsive and had to be killed with task manager, three times I let it sit after selecting remove for more than 15 minutes. so i did tell it to remove it, that was the context of my original post, after asking for its removal, the program would crash and not remove it. it would find it, no problem, but it would become unresponsive when asked to remove it. I even went to the extent of uninstalling MBAM , restarting my computer, re-downloading the program, and, re-installing it with the same results.I have since found another way to remove it,

 

Thanks for the responses, have a happy new year...

[AdvancedSetup]

Please follow the advice in post #2 above and someone will assist you in cleaning your computer and getting things working correctly again.

 

Thanks