JSntgRvr Posted November 28, 2021 ID:1490215 Share Posted November 28, 2021 Upgrade to the latest version of Windows 10. Perhaps those entries will change with the new version. Here is the link: Download Windows 10 (microsoft.com) Link to post Share on other sites More sharing options...
scottish33 Posted November 29, 2021 Author ID:1490236 Share Posted November 29, 2021 I have already updated . Link to post Share on other sites More sharing options...
JSntgRvr Posted November 29, 2021 ID:1490238 Share Posted November 29, 2021 Are those rules present? Link to post Share on other sites More sharing options...
scottish33 Posted November 29, 2021 Author ID:1490239 Share Posted November 29, 2021 yes i am. Link to post Share on other sites More sharing options...
scottish33 Posted November 29, 2021 Author ID:1490240 Share Posted November 29, 2021 yes they are. Sorry for my english. Link to post Share on other sites More sharing options...
JSntgRvr Posted November 29, 2021 ID:1490243 Share Posted November 29, 2021 lets try to disable the rule: Highlight the entire content of the quote box below. Start:: Powershell: Disable-NetFirewallRule -DisplayName "@FirewallAPI.dll,-80201" Powershell: Disable-NetFirewallRule -DisplayName "@FirewallAPI.dll,-80206" End:: Right click on the highlighted text and select Copy. Start FRST (FRST64) with Administrator privileges Press the Fix button. FRST will process the lines copied above from the clipboard. When finished, a log file (Fixlog.txt) will pop up and saved in the same location the tool was ran from. Please attach this file to your next reply. Link to post Share on other sites More sharing options...
scottish33 Posted November 29, 2021 Author ID:1490244 Share Posted November 29, 2021 Fixlog.txt Link to post Share on other sites More sharing options...
scottish33 Posted November 29, 2021 Author ID:1490245 Share Posted November 29, 2021 The rule are actived yet. Link to post Share on other sites More sharing options...
Solution JSntgRvr Posted November 29, 2021 Solution ID:1490248 Share Posted November 29, 2021 I just wonder if these are created virtually, as none of these appear physically in Windows. Also, the consensus is that the 82201 is inbound TCP and 82206 Inbound UDP for the camera FrameServer through the svhost.exe which allows for a camera to be used by multiple applications at the same time. It is not malware and there are no more actions that should be taken. I see that this time, both entries are unchecked. If satisfied, mark this thread as solved. Link to post Share on other sites More sharing options...
scottish33 Posted November 29, 2021 Author ID:1490250 Share Posted November 29, 2021 ok thanks a lot. Link to post Share on other sites More sharing options...
Maurice Naggar Posted February 5, 2022 ID:1500890 Share Posted February 5, 2022 Glad we could help. If you need this topic reopened, please send a Private Message to any one of the moderating team members. Please include a link to this topic with your request. This applies only to the originator of this thread. Other members who need assistance please start your own topic in a new thread. Please review the following to help you better protect your computer and privacy Tips to help protect from infection Thank you Link to post Share on other sites More sharing options...
Recommended Posts