Difference between revisions of "Windows Management Instrumentation"
From Conservapedia
(finished topic (for now)) |
(added issues section) |
||
| Line 1: | Line 1: | ||
'''Windows Management Instrumentation''' is a part of the [[Windows]] [[operating system]] which allows users to manage local and remote systems. Through this, daily management tasks using programming or scripting languages can be undertaken. Its features include rebooting a remote [[computer]], manually starting a process on a remote system, and can also include views, querying, eventing and remoting.<ref>http://www.neuber.com/taskmanager/process/wmiprvse.exe.html</ref> | '''Windows Management Instrumentation''' is a part of the [[Windows]] [[operating system]] which allows users to manage local and remote systems. Through this, daily management tasks using programming or scripting languages can be undertaken. Its features include rebooting a remote [[computer]], manually starting a process on a remote system, and can also include views, querying, eventing and remoting.<ref>http://www.neuber.com/taskmanager/process/wmiprvse.exe.html</ref> | ||
| + | |||
| + | ==Issues== | ||
| + | This process does not usually cause problems on its own. However, [[malware]] sometimes takes the same name, and tries to "hide in plain sight." This process may use a fair amount of [[CPU]] power while it indexes hardware, but if this high usage persists for hours or especially days, you may have a problem. | ||
==Process Names== | ==Process Names== | ||
Revision as of 20:51, February 3, 2016
Windows Management Instrumentation is a part of the Windows operating system which allows users to manage local and remote systems. Through this, daily management tasks using programming or scripting languages can be undertaken. Its features include rebooting a remote computer, manually starting a process on a remote system, and can also include views, querying, eventing and remoting.[1]
Issues
This process does not usually cause problems on its own. However, malware sometimes takes the same name, and tries to "hide in plain sight." This process may use a fair amount of CPU power while it indexes hardware, but if this high usage persists for hours or especially days, you may have a problem.
Process Names
- WmiPrvSE.exe (or all lower case, wmiprvse.exe)
