rocksuitcase

I booted into SAFE mode Thursday, ran MBAM, it didn't find PUM.Bad.Proxy, but found 4 other critters. I then attempted to install FRST- no good. This machine may be in need of an install repair or possibly a clean install. for now, unless you have any other ideas, we can close this and I can open up a new thread if/when necessary?!? THANKS Mr. C for all you do for us.

Mr. Charlie, first-thanks! Second, don't close this out; it may take me 3-4 business days to get that thing booted in SAFE mode.When I do that, it will be at night EDT, usually between 8PM and Midnight. I will try to get t it tonight, but if not, please don't close out until you hear from me?!

I just DL'd them both and attempted to run "normally", then as administrator (even though I am logged in as the domain administrator) they will not run on this machine. (Windows 7, 64 bit, Dell Precision Workstation, 16 GB RAM, i& processor). the only problem it has been reporting is this PUM.Bad.Proxy. it occurs once per day during the scheduled daily scan; I have MBAM set to automatically quarantine both PUP's and PUM's. the main problem with fixing this computer is that it is a "production" machine which stores data for several CAD drafters and thay use it aboyut 14 hours per day including Saturdays. About two weeks ago, on a Sunday, after manually removing the registry entries which Bad Proxy reports, I then rebooted and ran MBAM, and it came back with zero infections. I then went into sysetem restore and deleted all restore points, and created a new one. The next night MBAM found and quarantined the PUM.Bad.Proxy again, and it has come back every night since. I can't easily wipe this thing clean and re-image as it is a "production PC". Is there any way to get help without runnning FARBAR? ( I haven't tried running FARBAR in SAFE mode- should I?)

I will do so today and see what happens. this bad proxy is a PITA for sure.

This PUM.Bad.Proxy has been detected and quarantined on a daily basis for well over one month. FRST64.exe would not download on IE 11 in an administrator account (Windows7 64 bit) so I put it on a flash drive and copied it onto the desktop of this machine. It claims it is the incorrect version when it is not. 2014-10-17mbamlog.txt I do have an MBAM log, but obviously can't get a Farbar log. We have 50 Premium licenses and this is the first time I have used the forums or any MBAM support, so please bear with me or provide me with the optimal way to do this. I am the IT person for this company and am able to deal with most repair functions adequately. Thank You, Kyle

All three of the PCs which experienced this issue have ATI onboard video; Dell Optiplex series.

I just created an account due to this error. I have been an active MBAM user both at home and work for almost 5 years. Currently I am sys admin for 2 small companies with about 40 users. MOst of our PCs are XP SP3, however, we do have some Windows7 64 bit machines (8 PCs). earlier in thuis week, I ran into this issue and was able to use the mbam-clean.exe and re install 1.6.0.0.1800 and all worked. TODAY, I have started my monthly maintenances during which I usually update mbam and run a quick scan. on the first three PCs (all XP SP3), this issue occurred. We do not use ZA or Avast- all of these machines use Symantec Endpoint Protection 12.5 and all are up to date as of today. I tried disabling SEP on one machine BEFORE updating MBAM-still got the error after the updates. So far, I am doing what has been suggested, [run mbam-clean.exe, OK out of all the errors, reboot, disable SEP, re install MBAM 1.60.0.1800]. BUT I will tell you that I refuse to update another PCs Mbam until this gets resolved. I do have 3 users using MBAM PRO, I may try to see if there are any differences with those as they automatically update every day. NOw, I realize this is "freeware" for most of us users, however, MBAM has had these updating issues about 3 times since I started using it. BAd enough to have to fight legit bad guys, but to have to worry that machines are infected when they are not is Waaaay BAD (as the kids say)!