 Eddy
| It is the Windows Management Instrumentation Provider Service and it is an essential Windows XP/2003 service which will start whenever software requirires its facilities
|
 Eddy
| It is Part Of Windows Operating System
|
 b. gates
| very very bad file
|
 FrEaKaZoId
| Part of the esential windows process, dont touch it!
|
 HardUp
| Essential Do Not Renove
|
 Ryan
| Don't listen to b. gates, he probably wants to make people destroy their own computers!
|
 Koko
| Kernel_check wmiprvse.exe
X
Added by the SONEBOT-B WORM!
scApp wmiprvse.exe
X
Added by the W32/SillyFDC-AW worm.
winmgmt wmiprvse.exe
X
Added by the Troj/Agent-GHP Trojan.
|
 Ritch58
| From Experience I have found that I can end this process without causing any instablity to my system or installed software.
|
 John Martin
| Essential
|
 Pedro Ortiz
| Good!
|
 Ricky
| essential
|
 yo what is it?
| is it good or bad
|
 Matt
| yer i no its ms...but "whenever software requirires its facilities" doesn't happen, so you can safely end this process.
|
 churvanels
| magkano yelo?
|
 dna
| is it goog or bad this file
??????????????????????????????????
|
 JED
| ok as long as it resides in the folder C:WindowsSystem32Wbem. An easy way to see the location is to highlight it in the Glary Utilities Process Manager and hit the "Show Details" button. The folder is listed under the Process Information section.
|
 CnC
| The Wimprvse software is essential for security and stability of the operating system. The operating system requires this program to run smoothly. It is however important to see where the wimprse.exe is situated and what folder it is running from. A Windows operating system that is functioning normally often requires various accounts to run wmiprvse.exe. It is normal to see wmiprvse.exe simultaneously running in the LocalService, NetworkService, and the LocalSystem.
Wmiprvse.exe application is always situated in the systems32 folder of the Windows operating system. The filename and path is C:WINDOWSSystem32Wbem. If you happen to observe that wmiprvse.exe running from a different origin, meaning outside the systems32 folder, then there is a huge possibility that it is a Trojan, or a Virus. More information
|
 n43
| this processus suck
|