When Microsoft (NASDAQ: MSFT) released the final version of Windows Vista Service Pack 1 (SP1) for download this week, many observers were expecting that like the earlier service packs for Windows XP, it would turn out to be a debacle for users.
So far, however, that does not appear to be happening. Although some users have experienced problems with the update, many of the issues are ones that Microsoft warned about how to avoid on its Vista Team Blog site Tuesday.
Microsoft released SP1 for download by volume customers last month, but just made it available for download to consumers earlier this week.
So far, all in all, Microsoft user forums and support sites such as TechNet and Microsoft community news groups, appear to be relatively quiet compared with the fairly widespread troubles that users encountered particularly with XP SP1 but also to some extent with XP SP2. That doesn't mean there won't be problems, however.
For instance, some users ran into a problem they were already warned about – device drivers for some hardware and software that do not work correctly with SP1.
The complaints roll in
"When I go to windows update on my laptop to download SP1 it doesn't find the update," groused one user on Microsoft's TechNet forum for Vista SP1.
Besides audio boards from SigmaTel, Realtek, Conexant and Creative Labs, a few other devices with unsupported device drivers are also affected, including two fingerprint scanners, a pair of graphics displays, a smart card controller, and a wireless card.
"I have just spent one to two hours figuring out that I have one of the problem [SigmaTel] drivers hence why windows update isn't offering me SP1. Neither is it offering me an updated new driver. In my book that is not a good customer experience and a bit of a waste of my time," complained one user, commenting on the Vista Team Blog.
Other complaints revolve around a pre-requisite patch that Microsoft circulated earlier this year that caused some users' PCs to get stuck in a constant cycle of reboots during installation of SP1. Microsoft identified the problem and fixed it for most users.
Friday, 2 october 2009
