Windows Discovery Error: LaunchWMI : Access is denied. (Exception from HRESULT: 0x80070005(E_ACCESSDENIED))Description<!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms After upgrading to Madrid, running a discovery on Windows device may fail with below error, even if test credential is successful. launchWMI: Access is denied. (Exception from HRESULT: 0x80070005(E_ACCESSDENIED)) Release Madrid Cause Access to admin$ share on the target host was always a requirement for discovery to run successfully. For example, the document in the link below indicates that access to admin$\temp is required for WMI: Active Connections probe. The credential used should be a local administrator on the device being discovered. https://docs.servicenow.com/csh?topicname=r_AdditionalPermissions.html&version=latest On a Madrid Patch 3 release, a code change related to Powershell requires all WMIRunner probes to have access to the admin$/temp folder on the device being discovered. Resolution Ensure that the credential used is a local administrator on the host being discovered. If the credential used has necessary privileges, the cause could be Anti-virus, Anti-malware protection software / Host intrusion Prevention Software, in that case, try to disable the antivirus for testing purposes.