on my task manager at dllhos.exe*32 it says COMSurrogate
Something I haven’t noticed before but I did intenstall some remote printers last week.
If so, d/l MBAM to a usb stick from that machine and try installing it on your hosed box.
I did a cursory search for 'dllhos.exe*32 COM Surrogate' and saw lots of references to it as a bug in the search results.
If it were my box, I'd try the system restore route first, using a restore point prior to when you installed that 'remote printer software' last week.
That would get you back to a point that you could again d/l stuff, and one of the first things I'd do afterward is grap MBAM, install it, and let it run a full scan.
Be sure to save any open docs first (.doc,xls, txt, etc), and they'll be untouched by the restore process.
Again > /.02
Lot’s of confusing, conflicting info popping up here. To summarize what I think you’re saying:
1. Your FR cookie is not persisting;
2. Your banking cookies are not persisting;
3. Something is blocking you from doing a D/L of Malwarebytes Anti-Malware 2.0.4 (MBAM).
These are all symptoms of a compromised system. If you have access to another PC, go to it an download MBAM to it, as well as McAfee’s free “Stinger” program - a self-contained anti-virus & anti-malware program that doesn’t require local installation. Copy these to a USB thumb-drive, and give them both different names when doing so (some viruses and malware look for and prevent you from running common anti-virus and anti-malware programs). Call them something like AV_PGM1 and AV_PGM2. Plug the thumb-drive into the corrupted PC, and run the Stinger program first. That will find most, but not all issues and correct what it can. Once that’s done, run the MBAM install; update the definitions, then do a full-scan.
Let us know what you find. Once you’re cleaned up a bit, THEN we can have you download and install CCleaner - a good, general maintenance and garbage clean-up program.