WMI service problem

[Alexander_Topco]

Hello. On several computers in our network WMI service stops during Lansweeper scanning without error entries in Windows Event log. On the rest of computers it works without problems. When I try to start it manually, an error message displays:

"Windows could not start the windows management instrumentation service on local computer. error 1053: the service did not respond to the start or control request in a timely fashion."

I can start WMI after executing advices on this page. But WMI stops again after next scanning. At the same time WMI service works normally with other apps that uses WMI requests, for example System Information.
What is the reason?

[Susan_A · Accepted solution]

FYI for everyone: this issue is likely related to recent Lansweeper releases trying to configure a fixed WMI port on machines that generate RPC (firewall) errors. This process restarts the WMI service and appears to be causing issues on some machines.

We implemented a change in the 5.3 beta so that the scheduled tasks generated on the client machines by Lansweeper no longer restart the WMI service. They will still try to configure a fixed WMI port, but will no longer restart the WMI service in the process. This should hopefully resolve the issue.

[Susan_A]

Question received via email as well. We're troubleshooting there.