<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Npcap on Anything About IT</title><link>https://www.verboon.info/tags/npcap/</link><description>Recent content in Npcap on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 23 Aug 2022 15:48:36 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/npcap/index.xml" rel="self" type="application/rss+xml"/><item><title>Microsoft Defender for Identity - Npcap driver Update</title><link>https://www.verboon.info/2022/08/microsoft-defender-for-identity-npcap-driver-update/</link><pubDate>Tue, 23 Aug 2022 15:48:36 +0000</pubDate><guid>https://www.verboon.info/2022/08/microsoft-defender-for-identity-npcap-driver-update/</guid><description>&lt;p&gt;Hello everyone,&lt;/p&gt;
&lt;p&gt;In July 2021 Microsoft &lt;a href="https://techcommunity.microsoft.com/t5/microsoft-defender-for-identity/microsoft-defender-for-identity-and-npcap/m-p/2584151"&gt;announced&lt;/a&gt; that starting with MDI version &lt;a href="https://docs.microsoft.com/en-us/defender-for-identity/whats-new"&gt;2.156&lt;/a&gt; they included the OEM version of the Npcap executable in the Sensor deployment package. The reason for doing so is because WinPcap is no longer supported and since it&amp;rsquo;s no longer being developed, the driver cannot be optimized any longer for the Defender for Identity sensor. Additionally, if there is an issue in the future with the WinPcap driver, there are no options for a fix. More details can be found &lt;a href="https://docs.microsoft.com/en-us/defender-for-identity/technical-faq"&gt;here&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>