Slashdot Mirror
Windows Vista SP1 Meeting Sour Reception In Places
Stony Stevenson writes "A day after it was released for public download, Windows Vista SP1 is drawing barbs from some computer users who say the software wrecked their systems. 'I downloaded it via Windows Update, and got a bluescreen on the third part of the update,' wrote 'Iggy33' in a comment posted Wednesday on Microsoft's Vista team blog. Iggy33 was just one of dozens of posters complaining about Vista Service Pack 1's effect on their PCs. Other troubles reported by Vista SP1 users ranged from a simple inability to download the software from Microsoft's Windows Update site to sudden spikes in memory usage. To top it all off, the service pack will not install on computers that use peripheral device drivers that Microsoft has deemed incompatible."
You can manually search for new updates now and it'll appear and can be manually installed - however the phased process (3 updates total I think) will automatically occur next month.
You seem to believe that the service packs are nothing more than a "roll-up" of the other patches.
Here's news for you, they aren't.
There are 8 reasons SP1 may not appear if you check WU:
1. You are already running Windows Vista SP1.
2. Windows Vista SP1 has not been released for the language of the language pack that you have installed.
3. Windows Service Pack Blocker Tool is used to block the delivery of Windows Vista SP1 from Automatic Updates or from Windows Update.
4. You tried to install Windows Vista SP1, and the installation failed with a known inconsistency in the file or registry structure.
5. A hardware device driver or device software was problematic when you updated to Windows Vista SP1. The Windows Update service can detect the small set of device drivers and software that falls into this category. The Windows Update service will not offer Windows Vista SP1 until an update for the hardware device driver or the device software has been installed.
6. You have installed a prerelease version of Windows Vista SP1, and you must uninstall the prerelease version, or start with a new installation of Windows Vista.
7.You used the third-party program vLite to configure the system, and you may have removed required system components that have to be available for Windows Vista SP1 to be installed.
8. You see one or more updates for Windows Vista when you run Windows Update. However, you do not see Windows Vista SP1 listed.
At that website are further causes for those 8 reasons, but the specifically mentioned drivers that block SP1 are:
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
The problem there is that Microsoft never had a chance to lock people into hardware in the first place (and probably never wanted to, but i don't know anything about their motives back in the early days).
:(.
The people most responsible for the extreme number of hardware variations for the PC today? IBM. they allowed people to clone their architecture (not without a token fight, though, if I recall). Now we have two major cpu manufacturers, 3 major motherboard chipset manufacturers, 3 major video card manufacturers, millions of extra peripheral devices, and the end result is an impossibly large number of hardware configurations.
The main problem i've seen so far with SP1 has been it backing out after a good chunk of the installation process because some third party tool or driver (which is hard to identify) is holding onto a handle to something that windows update needs to update, but can't because there's an open handle.
At least it does the sane thing and backs out cleanly. Bummer to hear that it's failing for a few people, but you know, it's entirely likely that some third party software has snuck in where it was least expected.
Personally, I've never assumed that a service pack will apply cleanly on a machine that's been in use for some time. I tend to install them immediately after installing the O/S or service, and go from there. I'd do the same for going from RHEL 5.0 -> 5.1, or anything else. Takes away potential headaches.
Pity OEM installs of vista make that a pain, since the recovery image often contains a mountain of extra junk
Kernel data structure changes.
The problem with giving people just enough rope to hang themselves is that they want a little slack so that it's not uncomfortable when they're tying the noose and getting on the chair, and get it by taping on their own rope with duct tape.
See this for an example of this. It's a really painful thing, and really makes me feel sorry for people like Raymond Chen who has to deal with these kinds of issues for pay. (His book's kinda interesting tho)
Admittedly, a lot of the benefits to the linux driver model is that they *don't* get a lot of third party drivers, which helps eliminate a lot of this kind of problem. It still exists however. Just ask anyone who's trying to debug a kernel with the nvidia driver installed.
Red Hat ?
RPM-based Red Hat ?
You, sir, are full of shit. Sure, Red Hat tends to be stable when you stick to the base packages. The reason everything is 18 months out of date is because they test the living shit out of their builds, and that's fine. We used to call that Debian, btw.
Now, install something non-standard on Red Hat, and you almost have to unless you're doing something extremely simple, and you'll quickly find yourself at the mercy of disjointed updates, and the beloved hassle of virtual packages. This is true of any package management system, but RPM seems to make it just a little more painful than average, being bound to archaic build routines and an intentional lack of "cheating" abilities.
I use Red Hat, but all my mission-critical apps are built from source and kept far far away from the package manager.
-Billco, Fnarg.com