Jump to content


  • Content Count

  • Joined

  • Last visited

About Philon

  • Rank
    New Member
  1. Agreed, but I didn't quite do it as I mentioned above. However, it looks like I solve it! Yay! Here's what I did in brief: Narrowed down which of my three Chrome accounts was the problem by closing all chrome windows, and opening one account at a time and rescanning with Malwarebytes each time. This told me one specific account was the problem Followed these instructions for the problematic account only, which did involve "reset syncing" the account in question. But it wasn't a big deal since I didn't delete the stuff from my local chrome account. Re-established sync on the account after a reset sync and the pup.optional.conduit didn't reappear. So, it looks like the reset sync for the problem account was what was needed. Thanks for the input, Kevin! I think I'm all set.
  2. Hi, Kevin: I followed most but not all of your instructions, since I have three accounts I'm logged into chrome with, and doing a "reset sync" on them would require a lot of work on my end to reset things to the way I want. So, I did "reset sync" only for one of the three accounts (the one that was malfunctioning) and followed the rest of your instructions. Unfortunately, once I scanned with Malwarebytes, PUP.optional.conduit reappeared after Chrome was reinstalled (it was gone when I uninstalled). This tells me that it's probably one of the chrome extensions I use that is reinstalling it. Is there any decent way that won't take hours to figure out which of my extensions may be installing it? If not, then I think I may just live with it. Most of my extensions are useful, and I've already spend a few hours working on this, and the cost-benefit ratio is starting to make this not worth it. If there's no easy way to track it, I may just give up and whitelist it. Let me know if there's an easy way to examine which Chrome extension may be the cause of it. If not, I'll give up. I appreciate your input either way; thank you again.
  3. Malwarebytes scan is above. The FRST log is attached. Note: I restored my Chrome folder after I discovered these method you suggested deleted some important browser history yet didn't remove the PUP, so that may be reflected in the FRST scan. Also, I may have to reinstall Chrome now since one of my accounts is malfunctioning after the restore. Because of this, I may just live with the PUP since it may be related to one of my Chrome extensions that I use. But I'm willing to try a bit more if you're confident that this can be removed without negative consequences. I appreciate your help thus far. FRST.txt
  4. Hi, Logs are below. Unfortunately, I did a Malwarebytes scan after performing what you suggested and PUP.Optional.Conduit still appeared in the scan results. Here's the contents of fixlog.txt And here's mrt.log
  5. Hello, kevinf80: Thanks for your reply! I checked under "Scan Options" and "Scan for Rootkits" was off. I turned it on. I then performed a scan. Two PUPs were identified: PUP.Optional.Conduit and PUP.Optional.InstallCore. I quarantined them, which crashed my running version of Chrome. Malwarebytes then asked me to reboot. I did so and my computer froze, causing me to do a hard shutdown. Here's the report from the clipboard: ____________________________ Here's the adwcleaner log: ________ I've attached the two FRST files as well. FRST.txt Addition.txt
  6. Hi, New premium user. Upon first scan, Malwarebytes detected Pup.optional.conduit, which I quarantined. After a reboot and a new scan, the threat reappeared. I've searched these forums for a general solution and found several references, but it looks like each person was helped through step-by-step and had their cases resolved differently, so I figured I'd open a thread of my own. Any help would be appreciated. Thanks you.
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.