calin radoni's humble web presence

home

docs

toolbox

about

Automatic Updates are not performed and error 0x80004015 is logged

Introduction
Symptoms
Cause
Solution
History
Copyright and License
Disclaimer

Introduction

In Windows Server 2003, a GPO defines the application of Automatic Updates service as Automatic correctly but these are not performed.

Symptoms

In the file Windows Update.log (or WindowsUpdate.log, the name depends of the version of Automatic Updates client) the error 0x80004015 is logged:

Client call recorder fails to init with error 0x80004015
WU client with version 5.4.3790.2182 failed to initialize with error 0x80004015 from component agent
Failed to initialize WU client: 0x80004015
WUAUENG ServiceMain exits. Exit code is 0x80004015

You may find in Event Log -> Security the following event:

Type: Failure Audit
Source: Security
Category: Object Access
Event: 560
User: NETWORK SERVICE

with a content similar to:

Object Open:
 	Object Server:        SC Manager
 	Object Type:          SERVICE OBJECT
 	Object Name:          wuauserv
 	Handle ID:            -
 	Operation ID:         {0,70117}
 	Process ID:           876
 	Image File Name:      C:\WINDOWS\system32\services.exe
 	Primary User Name:    xxxComputerNamexxx$
 	Primary Domain:       xxxDomainNamexxx
 	Primary Logon ID:     (0x0,0x3E7)
 	Client User Name:     NETWORK SERVICE
 	Client Domain:        NT AUTHORITY
 	Client Logon ID:      (0x0,0x3E4)
 	Accesses:             READ_CONTROL 
				Query service configuration information 
				Query status of service 
				Enumerate dependencies of service 
				Query information from service 
			
 	Privileges:           -
 	Restricted Sid Count: 0

Cause

If you read carefully the content of EventID 560 you will see that wuauserv tries to do some things (see Accesses) under the NETWORK SERVICE account and fails. This thing has lead me to examine the permissions for the Automatic Updates service. As expected, there was no mention about NETWORK SERVICE (This paragraph sounds a lot like what I have written in the IISADMIN failed to start with a stupid error: 2147549183 tip, I want to keep it consistent).

Solution

Here is a solution:

Find the GPO that configure the Automatic Update service. If you do not know how to do this, read my tip: How to find the settings applied through GPO in Windows XP .
Go to your Domain Controller.
1. Edit the GPO that configure the Automatic Update service
2. Go to Computer Configuration -> Windows Settings -> Security Settings -> System Services
3. Right click Automatic Updates and choose Properties
4. Select Define this policy setting
5. For Select service startup mode choose Automatic
6. Click Edit Security ...
7. Add NETWORK SERVICE with Read permission.
Go back to your computer.
1. Force the refreshing of policies by typing at a command prompt gpupdate /force
2. Open Computer Management -> Services
3. Select Automatic Updates
4. Start the service
5. Inspect again the file Windows Update.log
6. If everything is Ok, do like I did: take a day off.

For me, this extremely simple solution has solved the big and ugly problem of Windows Automatic Updates (after I have searched "the net" and Microsoft's site, coming back empty handed) and now, a few hundreds computers have innocent smiles...

History

21 June 2005, First version.

Copyright and License

Disclaimer

No liability for the contents of this document can be accepted. Use the concepts, examples and information at your own risk. There may be errors and inaccuracies that could be damaging to your system. Proceed with caution, the author do not take any responsibility.

All copyrights are held by their respective owners, unless specifically noted otherwise. Use of a term in this document should not be regarded as affecting the validity of any trademark or service mark. Naming of particular products or brands should not be seen as endorsements.

Hosted on http://www.oocities.org/calinradoni

Last page modification is 21 June 2005