Automatic Update Client Stuck in AU STATE# 4!!!

Automatic Update Client Stuck in AU STATE# 4


In this Article, I will explain, why Automatic Update Client Stucks in AU STATE# 4 and doesn’t installs the updates.


To see the AU State, you can run a simple Reg query from command prompt; You can download REG.exe from here.


Reg query “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update”


    SusServerVersion  REG_DWORD      0x1

    AUState                 REG_DWORD      0x4

    NextDetectionTime REG_SZ              2004-10-06 05:54:40

    ConfigVer             REG_DWORD      0x1

    LastWaitTimeout    REG_SZ              2004.10.07 01:23:20


Also, Run Bitsadmin /list /allusers /verbose to see what is in the queue (BITS ADMIN is in the Support-tools directory on the XP CD)


Actually AU STATE# 4 means Automatic Update Client is downloading patches. If this state remains for more than expected time then that means it got stuck while downloading the patches. It is due to BITS service (which downloads the patches) which might get stuck in resolving the SUS SERVER NAME which you have defined in SET OPTIONS;


Here are few tips to avoid such behavior;


  • Make sure you have defined the correct SUSSERVER NAME.

  • Try using IP ADDRESS instead of NETBIOS NAME / FQDN of SUS Server in SET OPTIONS to ease the name resolution process.

  • Use the same IP Address instead of NetBIOS name while configuring AU Client thru GPO (WUAU.adm Template) or thru Registry edits.

Optionally, you can try to add the SUSSERVER NAME with IP ADDRESS in the hosts file (C:\WINDOWS\system32\drivers\etc\hosts) of the client which enables the client to resolve the hostname/NetBIOS name thru this host file.


Happy Reading!
Mohammed Athif Khaleel
Windows Server Update Services Wiki
Save the Internet. Keep all Systems Patched


[This posting is provided “AS IS” with no warranties and confers no rights.]

Leave a Reply

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