Windows Vista SP1 - Why Isn't Windows Update Showing It To Me?

If you're waiting patiently for Windows Vista SP1 and Windows Update isn't letting you know about it, then you probably want to go and look at MSKB 948343 for a list of reasons why you're not seeing it.

In particular, check your driver versions. This is the current list of drivers known to be problematic with SP1:

Audio drivers
Realtek AC'97

• For x86-based computers: Alcxwdm.sys - version 6.0.1.6242 or earlier

• For x64-based computers: Alcwdm64.sys - version 6.0.1.6242 or earlier

SigmaTel

• For x86-based computers: Sthda.sys - version 5.10.5762.0 or earlier

• For x64-based computers: Sthda64.sys - version 5.10.5762.0 or earlier

SigmaTel

• For x86-based computers: Stwrt.sys - version 6.10.5511.0 or earlier

• For x64-based computers: Stwrt64.sys - version 6.10.5511.0 or earlier

Creative Audigy

• For x86-based and x64-based computers: Ctaud2k.sys - version 6.0.1.1242 or earlier

• For x86-based computers: P17.sys – all versions (This was originally a Windows XP-based driver.)

Conexant HD Audio

• For x86-based computers: Chdart.sys - version 4.32.0.0 or earlier

• For x64-based computers: Chdart64.sys - version 4.32.0.0 or earlier

Biometric (Fingerprint) Sensors

• AuthenTec Fingerprint Sensor with the Atswpdrv.sys driver file – version 7.7.1.7 or earlier

• UPEK Fingerprint Sensor with the Tcusb.sys driver file – version 1.9.2.99 or earlier

Display drivers
Intel Display

• For x86-based computers: Igdkmd32.sys – versions between and including driver 7.14.10.1322 and 7.14.10.1403

• For x64-based computers: Igdkmd64.sys – versions between and including driver 7.14.10.1322 and 7.14.10.1403

Other drivers
Texas Instruments Smart Card Controller with the GTIPCI21.sys driver file – version 1.0.1.19 or earlier
Sierra Wireless AirCard 580 with the Watcher.exe application – version 3.4.0.9 or earlier (This application is located in the AirCard 580 Program Files folder.)
Symantec software driver for Symantec Endpoint Protection and for Symantec Network Access Control clients

• For x86-based computers: Wgx.sys – versions 11.0.1000.1091 or earlier

• For x64-based computers: Wgx64.sys – versions 11.0.1000.1091 or earlier

Note Symantec is aware of this issue, and it is working on a solution. Symantec provides various update procedures. This includes their LiveUpdate service.

Windows XP Netlogon 5719 Errors

Had a new PC to remotely install at a client site. The site is running Windows Server 2003 Domain Controllers and makes use of GPOs to manage the settings and software installation. I added the PC to the domain and placed it in the correct OU for the necessary software installation and rebooted. I was very surprised to not see any files being shifted from the server to the PC. Logged in remotely as Administrator and found that the User policies had been applied, but not the Computer policies.
A look through the Event Log found the dreaded Netlogon 5719 error - "no domain controller could be found". Tried locking down the network card to use 100Mbps/Full Duplex. No joy. Tried setting ExpectedDialupDelay in HKLM\System\CurrentControlSet\Services\Netlogon\Parameters. Still no joy.

The network card was an SiS 900 integrated NIC and an old driver was being used. Upgraded to the latest version of the driver. Still no joy. Right. Let off some steam by vigorously chopping some wood that really, really needed it. Still didn't help my GPO problem, but made a big difference to my mood.

I then decided to see what drivers were available to me for this network card. Found that there was a signed Microsoft driver for the SiS 900, so I decided to try this before having to go onsite with a new network card. Installed the driver, rebooted the system and noticed a flurry of file transfers from the server to the PC. Yay!

I shall now make sure that if I see the problem in the future to see if there's a signed Microsoft driver for the network card before getting hot under the collar (especially as the amount of wood to chop up is getting lower!).