Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About ColdlyIndifferent

  • Rank
    New Member

Recent Profile Visitors

547 profile views
  1. I've already posted about this matter on the ISP's forum - their preferred way of initial contact and as I've found out the quickest way of getting a response. Not heard back from them yet and probably will not for several days. My suspicion is your third suggestion - it would be 'in character' for my ISP. I really doubt a system issue my end. The fact that it has affected two PCs which, whilst they share the same router, are not networked and have never even been on at the same time specifically to reduce the likelihood of cross contamination. I've done full system AV, Rootkit, MW,
  2. Just changed the DNS (to Google) and.....................................it worked. But what does this mean? I'm using my ISPs default DNS and have been for a decade without any problems until now. Why would it be blocking one particular thing and Malwarebytes definition updates in particular? I've done a whole load of updating as I do at the end of every week without a similar problem for any of them. Anyway big thanks to those here for their help and exile360 in particular. I would never have thought to check if this was a DNS issue myself.
  3. No, no VPN or Proxy. I've not tried changing the DNS yet but what I have managed to do is copy in the most the last definitions update from the other PC so at least I have a working MB installation. When I tried just copying over the rules.ref file it didn't work, I had the missing/corruption message but I thought I'd try simply replacing all the MB's folder content ie. Program Files (x86), Program Data and User AppData. Everything but the Windows Explorer DLL (in use) copied fine. I thought that was unlikely to be problem and it wasn't. On reboot MB was showing the replacement
  4. I tried the full Windows 7 resetting the DNS cache thing:- Windows 7 Click Start > All Programs > Accessories. Right-click Command Prompt and choose Run as administrator. When asked whether to allow Command Prompt to make changes to your computer, select Yes. Note: If you are asked for an administrative login, you will need to contact your system administrator. Type "ipconfig /flushdns" and press Enter. Type "ipconfig /registerdns" and press Enter. Type "ipconfig /release" and press Enter. Type "ipconfig /renew" and press Enter.
  5. I do not rely on Malwarebytes and treat it like an adjunct to my security software, scanning downloads and doing weekly scans just to check that nothing untoward has sneaked onto my system. When I tried updating to a more recent version on the PCs in question I found that just scanning manually an individual download took three times as long rendering it pretty much redundant for quick check purposes. I think I posted here about that at the time. The fact is I've had no trouble downloading the definitions updates until this week, I'm guessing 9th August or around that date. Whatever the p
  6. I know it is an old version but for my purposes on a XP virtual machine and a Win7 system with limited speed/memory Malwarebytes v1.75.0.1300 is ideal. The definitions have updated without issue until now. As a result of a mistake I had to use System Restore yesterday. As in normal when done everything works OK but the Malwarebytes definitions database always reports it is either missing or corrupt so I click to download and install the latest version. That normally goes without a hitch but this time is seemed to hang momentarily, not connecting to the server and not downloading anything
  7. No new news to report except that Microsoft are refusing to budge on their sudden decision to treat PH2 as high threat malware. This link to a Process Hacker forum admin post links to relevant threads which may help others coming here in regard to this matter:- https://wj32.org/processhacker/forums/viewtopic.php?f=1&p=11304#p11304 and the other thread there:- https://wj32.org/processhacker/forums/viewtopic.php?f=40&t=3729&p=11282#p11282 In short MS, and only MS, now regard PH2 as a malware tool and their anti-virus/anti-malware programs will, depending on y
  8. Found this telling PC blog post. PH2 has been tested and absolved but MS hate it anyway seems to be real story.
  9. As a follow up I've posted about this in the appropriate MS Community forum and Process Hacker 2's forum. In the latter this MSE/Defender definitions issue (as that is what it appears to be) is also being reported. Although it is not really a Malwarebytes' matter, as that, like all other security tools it reports there being no problem it would be helpful if this thread is kept open so if there is some resolution/explanation from MS about this it can be posted. Other users coming here may find it useful information and not have to bother Malwarebytes any further with it.
  10. The uninstall you did probably left stuff behind and did you check Defender's Quarantine folder because it might still contain those quarantined items? It will delete them after a certain period of time, 30 days I think, but if you've decided to get rid of PH2 then it would be a good idea to use the Remove option if anything PH2 related is there. I do not know whether Defender is the same but MSE makes adding exclusions, once detected, as difficult as possible. Once there they also seem to persist in Quarantine even if you use the Allow option. The Allow option is only available under the
  11. Yes I am saying that the reason we've both had this on two different MS security platforms is that definitions have probably both been updated because somebody, somewhere has either made a mistake, added it after someone reported it as a problem without checking or some process PH2 uses has been wrongly detected as a "threat". There is a warning with the PH2 installer that one of the options is not recommended and it has been known for that it can be used as a potential conduit for malware. Whether it has or not that would be enough for it to designated as a threat. This is a quote from a
  12. I think we might well have another false positive issue here. I have Microsoft Security Essentials (MSE) as a temporary AV on another PC and that too suddenly started reporting (the same weekend) that the Process Hacker 2.exe was a "high" threat after its most recent definitions update. Unfortunately for me I'd not changed MSE's default settings and in the case of a "high" threat it deals with what it sees as the offending file automatically. I expect that is what has happened here for the OP with Defender which is probably using the same MS definitions. I only realised it had bee
Back to top
  • 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.