Results 1 to 4 of 4
  1. #1
    New Lounger
    Join Date
    Jan 2013
    Posts
    2
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Errors in WMI Control Module

    Hello folks, I am recovering from an infection of one of the conficker viruses. I have gotten almost all of the machine’s
    systems back online except for the WMI service. I ran the WMIDiag program and have listed the problem area.
    I was hoping someone could explain how to get these Win32 errors corrected in the root directory. I have looked
    far and wide on the internet and have come up empty. I am not happy with the websites that say “Free scan to fix your
    problem”, only to download the program, run the scan, and then it says ,”You have multiple problems, Just pay $$$ to fix it”.
    What a bummer. I could go broke trying to fix it.

    Any help will be greatly appreciated as I have spent many many hours trying to fix this issue.
    I also can’t turn on the windows firewall system. I am hoping that fixing one issue will fix the other.

    Again, Thanks for the help.
    BTW-The rest of the WMI report was ok.


    .1842 20:54:09 (0) ** - Started at 'Root' --------------------------------------------------------------------------------------------------------------
    .1843 20:54:09 (0) ** WMI permanent SUBSCRIPTION(S): .................................................. .................................... NONE.
    .1844 20:54:09 (0) ** WMI TIMER instruction(s): .................................................. ......................................... NONE.
    .1845 20:54:09 (1) !! ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces: .......................................... 1 ERROR(S)!
    .1846 20:54:09 (0) ** - Root, 0x8007007E - The specified module could not be found..
    .1847 20:54:09 (0) **
    .1848 20:54:09 (1) !! ERROR: WMI CONNECTION errors occured for the following namespaces: .................................................. 16 ERROR(S)!
    .1849 20:54:09 (0) ** - Root, 0x8007007E - The specified module could not be found..
    .1850 20:54:09 (0) ** - Root, 0x8007007E - The specified module could not be found..
    .1851 20:54:09 (0) ** - Root/subscription, 0x8007007E - The specified module could not be found..
    .1852 20:54:09 (0) ** - Root/DEFAULT, 0x8007007E - The specified module could not be found..
    .1853 20:54:09 (0) ** - Root/CIMV2, 0x8007007E - The specified module could not be found..
    .1854 20:54:09 (0) ** - Root/CIMV2/Security, 0x8007007E - The specified module could not be found..
    .1855 20:54:09 (0) ** - Root/CIMV2/Applications, 0x8007007E - The specified module could not be found..
    .1856 20:54:09 (0) ** - Root/nap, 0x8007007E - The specified module could not be found..
    .1857 20:54:09 (0) ** - Root/SECURITY, 0x8007007E - The specified module could not be found..
    .1858 20:54:09 (0) ** - Root/WMI, 0x8007007E - The specified module could not be found..
    .1859 20:54:09 (0) ** - Root/directory, 0x8007007E - The specified module could not be found..
    .1860 20:54:09 (0) ** - Root/directory/LDAP, 0x8007007E - The specified module could not be found..
    .1861 20:54:09 (0) ** - Root/SecurityCenter, 0x8007007E - The specified module could not be found..
    .1862 20:54:09 (0) ** - Root/Microsoft, 0x8007007E - The specified module could not be found..
    .1863 20:54:09 (0) ** - Root/Microsoft/HomeNet, 0x8007007E - The specified module could not be found..
    .1864 20:54:09 (0) ** - Root/aspnet, 0x8007007E - The specified module could not be found..
    .1865 20:54:09 (0) **
    .1866 20:54:09 (0) ** WMI GET operations: .................................................. ............................................... OK.
    .1867 20:54:09 (0) ** WMI MOF representations: .................................................. .......................................... OK.
    .1868 20:54:09 (0) ** WMI QUALIFIER access operations: .................................................. .................................. OK.
    .1869 20:54:09 (0) ** WMI ENUMERATION operations: .................................................. ....................................... OK.
    .1870 20:54:09 (0) ** WMI EXECQUERY operations: .................................................. ......................................... OK.
    .1871 20:54:09 (0) ** WMI GET VALUE operations: .................................................. ......................................... OK.
    .1872 20:54:09 (0) ** WMI WRITE operations: .................................................. ............................................. NOT TESTED.
    .1873 20:54:09 (0) ** WMI PUT operations: .................................................. ............................................... NOT TESTED.
    .1874 20:54:09 (0) ** WMI DELETE operations: .................................................. ............................................ NOT TESTED.
    .1875 20:54:09 (0) ** WMI static instances retrieved: .................................................. ................................... 0.
    .1876 20:54:09 (0) ** WMI dynamic instances retrieved: .................................................. .................................. 0.
    .1877 20:54:09 (0) ** WMI instance request cancellations (to limit performance impact): .................................................. . 0.

  2. #2
    WS Lounge VIP
    Join Date
    Dec 2009
    Location
    Earth
    Posts
    8,191
    Thanks
    48
    Thanked 986 Times in 916 Posts
    WMI errors indicates deep seated problems and the only solution I use for these is a re-build.

    Backup all your data, especially passwords you have hidden in mail etc. Take an image as well to be extra sure.
    Disconnect the backup drive.
    Re-build, deleting all partitions to ensure you have clobbered the virus.

    cheers, Paul

  3. #3
    New Lounger
    Join Date
    Jan 2013
    Posts
    2
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Over the coarse of this repair, I am fairly sure I have killed the virus as I have recovered most of the systems that it had control of.
    Running the WMIDiag shows that I have a WIN32 problem which I know is equally bad, but am hoping that I can get around the total
    rebuild because I have many automotive programs that are hard to reload. I know a backup of a clean machine at the time would also
    have been a much better option, but alas, hindsite will always be better. I am also hoping that there is a way to reload the missing
    modules that the errors are pointing to. Unless someone says that I am just screwed, I am still hoping for the instructions to fixing the problem.
    Thanks for your siggection though, It is taken under advisement.

  4. #4
    WS Lounge VIP
    Join Date
    Dec 2009
    Location
    Earth
    Posts
    8,191
    Thanks
    48
    Thanked 986 Times in 916 Posts
    A search for "wmi not installed" found these possibilities.

    http://www.pcpitstop.com/pcpitstop/FixWmi.asp
    http://blogs.technet.com/b/askperf/a...epository.aspx

    cheers, Paul

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •