Windows discovery using WMI fails with - Error evaling C:\Users\dnsadmin\AppData\Local\Temp\GenerateWMIScriptJS_WMI_FetchData6214298325369083622.js: Expected ';'Issue For a windows server discovery, if the MID server from which the discovery is being executed has the MID service account running with a 'logon account' that may have the right access to the target system, The WMI classify will still end up throwing the error message - Error evaling C:\Users\dnsadmin\AppData\Local\Temp\GenerateWMIScriptJS_WMI_FetchData6214298325369083622.js: Expected ';'ReleaseExpected to happen in NewYork base version and above.CauseThis issue is caused because one of the MID server script files, "WMIRunner.js", is unable to handle an exception which in turn would be causing -Error evaling C:\Users\dnsadmin\AppData\Local\Temp\GenerateWMIScriptJS_WMI_FetchData6214298325369083622.js: Expected ';'ResolutionTo resolve the issue, please follow the below steps: Hop on to any instance which has the issue and for the MID server using which the windows discovery is being executed, you may see the property mid.use_powershell = false as the expectation is to trigger WMI remote command execution and not Powershell.Navigate to MID server-> MID server script files --> Take an XML back up of "WMIRunner.js" file already present and upload the XML(ecc_agent_script_file_b6fdf97bef65010098d5925495c0fb57 (1).xml ) attached to PRB1384070.Once done, restart the MID server service on the target host for the new WMIRunner.js to take effect.Post the restart, run discovery for a target host and it would be successful.