The Windows Process Journey — DrvInst.exe (Driver Installation Module)

<p>&ldquo;DrvInst.exe&rdquo; is a PE executable located at &ldquo;%windir%\System32\drvinst.exe&rdquo;, it is known as &ldquo;Driver Installation Module&rdquo;. Since Windows Vista when PnP (Plug and Play) manager detects a new device &ldquo;DrvInst.exe&rdquo; is started. It is used for searching and installing the relevant driver for the new device detected (<a href="https://learn.microsoft.com/en-us/windows-hardware/drivers/install/debugging-device-installations-with-a-user-mode-debugger" rel="noopener ugc nofollow" target="_blank">https://learn.microsoft.com/en-us/windows-hardware/drivers/install/debugging-device-installations-with-a-user-mode-debugger</a>).</p> <p>&ldquo;DrvInst.exe&rdquo; can also be used for installing drivers while installing a software package. Let us take for example the installation of &ldquo;OpenVPN Connect&rdquo; (<a href="https://openvpn.net/client/" rel="noopener ugc nofollow" target="_blank">https://openvpn.net/client/</a>).</p> <p>Thus, as with most VPN (Virtual Private Network) solutions there is a need to install a TAP driver, which is a virtual network device (<a href="https://www.techradar.com/vpn/what-is-a-tap-adapter" rel="noopener ugc nofollow" target="_blank">https://www.techradar.com/vpn/what-is-a-tap-adapter</a>). This causes &ldquo;services.exe&rdquo; to launch a new process using the following arguments &ldquo;C:\Windows\system32\svchost.exe -k DcomLaunch -p -s DeviceInstall&rdquo;, which is part of the &ldquo;DCOM Server Process Launcher&rdquo;. It is executed with the permission of the &ldquo;LocalSystem&rdquo; user.</p> <p><a href="https://medium.com/@boutnaru/the-windows-process-journey-drvinst-exe-driver-installation-module-d2ea1bcbb39f"><strong>Click Here</strong></a></p>