1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Error when trying to Device Manager: Snap-in failed to initialize

Discussion in 'Windows XP' started by yellowcat, 2004/11/24.

Thread Status:
Not open for further replies.
  1. 2004/11/24
    yellowcat

    yellowcat Inactive Thread Starter

    Joined:
    2003/12/13
    Messages:
    16
    Likes Received:
    0
    I have Windows XP With SP 2 installed.Now when I try to open the device manager I get This error message

    Snap-in failed to initialize
    Name:<unknown>
    CLSID:{74246BFC-4C96-11DO-ABEF-0020AF6BOB7A}

    Anyone have any ideas?I did search Microsoft some ,but I did not find anything about not being able to open the Device Manager.
    Thank you
     
    yellowcat,
    #1
  2. 2004/11/24
    Steve R Jones

    Steve R Jones SuperGeek Staff

    Joined:
    2001/12/30
    Messages:
    12,317
    Likes Received:
    252
    Steve R Jones,
    #2


  3. to hide this advert.

  4. 2004/11/24
    yellowcat

    yellowcat Inactive Thread Starter

    Joined:
    2003/12/13
    Messages:
    16
    Likes Received:
    0
    Device Manager

    Tried both of soloutions nether one changed anything.I still get the same error.
    Thanks
     
    yellowcat,
    #3
  5. 2004/12/01
    yellowcat

    yellowcat Inactive Thread Starter

    Joined:
    2003/12/13
    Messages:
    16
    Likes Received:
    0
    Device Manager

    Finally figured out that I had an error with the Microsoft Management Console,that is way I could not get into the Device Manager.I ended up reformating my hardrive and reinstalling XP SP2.I looked on the net but I could not find any way to repair it.Everthing is up and running fine now.Anyone have a clue as to what caused this error?
    Thank you
     
    yellowcat,
    #4
  6. 2004/12/01
    Newt

    Newt Inactive

    Joined:
    2002/01/07
    Messages:
    10,974
    Likes Received:
    2
    Not a clue what broke your mmc but
    start => run => sfc /scannow and OK might have fixed it for you without needing the reinstall.
     
    Newt,
    #5
Thread Status:
Not open for further replies.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Accept Learn More...