WMI timeout on a few machines
I'm noticing on a few machines that they will struggle when doing the "disks" scan and I believe because of that long duration on that scan they will end up posting a WMI operation timed out. I've already increased the timeout to 240 seconds and there were still a few machines posting this timeout. When I removed the "disks" scan function from the profile then they scanned successfully.
Is the WMI timeout the entire duration of the scan function? meaning if the whole process takes longer than 4 min it will just time out? If so I would probably just raise this to 480 to see if these machines complete a full scan in that time. That could point to them just being older and slower, which I wouldn't disagree with. But there is one that is a relatively quick machine with an SSD and still times out.
Comments
Hi Jonathan,
I'll suggest you raise the timeout again and see what happens. If the problem sstill persis, I'll uggesty you do some maintenance on the particular machines.(in command line as admininistrator
SFC ./SCANNOW
DISM /online /cleanup-image /scanhealth use DISM /online /cleanup-image /restorehealth if problems are found)
If that does not help, then you should fix the WMI, go with the guide on Spiceworks:
https://community.spiceworks.com/how_to/2382-solving-timeout-waiting-for-wmi-connection
Let us know if any of the steps helped
Hi everyone,
I'm having similar issues with only a few machines (increasing the WMI timeout from 90 to 180 seconds did not help). I was able to track down the problem to SD card readers.
Once I unplugged the SD card reader from the mainboard there where no issues. I can't tell for sure if it's a PDQ problem since I wasn't even able to open the Disk Management MMC snap-in (it did load forever), maybe a 2004 (driver) issue?
The attached picture shows the SD card reader in the 'Disk Drives' before it was unplugged from the mainboard.
Hi Vitus,
first of all, I see that the device is using a generic driver. Try to locate the manufacturers website and download their drivers.
Its not PDQ Inventory's fault if WMI is not working as it should. My experience is that I had to set the WMI timeout to 360s on old systems and even then it happened time to time that I had to re-run the scan because it failed.
Check out DriverCloud it will help you to locate the most up to date drivers for your devices. I am using it for years now.
Just getting back to this issue, at 240 timeout I still have 3 machines that regularly post a WMI timeout issue so I will attempt the fix in the Spiceworks link on those machines and see if it helps. They are all older machines, but not overly slow. All three do have multi card type readers, with Generic drivers as well. Some of these devices I'm sure won't have a supportive driver for Windows 10 either due to their age, but I will also check that avenue since I have that similarity with Vitus Niemeyer.
Well that was short lived... WmiDiag.vbs is no longer available for download from Technet... I will have to do some searching to see if I can find it elsewhere from a trustworthy source.
I've got the WMIDiag.exe from 2013 here. Its signed by Microsoft. If you don't find it, let me know and I can put it on my server.