Link to home
Create AccountLog in
Windows Server 2008

Windows Server 2008

--

Questions

--

Followers

Top Experts

Avatar of Naj Saqi
Naj Saqi🇦🇺

WMI Issue: Cannnot
I am running Windows Server 2008 R2 x64


I couldn't install SCCM and SCOM clients due to WMI issues. Whenever I try to look at the properties of WMI Control, it says:

User generated image
Failed to initialize all required WMI classes
Win32_processor:Win32: Class not registered
Win32_WMI setting: Successful
Security Information : Successful
Win32_Operating System:Win32: Class not registered

I am attaching the WMIDiag Report as well.

I have tried everything in regards to rebuild/repair repository but issue still persists. I have already tried the following methods:

http://chrisneiger.blogspot.com/2011/06/re-register-wmi-on-windows-server-2008.html
http://www.paessler.com/knowledgebase/en/topic/3713-i-have-tried-a-lot-of-things-to-fix-my-wmi-what-else-can-i-try-to-avoid-reinstalling-windows
http://katyscode.wordpress.com/2007/02/03/tutorial-how-to-fix-wmi-corruption/
http://www.jim-doyle.com/?p=1271
WMIDIAG-V2.1-2K8R2.SRV.SP1.64-TA.TXT

Zero AI Policy

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.


Avatar of RobSampsonRobSampson🇦🇺

The second link you posted is the most comprehensive list I've ever seen.....if something there doesn't fix it, I'm not sure what would!

I haven't read through all of that, but in the WMIDiag, there is this:
!! ERROR: WMI service DCOM setup: ...................................................................................... ERROR!
=> You can correct the WMI service DCOM configuration by executing the two following commands:
REGSVR32.EXE WMISVC.DLL
UNSECAPP.EXE /REGSERVER
FOR %i IN ("C:\WINDOWS\SYSTEM32\WBEM\WBEM*.DLL") DO REGSVR32.EXE /S %i

Once completed, stop and restart the WMI Service with the following commands:
NET STOP WINMGMT
NET START WINMGMT

Open in new window


The log also says this:
29 error(s) 0x80040154 - (WBEM_UNKNOWN) This error code is external to WMI.
=> This error is not a WMI error. This error is a DCOM component registration error.
   The registry information for DCOM to initialize a DCOM object is missing or wrongly configured.
   - An application has changed the COM/DCOM settings of OLE32.DLL and/or OLEAUT32.DLL.
   - The registry settings of COM/DCOM has been damage or wrongly modified.
   - The registry security settings of COM/DCOM has been damage or wrongly modified.
=> Verify WMIDiag report if ERRORS or WARNINGS are reported about the DCOM security for
   the following DCOM objects:
   - 'My Computer'
   - 'Windows Management Instrumentation'
   - 'Microsoft WMI Provider Subsystem Host'
   - 'Microsoft WBEM UnSecured Apartment'
=> You must also verify with 'REGEDIT.EXE', if the 'Users' builtin group is granted read access for
   the following registry hives:
   - HKCR\APPID
   - HKCR\CLSID
   - HKCR\APPID\{1BE1F766-5536-11D1-B726-00C04FB926AF} (WinMgmt EventSystem APPID keys)
   - HKCR\CLSID\{1BE1F766-5536-11D1-B726-00C04FB926AF} (WinMgmt EventSystem CLSID keys)
   - HKCR\APPID\{8BC3F05E-D86B-11D0-A075-00C04FB68820} (WinMgmt APPID keys)
   - HKCR\CLSID\{8BC3F05E-D86B-11D0-A075-00C04FB68820} (WinMgmt CLSID keys)

Open in new window


which suggests registry permissions might be screwed up, so you could try resetting all permissions to their defaults as shown here:
http://www.windowsreference.com/security/reset-the-entire-registry-permissions-to-defaults/

And, you've probably seen and / or done this already:
    - a WMI repository corruption.
      In such a case, you must rerun WMIDiag with 'WriteInRepository' parameter
      to validate the WMI repository operations.
    Note: ENSURE you are an administrator with FULL access to WMI EVERY namespaces of the computer before
          executing the WriteInRepository command. To write temporary data from the Root namespace, use:
          i.e. 'WMIDiag WriteInRepository=Root'
    - If the WriteInRepository command fails, while being an Administrator with ALL accesses to ALL namespaces
      the WMI repository must be reconstructed.
    Note: The WMI repository reconstruction requires to locate all MOF files needed to rebuild the repository,
          otherwise some applications may fail after the reconstruction.
          This can be achieved with the following command:
          i.e. 'WMIDiag ShowMOFErrors'
    Note: The repository reconstruction must be a LAST RESORT solution and ONLY after executing
          ALL fixes previously mentioned.
!! WARNING: Static information stored by external applications in the repository will be LOST! (i.e. SMS Inventory)

Open in new window


If all that fails, then I'm at a loss.

Regards,

Rob.

Avatar of Naj SaqiNaj Saqi🇦🇺

ASKER

Well,  by reseting the registry permissions,  i ended up in blue screen.  Now we are trying to restore our domain controller.

Avatar of RobSampsonRobSampson🇦🇺

Oh that's yuck!  Sorry that's happened.  It evidently worked for quite a few people by the replies on that site.  You never know what Windows will do.....

I sincerely hope you have some luck with restoring your domain controller.

Rob.

Reward 1Reward 2Reward 3Reward 4Reward 5Reward 6

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.


ASKER CERTIFIED SOLUTION
Avatar of Naj SaqiNaj Saqi🇦🇺

ASKER

Link to home
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Create Account
Windows Server 2008

Windows Server 2008

--

Questions

--

Followers

Top Experts

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.