Discussion in 'other anti-malware software' started by Mister X, Mar 17, 2017.
I just installed this, but not sure if it is working or not.
Did you click "Allow"?
Not sure what you mean, but I double clicked on the service in the folder and VS popped it's warning, and I allowed, but then I got a another warning message:
I am getting there. This time right-clicked on the service, and then Run as administrator, and this time WAR, popped it's warning, and I clicked on "allow next time". So, I will launch it again, and this time it should work.
Well, I launched the service again, and no more warnings/popups...But, the service is still not able to run, for some reason.
Did you right-click the install.bat in C:\ProcLoggerSvc and run that as Admin, as per the instructions?
Now, I am trying Process Hacker to create the service...Nothing works, for me.
OK, some people do seem to have issues running it on Win 10, although I haven't experienced this.
First thing I did was exit VS, turn off WAR and set Appguard to allow installs. Next I go to the service folder , 64 bit folder and copy the procloggersvc folder to my c: root drive. Then I navigate to that folder on my c: root , right click on install.bat as admin. Now you should see logging happening.
I never clicked on the proscessloggersvc.EXE
sorry for not being specific. I wasn't sure if you clicked allow at the VS prompt as it was in your screenshot.
Well, WAR has it as accepted/allowed, now.
I understand, now what you meant...I was a little slow, comprehending.
From your above process hacker screen shot you were trying to do something to the EXE. Leave that file alone. It does appear you have copied the folder correctly.
Just use the install.bat and you might have to do a reboot. Then checks the logs folder in that same folder not the one you copied it from.
I did use the install bat, but I didn't see any CMD window....I have checked the logs folder, and nothing is there.
I am shutting down shortly, and going to bed.
I couldn't sleep, so I decided to get stuck into the problem. I reran the batch file, and this time SAP put in an appearance. Just about all layers of my security, have been involved up to this point. ...anyway, I have got the process working, now, finally.
No problem. Glad to hear you finally have it working.
We've officially released the new version v1.3:
It was a relief to get it working.
Any change from the test version, or no need to reinstall the service?
I extraced both .zip-files (Release version 1.3 + test version 1.3) and compared both folders. The only change was in the file Changelog.txt
Separate names with a comma.