tomcat wrote: ↑01 Sep 2017 10:35
dmex wrote: ↑15 Aug 2017 06:39
I don't have issues with the FirewallMonitor plugin on Windows 10
Not even me, no problem
Well, it would help if you guys listed the actual version you are using since for me, I am basically running the binaries of the latest nightly build of process hacker as found here:
So after extracting that to the processhacker-3.0.1102-bin on my desktop, Process Hacker works when running processhacker-3.0.1102-bin\x64\ProcessHacker.exe so I exit ProcessHacker.
What I do is I download the file Process_Hacker-bin.7z from post #27 of this thread at:
I extract the Process_Hacker-bin.7z and take the processhacker-3.0-bin.zip from that file.
I extract the processhacker-3.0-bin.zip to the desktop as processhacker-3.0-bin and then take the following files.
Copied the following from processhacker-3.0-bin\x64\plugins and copied to the processhacker-3.0.1102-bin\x64\plugins folder in the nightly build:
Copied the following from processhacker-3.0-bin\x64\plugins\plugindata and copied to the processhacker-3.0.1102-bin\x64\plugins\plugindata folder in the nightly build:
At this point, I run processhacker-3.0.1102-bin\x64\ProcessHacker.exe by right click as Admin and it runs for exactly 1 second and exits.
As soon as I rename the file processhacker-3.0-bin\x64\plugins\FirewallMonitorPlugin.dll to processhacker-3.0-bin\x64\plugins\FirewallMonitorPlugin.dll.bak and run processhacker-3.0.1102-bin\x64\ProcessHacker.exe by right click as Admin, ProcessHacker will work fine. If I have the processhacker-3.0-bin\x64\plugins\FirewallMonitorPlugin.dll there, ProcessHacker will exit as soon as it runs.
It is actually Process_Hacker-bin\plugins_install.txt after extracting that says the following:
./plugins/FirewallMonitorPlugin.dll - only for Windows 7 - 8.1
The same problem happened with earlier nightly builds of Process Hacker since August 2017 when I tried to use the FirewallMinitorPlugin.dll as well, I am just using the latest nightly build version as a example to illustrate the problem. The problem still happens in Windows 10 Home x64 with Fall Creators Edition. So what am I doing wrong?