rdam1989:
You are right Scott, although in my time reading the forums it more times then not being you that has solved so many problems. I cannot imagine that I am the only one that is experiencing this and somehow I believe it is related to a WGT update.
Thank you for anything you can find, it is greatly appreciated,
Rich
Have you looked at error logs?
To identify which specific process is causing problems with WMI, use the Event Viewer. On Windows 10 or 8, you can right-click the Start button and select “Event Viewer” to open it. On Windows 7, open the Start menu, type “Eventvwr.msc”, and press Enter to launch it.
In the left pane of the Event Viewer window, navigate to Applications and Service Logs\Microsoft\Windows\WMI-Activity\Operational.
Scroll through the list and look for recent “Error” events. Click each event and look for the number to the right of “ClientProcessId” in the bottom pane. This tells you the ID number of the process that caused the WMI error.
There’s a good chance you’ll see several errors here. The errors may be caused by the same process ID number, or you may see multiple different process IDs causing errors. Click each error and see what the ClientProcessId is to find out.
You can now pin down a process that may be causing problems. First, open a Task Manager window by pressing Ctrl+Shift+Escape or by right-clicking the taskbar and selecting “Task Manager”.
Click over to the “Details” tab, click the “PID” column to sort running processes by process ID, and locate the process matching the ID number that appeared in the Event Viewer logs.
For example, here, we’ve seen that the “HPWMISVC.exe” process caused these errors on this particular computer.
If the process has since closed, you won’t see it in the list here. Also, when a program closes and reopens, it will have a different process ID number. That’s why you need to look for recent events, as the process ID number from older events in your Event Viewer won’t help you find anything.
With this information in hand, you now know the process that may be causing problems. You can search for its name on the web to find out the software it’s associated with. You can also just right-click the process in the list and click “Open File Location” to open its location on your system, which may show you the larger software package the program is a part of. You may need to update this software if you use it, or uninstall it if you don’t.