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.

group policy window

Discussion in 'Windows XP' started by ackerberg, 2005/03/22.

Thread Status:
Not open for further replies.
  1. 2005/03/22
    ackerberg

    ackerberg Inactive Thread Starter

    Joined:
    2002/02/02
    Messages:
    869
    Likes Received:
    2
    How do I locate and view the Group Policy Window.
    I would have thought that typing "gpedit.msc" no quotes into RUN would have turned it up, but I get the message that nothing can be found. Got this ifo from the book Windows XP annoyances, p.248.
     
  2. 2005/03/22
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    AFAIK Group Policy is only available in XP Pro - which are you running?
     

  3. to hide this advert.

  4. 2005/03/22
    ackerberg

    ackerberg Inactive Thread Starter

    Joined:
    2002/02/02
    Messages:
    869
    Likes Received:
    2
    I'm running Win XP home. This is my problem which occurs at shutdown. Here are two messages from the events log just at shutdown:
    Event Type: Information
    Event Source: Application Popup
    Event Category: None
    Event ID: 26
    Date: 3/22/2005
    Time: 12:21:04 PM
    User: N/A
    Computer: BOBBY2
    Description:
    Application popup: dwwin.exe - DLL Initialization Failed: The application failed to initialize because the window station is shutting down.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Event Type: Information
    Event Source: Application Popup
    Event Category: None
    Event ID: 26
    Date: 3/22/2005
    Time: 12:21:04 PM
    User: N/A
    Computer: BOBBY2
    Description:
    Application popup: drwtsn32.exe - DLL Initialization Failed : The application failed to initialize because the window station is shutting down.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    It seems that DrWatson wants to start but can not. Is there some reason why it should start? Everything on my computer works, except for this error message when I shut down. Am feeling very frustrated about not being able to solve this problem.
    In th events log I also found 3 red X's with the following info:
    1.The mrtRate service failed to start due to the following error. The system can not find the file specified
    2. The nVidia WDM Video Capturwe(Universal) service failed to start due to the following error: The service cannot be started either because it is disabled or because it has no enabled devices associated with it
    3.The nVidia WDM A/V Crossbar service failed to start due to the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

    Does anyone have any idea of what's going on here?
     
  5. 2005/03/23
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    See here for an explanation - and solution for dwwin.exe.

    mrtRate service is part of Quicken - see post #9 & 10 here for solution.

    the nVidia messages refer to functions of an nVidia VIVO video card - you may need to reload/update the drivers if you have this card installed.
     
  6. 2005/03/23
    BenMcDonald[MS]

    BenMcDonald[MS] Inactive

    Joined:
    2004/12/14
    Messages:
    228
    Likes Received:
    0
    Disabling error reporting (dwwin.exe) is just hiding the fact that an exception is occuring, not that something didn't crash. I do not recommend following the advice in the article pete pointed to unless you understand the ramifications of not reporting exceptions.


    The biggest complaint about the error reporting service is it causing alot of various applications to not load or crash during use.

    This statement from that website is inaccurate. A program is crashing, and the error reporting tool invokes to collect data. It did not cause the crash, nor would it be running unless the crash occured and the system invoked the exception handler.

    I'm sure the site has no malice in the advice, but masking a problem by disabling the thing that reports its occurance isnt a solution.

    I spend part of my day looking at error reports generated by this tool. You are only hurting yourself (and others running the same software) by not reporting a crash. We pass crash information to vendors and our internal teams all the time. No report, no fix.
     
    Last edited: 2005/03/23
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.