NVIT
asked on
Did Powershell 4.0 break WMI?
Server 2008 R2.
I don't know if ps 4.0 is the cause but the last major change done on this server was on 12/23/17, upgraded from Powershell 2.0 to 4.0 per https://www.microsoft.com/en-us/download/details.aspx?id=40855
Issue first noticed on 12/26/17 in the log created by a bat utility that runs WMI to get drive space of various servers. Prior to issue, log showed without errors as expected on 12/23/17 to 12/15/17.
The Winmgmt service, which normally starts automatically, now doesn't. Manually starting the service returns:
"Windows could not start the Windows Management Instrumentation service on Local Computer."
When I run WinMgmt.exe gets error: WinMgmt.exe - Application Error. The application was unable to start correctly (0xc000007b). Click OK to close the application.
I ran SFC /scannow and attached parts of the cbs.log. The parts are where it tries to repair the wmi files but says "Cannot repair member file..."
Is it supposed to 'repair' the wmi files because wmi is broken? Or, is it normal, i.e. can't be repaired because I upgraded the powershell?
Has anyone come across this? Did you resolve it?
Server_SFC_WMI_Issues.txt
I don't know if ps 4.0 is the cause but the last major change done on this server was on 12/23/17, upgraded from Powershell 2.0 to 4.0 per https://www.microsoft.com/en-us/download/details.aspx?id=40855
Issue first noticed on 12/26/17 in the log created by a bat utility that runs WMI to get drive space of various servers. Prior to issue, log showed without errors as expected on 12/23/17 to 12/15/17.
The Winmgmt service, which normally starts automatically, now doesn't. Manually starting the service returns:
"Windows could not start the Windows Management Instrumentation service on Local Computer."
When I run WinMgmt.exe gets error: WinMgmt.exe - Application Error. The application was unable to start correctly (0xc000007b). Click OK to close the application.
I ran SFC /scannow and attached parts of the cbs.log. The parts are where it tries to repair the wmi files but says "Cannot repair member file..."
Is it supposed to 'repair' the wmi files because wmi is broken? Or, is it normal, i.e. can't be repaired because I upgraded the powershell?
Has anyone come across this? Did you resolve it?
Server_SFC_WMI_Issues.txt
ASKER
We uninstalled the antivirus. Rebooted. No joy.
Here are 10 fixes:
http://www.tomshardware.com/faq/id-1931360/0xc00007b-error-fix.html
http://www.tomshardware.com/faq/id-1931360/0xc00007b-error-fix.html
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Ok bud no problem, just mark the answers of the question please so it can be closed.
jose
jose
ASKER
A colleague installed and ran SFCFIX at http://www.majorgeeks.com/files/details/sfcfix.html which fixed the problem.
You can always uninstall PowerShell and re-install it, but I'd highly recommend going directly to Powershell 5.
Remember you will required 2008 R2 SP1 install to make it run as it should:
https://www.microsoft.com/en-us/download/details.aspx?id=50395