Clearing up Event Id 1030

I was getting lots of Event Id 1030 errors on a workstation — “Windows cannot query for the list of Group Policy objects”. I know I am not the only one to have seen these errors in their event logs. Microsoft CSS posted the following reg edit patch which cleared up the Event 1030 errors on my workstation:


Remove Bad Stored Credentials from the Credential Manager:


1. Run Regedit
2. Drill down to HKLM\System\CurrentControlSet\Control\Lsa
3. In the right pane locate the disabledomaincreds key
4. Change the disabledomaincreds value to 1 to stop store domain credentials.

13 thoughts on “Clearing up Event Id 1030

  1. 1. A great tip.
    2. I used it with “netsh winsock reset” and the combination of both solved my errors on the station.

  2. Kevin or G3:

    Any way to push this out system wide? I have about 2o or so stations that have been exhibiting this issue. This is a clean network with new SBS R2 install that was made several weeks back. Ever since I turned on WSUS, this error and others have been showing up in workstation event logs.

    Any help would be appreciated.

  3. I was also wondering if this affects the storing of credentials for those using laptops that may not be on the domain and they need to “logon” so that they can work “disconnected”????

  4. Thanks for the trip. I had user with lot of symcrhonization problems with Outlook and other domain services. The trip solved the problem.

  5. Hi

    I have this problem on my Domain Controller, but it is not SBS. Almost every week-end my DC will crash with event ID 1030 and 1053, and since it cannot be reached, all networks services (DNS, Exchange etc.) fails.

    I will try this registry change on my DC, but it seems almost too easy for a problem which has been bugging me for 6 months.

  6. I would imagine for multiple machines you could push a .reg file with those changes to the registry. Try that…

Leave a Reply

Your email address will not be published. Required fields are marked *