Failed to start service WMS - Error Id 1010

@Indianacarbnie - quick question, I took a look at 'Process Library' and agree that it looks a useful resource however, I also noticed that some of the explanations given, in this case concerning 'netmon.exe' seemed to be truncated. In other words the text reads - "........... in order to proceed with this action we recommend you."

It ends there in mid-air. Does that mean the text is taken from another source or is it available in complete form somewhere else?

Regarding potential side effects of renaming 'netmon.exe' I'm not sure if this is related but I am now seeing a large number of 'event id 129' - Log Name: System
Source: storahci
Date: 31/01/2018 10:23:51
Event ID: 129
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Description: Reset to device, \Device\RaidPort0, was issued.

No idea yet if this is related or not?

After a recent reboot, I experienced pretty bad computer lag. I mean the typing and clicking was a half-second delayed; opening, closing, and moving windows was slow; and running games was nigh impossible.

These files were the collective culprit. I'll explain everything.

In this folder: C:\Windows\nvidia were "wintask.exe" and "NvUpdater64.exe". In the Services, you'd find something like NVU, which pointed to "wintask.exe" and claimed to be the "NVIDIA driver updater". When this service was running, my computer was laggy, and the Task Manager (and superior Process Explorer) displayed regular low usages for CPU, GPU, RAM, and I/O. After looking up NvUpdater64, it seems to be a virtual currency miner...

Anti-malware programs detected nothing wrong with these files. I already submitted them to Microsoft and Malwarebytes.

They had connections in the registry to NSSM... Sound familiar? That's the Source of the Event originally in question in this topic.

I recommend removing everything related to them. I followed the manual instructions here since I don't trust those downloads: http://greatis.com/blog/how-to/remov...ater64-exe.htm

As an aside, it seems that C:\Windows\wmi\WmiPrvSE.exe was also involved, but I ended up removing that earlier during my troubleshooting. That file name belongs in two or three other folders, not in wmi.

I hope this post helps people who stumble upon this later.