This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(32, 39%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
Any idea why "get-wmiobject win32_quickfixengineering" would hang on a group of windows 10 computers?
releaseid: 1909
ubr: 1646 (printnightmare patch kb5004946)
All Dell OptiPlex AIO's, 5250, 5270, 7480
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 74%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERM%3C/text%3E%3C/svg%3E)
If you use Get-CimInstance you can first create a CIM session and use that together with the -OperationTimeout parameter.
But here's the thing: is it the WMI operation that's the problem, or the RPC connection?
You can use your own CIM options for the CIM session and use WSMan as the protocol rather than DCOM.
It's WMI. It happens locally too. "wmic qfe" does the same thing. I think it's a problem with applying cumulative updates after not updating for a while.
Would (or does) the Get-HotFix cmdlet work for you?
Nope. I think it uses the same wmi class.
I don't know if you want to try this or not. You can install Visual Studio and ten down the PSMSI package from github (psmsi and compile the cmdlet.
Short of reimaging, I followed the directions on this page under "How to reset Windows Update using Command Prompt" and it worked for me. Sometimes I would have to kill the windows update service by force. https://pureinfotech.com/reset-windows-update-windows-10-fix-downloads-installs/ Windows update seems occasionally fragile. It would take me 90 minutes to reboot with "shutdown /r /t 0".
