Andrew F.

Hi, Sorry, I must have missed the notification email for your reply somehow. And - yes, reproduced. Should be fixed for next release.

@m0unds Thanks, I've received the logs. Will try to reproduce it.

Thanks for explanation. Would it be possible to reproduce this and get a set of debug logs? (Please make sure to reboot after enabling debug logging). (Thank you in advance). But again... did you make sure that you didn't test your router ? About what windows shows - there's a bug with displaying the status of our firewall module in the windows defender, so the information there isn't correct. I believe there will be a notice in the changelist when this will be fixed.

Hello, Thank you for the input. EIS should block those ports for public networks only. Technically, when you switch the network type - you tell the firewall core which rules should be active. For example - rules blocking those tcp/udp ports are "enabled" for the public networks only. This means, that the rule should work for the public networks and shouldn't for the private ones. So, the ports being seen as open while in "private" network - is an expected situation. About the nmap.org and other tests from outside - did you make sure that you didn't actually test y

Hello, Could you please tell me whether the network type is set to "public" in EIS settings ? You can see that at Protection->Firewall->Manage Networks. A screenshot of that dialog would be even better than just a reply Thank you in advance,

Thank you for the feedback. Please feel free to create another thread if you'd need help with anything else.

You're welcome. Thank you for the feedback.

You're welcome. Looking forward for the feedback Thanks in advance,

I've analyzed your dumps. The BSOD is caused by a bug in Windows. There's a hotfix available from MS: https://support.microsoft.com/en-us/kb/2958399 We recomment that you uninstall Emsisoft Internet Security, install the hotfix and then install Emsisoft Internet Security again. Please note that the download from Microsoft will not install the hotfix. It will attempt to extract the installer for the hotfix to your C: drive so that you can run it and install the hotfix, however this will fail unless you run the download from Microsoft as an Administrator. The easy way around

Hello, Sorry you're having problems with EIS and thank you for submitting the dumps. I will take a look into the dumps asap.

Thank you for your kind words. I will post a reply here as soon as there will be a new beta available.

Thank you. Replied for the PM

Please see PM.

Hello, Sorry you're having troubles with EIS. And thank you for attaching the minidumps. I will investigate this asap.

Full memory dumps are always better Thanks, will download and analyze asap.

Hello, It'd be great to take a look at the minidumps. Please upload them. Thank you in advance,

Thank you for the feedback.

Hello, With the next stable release

Hello, Thank you for the dump. The latest beta should fix this problem (11.0.0.5935). You can receive the beta by switching to beta updates feed in Settings->Updates.

Hello, Could you please tell me whether you received the latest beta update ? (11.0.0.5935) Thank you in advance,

Thanks, downloaded.

Hello, Could you please give me the actual dump files ? Thank you in advance,

Thank you for the dump. Will look into asap.

You'd need to keep beta updates enabled to verify whether they fix the BSOD issue. Reverting back to stable will again cause the BSOD to appear.

Unfortunately, the archive is empty it seems. Could you please recreate the archive and upload it again ? Thank you in advance,