WMI failed to connect to local computer on Win 7, error code 0x8007007e
Hi,
Please have someone here to point out the solution / workaround for the WMI issue i encountered on my Windows 7 with SP1, 32bit environment. Thanks in advance.
There is the status "WMI failed to connect to <local computer>, Because Win32: the specified module could not be found" is showed from WMI control screen, afterward I discovered the following warn/error massage are reported from Winows application
log. Moreover, the local computer is also failure connected by WMI through the WBEMTEST tool used.
I understood there may not be worth spent too much time for troubleshooting on desktop environment, however, my case is because the desktop environment that was critical using by on-going project, it may currently not be allowed to re-image
due to the applications configured via 3rd pty on that for project engagement needed.
BTW, I have tried many tricks discovered from internet world for solution, but all not luck for me, I'm looking forward to see the solution from this kindly forum for my problem encountered.
-
System
-
Provider
[ Name]
Microsoft-Windows-WMI
[ Guid]
{1edeee53-0afe-4609-b846-d8c0b2075b1f}
[ EventSourceName]
WinMgmt
-
EventID
43
[ Qualifiers]
49152
Version
0
Level
3
Task
0
Opcode
0
Keywords
0x80000000000000
-
TimeCreated
[ SystemTime]
2012-09-19T01:25:42.000000000Z
EventRecordID
12103
Correlation
-
Execution
[ ProcessID]
0
[ ThreadID]
0
Channel
Application
Computer
TW-LINJ4-1.ap.uis.unisys.com
Security
-
EventData
\\.\root\cimv2
0x8007007e
-
System
-
Provider
[ Name]
Microsoft-Windows-WMI
[ Guid]
{1edeee53-0afe-4609-b846-d8c0b2075b1f}
[ EventSourceName]
WinMgmt
-
EventID
28
[ Qualifiers]
49152
Version
0
Level
2
Task
0
Opcode
0
Keywords
0x80000000000000
-
TimeCreated
[ SystemTime]
2012-09-19T01:21:47.000000000Z
EventRecordID
12090
Correlation
-
Execution
[ ProcessID]
0
[ ThreadID]
0
Channel
Application
Computer
TW-LINJ4-1.ap.uis.unisys.com
Security
-
EventData
0x8007007e
September 20th, 2012 11:09pm
Hi,
Please perform the following steps to troubleshoot the issue:
1. Log onto Windows 7 with an administrator account, click Start, type services.msc in the Start Search box and press Enter.
2. In the right pane of the Service console, locate and right-click Windows Management Instrumentation, and then select Stop to stop
the service.
3. Start Windows Explorer, and then locate the %SystemRoot%\System32\Wbem\Repository folder.
4. Backup and delete all the files in the %SystemRoot%\System32\Wbem\Repository folder.
5. Restart the computer.
The files that were deleted will be re-created when the computer restarts.
Note: The Windows Management Instrumentation service starts automatically when you restart
the computer.
If the issue persists, please re-register WMI DLL files and re-compile WMI mof files to check if the issue can be resolved. Here are the detailed steps:
1. Disable and stop the Windows Management Instrumentation service.
2. Right-click Command Prompt and select Run as Administrator.
3. In the Command Prompt, type cd %windir%\system32\wbem and press Enter.
4. Type for /f %s in ('dir /b *.dll') do regsvr32 /s %s and press Enter to re-register WMI DLL files.
5. After completed, type for /f %s in ('dir /b *.mof') do mofcomp %s and press Enter to re-compile WMI mof files.
6. After that, type the command wmiprvse /regserver and press Enter.
7. Start the Windows Management Instrumentation service and change the Startup Type back to Automatic.
Hope this helps.Vincent Wang
TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
September 24th, 2012 5:01am
Hi,
Please perform the following steps to troubleshoot the issue:
1. Log onto Windows 7 with an administrator account, click Start, type services.msc in the Start Search box and press Enter.
2. In the right pane of the Service console, locate and right-click Windows Management Instrumentation, and then select Stop to stop
the service.
3. Start Windows Explorer, and then locate the %SystemRoot%\System32\Wbem\Repository folder.
4. Backup and delete all the files in the %SystemRoot%\System32\Wbem\Repository folder.
5. Restart the computer.
The files that were deleted will be re-created when the computer restarts.
Note: The Windows Management Instrumentation service starts automatically when you restart
the computer.
If the issue persists, please re-register WMI DLL files and re-compile WMI mof files to check if the issue can be resolved. Here are the detailed steps:
1. Disable and stop the Windows Management Instrumentation service.
2. Right-click Command Prompt and select Run as Administrator.
3. In the Command Prompt, type cd %windir%\system32\wbem and press Enter.
4. Type for /f %s in ('dir /b *.dll') do regsvr32 /s %s and press Enter to re-register WMI DLL files.
5. After completed, type for /f %s in ('dir /b *.mof') do mofcomp %s and press Enter to re-compile WMI mof files.
6. After that, type the command wmiprvse /regserver and press Enter.
7. Start the Windows Management Instrumentation service and change the Startup Type back to Automatic.
Hope this helps.Vincent Wang
TechNet Community Support
September 24th, 2012 5:03am