I was keen to try it until some red flags popped up.... In the screenshots on their web site, the product window is titled "Fort knox 2009"......
Blocking and logging ok here too... Date/Time: 29/03/2017 15:06:05 Operation: Write Value Process: [27676]C:\Windows\regedit.exe Parent:...
On 3.56 and 3.57 here with no issues on either machine. That said I've not had any issues with 3.53, or any of the subsequent betas.
This is what was in 3.56...so I assume 3.57 has this too...
I experience the same problem if I refresh the logs regularly. Appears to happen randomly though.
The commonality is we both have Office 365 - it's probably why the command line is additional to what you've seen, unless that is, you have it aswell.
The reference to generaltel.dll would suggest to me it's something to do with sending telemetry data to Microsoft. I've seen the same on my PC and...
No problem. Glad to hear you finally have it working.
sorry for not being specific. I wasn't sure if you clicked allow at the VS prompt as it was in your screenshot.
Did you click "Allow"?
Why is it too late? You may be compromised, but do you really want to allow the malware to have free reign to do whatever it likes to your system,...
I'm interested to know what you think should happen instead of a lock down when VS is killed by malware or some other method? Nothing?
Sorry :( you are correct the source and destination ports in the inbound log are the wrong way around. Good spot.
Apologies you are correct. I didn't realise you were creating an incoming RDP connection to your local machine. There is a mistake but it's not...
@VoodooShield Hi Dan I'm all for implementation of a 'tamper mode' feature that locks the system down when VS is targeted, but I do believe it...
The source and destination addresses are not the wrong way around. The problem appears to be, you are creating your RDP rule from the "inbound"...
Paul, I believe we were both right: MR7 does feel rushed, just not in the same league as MB3
Why did closing VS lock up your machine? A normal exit should just close the application, only terminating the VS processes through a backdoor...
On my system, V7 is running just as well as v6 was; there is no discernable difference between the two versions as far as my daily backups are...
Sorry I mistakenly thought it used it's own driver.
I'd be wary of using a program that hasn't been updated for a year, especially on Windows 10, which has received major updates in that time.
Thanks :thumb:
@VoodooShield All working great here. Rebooted several times with no issues, using 3.54 "Krusty" beta! on Win 8.1 Ent. x64 Thanks for the updated...
Personally I don't notice any difference. The headline CBT feature sounds good but it's only any interest if you plan to perform incremental...
Thanks. I will check out Winaero Tweaker as my next question was going to be 'how?'
Separate names with a comma.
