What’s Fixed In SP1
Bug fixes are a big part of any Microsoft service pack, but not just for the bugs being fixed specifically by the service pack. Microsoft has released numerous hotfixes since Vista launched, correcting a number of issues declared significant enough that they need to be fixed before the next service pack, but minor enough that they’re not worth a full deployment and the kind of massive regression testing that entails. The result is that there are a number hotfixes already out that can potentially fix specific issues certain users are having, but because they aren’t well-tested they’re instead well-hidden with only a small number of users with extreme problems usually getting their hands on any given hotfix. Now that a service pack has arrived, Microsoft has rolled up all of these hotfixes into the service pack, in essence approving them for wide release and full support.
Among the 24 pages(!) of hotfixes that have been rolled into Vista SP1 are favorites such as the virtual address space fix and a fix for a conflict with NVIDIA’s USB controller and >2GB of RAM. Other additions include fixes for ejecting iPods, a fix for HybridSLI/HybridCrossfire (which is why the launch of these technologies is tied to SP1), and a fix for AMD Barcelona processors causing system reboots during Windows installations. While we could rattle off the entire 24 page list of hotfixes, the important thing to note here is that there are a number of small issues that have been “fixed” prior to SP1 but are only now being widely corrected. We’re going to spend most of our time going over the biggest and most noticeable fixes in SP1, but please keep in mind there are many more things addressed in this service pack than what we’re looking at today or are listed in Microsoft’s consumer-level product literature.
Among the most significant fixes to Vista in SP1 is Microsoft's work on further refining the User Account Control (UAC) prompts of Vista. Even after already being scaled down between the betas and Vista’s launch, these prompts are still rather prolific at times. An adjustment to the folder creation is the most prominently touted of these fixes, with the number of folder creation prompts (when creating a folder in a protected location) falling from four to one. Microsoft doesn’t list any further reductions in UAC dialogs, but as far as anecdotal evidence is concerned it certainly feels like they’ve done a bit more than that. This won’t change the public perception of UAC (or Apple jokes on the subject), but any reduction is welcome and perhaps will stem the tide of Vista users who are completely turning off this critical system feature.
Another significant fix appearing in SP1 is a partial resolution to the conflict between the MultiMedia Class Scheduler Service and networking. As we’ve talked about the issue a bit before, the Vista audio stack is now in user space, which has lead to a change in how it operates. MMCSS boosts the priority of multimedia processes to real-time levels so that lower-priority processes can’t interrupt multimedia playback. During this time many other operations are interrupted or delayed so that they do not themselves interrupt the audio stack. One area that is dialed back involves the network interfaces, which are limited to 10k packets per second as a precaution.
For SP1 we were hoping for a complete overhaul of the MMCSS so that it ceased adversely affecting network performance, unfortunately what we’re getting is something about mid-way towards that. With SP1 it is now possible to control the amount of network throttling that MMCSS does, which means that throttling hasn’t been removed completely nor has it even been adjusted as far as the defaults are concerned. A quick test with Microsoft’s NTttcp tool shows the throttling level remains the same post-SP1 as it was pre-SP1 (roughly 70Mbps on a 1000Mb connection), which means SP1 will not be bringing any immediate relief. Furthermore there’s no GUI component (or real documentation) for this tweak, so users will be left to directly modifying the registry, a very uninviting situation.
What we do know is that this tweak only affects network receive performance, with a key apparently dictating the maximum percentage of the amount of network traffic allowed while the MMCSS is actively working. The key:
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Multimedia\SystemProfile\NetworkThrottlingIndex
...defaults to 10 (for 10%) and can be adjusted to between 1 and 100, with the system requiring a reboot between adjustments. We did some quick testing with this key and were easily able to set it to 70%, which got us around 550Mbps of bandwidth through NTttcp, and we probably could have gone higher - especially on multi-core platforms.
Default throttling (top) and throttling with an index value of 70 (bottom)
While this is a solution to the MMCSS throttling issue, it’s not a good solution. The default value still makes for rather anemic performance on gigabit networks and the nature of the solution means that there is no single correct value to use to maximize network performance while not interrupting the audio stack; the highest value is highly dependent on processor performance. As a result power users wanting to correct this deficiency will have to a lot of experimenting on their own to find the highest value their system can tolerate without affecting multimedia playback. Had this value at least been auto-sensing we wouldn’t be so disappointed in Microsoft, but at the end of the day this isn’t a great solution. We’ll fully admit the problem will only affect a small number of users (those with gigabit networks who need high network performance while using multimedia applications), but then we’re exactly that kind of user.
For what it’s worth, we did inadvertently discover that the MMCSS throttling process doesn’t engage when audio streams are using APIs other than WaveOut and DirectSound (i.e. aren’t directly routed through the user-mode audio stack). OpenAL and ASIO do not trigger throttling, which means it’s possible to have both unthrottled networking and proper multimedia playback under Vista, as long as there’s hardware present that can deal with these APIs. This may very well be good news for Creative Labs in particular, whose DirectSound-to-OpenAL “Alchemy” wrapper can be used to have DirectSound applications routed to OpenAL instead and preventing throttling.
NTttcp Performance | ||
|
MMCSS Active
|
MMCSS Inactive
|
Vista RTM |
70Mbps
|
940Mbps
|
Vista SP1 (Index 10) |
70Mbps
|
940Mbps
|
Vista SP1 (Index 70) |
550Mbps
|
940Mbps
|
. |
Moving on, SP1 also introduces a few interesting fixes for the user experience. For anyone who has a system running a 32-bit version of Windows and 4GB of RAM, they will be well aware that in 32-bit mode not all of that RAM can be addressed, and that Windows reports the amount that can be addressed accordingly. With Vista SP1 Windows will now be reporting the amount of RAM in the system, and not the amount that can be addressed. The advantage of this is that it will reduce the number of computer owners thinking something is wrong because Windows doesn’t “see” all of their RAM; on the other hand this is clearly disadvantageous because they will no longer be informed that Windows in fact isn’t using all of their RAM, nor will there be an easy way any longer to tell how much RAM it is capable of using.
Another user experience change with SP1 is that password
hints are no longer optional when accounts are being created. It turns out that
OEMs were complaining to Microsoft that users were forgetting their passwords
and had no easy way to recover control of their computer since the
Administrator account is no longer active by default, so Microsoft has done
something about it. Password hints are now mandatory for all user accounts so
that forgetful users are less likely to forget their passwords. How that will affect people that then forget what their hints mean remains to be seen.
62 Comments
View All Comments
Griswold - Wednesday, February 27, 2008 - link
Unless you are using vista NOW, you're not qualified to claim knowledge about performance issues NOW.mechBgon - Wednesday, February 27, 2008 - link
I think you should brush up on Windows Integrity Control and Kernel Patch Protection (for x64). These mandatory access controls are > users.Also, you are sadly incorrect in thinking that malware can only get onto a system with user cooperation. As the 4th-ranked SiteAdvisor reviewer worldwide (by total reputation), I have a fair amount of insight on the subject. ;) Between trusted sites being hacked and turned malicious, Mpack/Icepack-type exploit suites and vulnerable third-party software that people don't think to update, there's plenty of need for proactive security and mitigation.
You like WinXP? Great. For a 7-year-old OS, it can be secured fairly well, if you want to, and I even have tips to help with that: http://www.mechbgon.com/build/security2.html">http://www.mechbgon.com/build/security2.html But it's time for OSes to be more secure by default, in my opinion. The latest Security Intelligence Report from Microsoft showed WinXP SP2 is 2.5x more likely to have malware detected by the Malicious Software Removal Tool than Vista SP-zero, to throw one statistic out there.
Food for thought. I haven't seen much at AnandTech yet on that aspect of Vista.
Microsoft MVP ~ Windows Shell/User
kmmatney - Wednesday, February 27, 2008 - link
I don't see exFAT being useful right away unless windows XP is updated to support it.Staples - Wednesday, February 27, 2008 - link
Vista SP1 mostly has all the updates that MS has released over the past year on Windows Update. I did not notice a difference either and I installed SP1 a few weeks ago. If this was a vanilla install I was installing it over, I am sure I would notice quite a few improvements. I have been using Vista Home Premium since Jan and it definitely had some problems then. Since about July, the drives were mature enough and other than the slow slow file copying (which now still is slower than XP), everything has been running well for months.KeypoX - Wednesday, February 27, 2008 - link
On both laptop and desktop :( but i didnt really have any problems before... or after.johnsonx - Wednesday, February 27, 2008 - link
"That experience has been unified somewhat with SP1, now the x86 environment can install the x64 version of the OS (but ____ the other way around, interestingly enough)."I do think a 'not' goes in that blank.
(btw, none of the comment buttons like B, I, U, Quote, etc. are working for me atm)
InternetGeek - Tuesday, February 26, 2008 - link
I've been using SP1 on Vista Ultimate and it does bring some improvements. It took about one hour to install without any trouble at all. I simply started it and one hour later it was up as running.In general I find my laptop to be more responsive (Toshiba P105-S921). It restarts faster and comves alive from suspend faster as well. Applications in general feel the same, though tonight I'll play Oblivion and get a more "objective" feel of it. I used VS.NET 2008, Sql Server 2005, Photoshop CS2, Office 2007, DVDFab Platinum, Alcohol 120%, iTunes/WMP for media.
Div 6.8 stopped working all together after applying 6.1. It either crashes while analyzing the subtitles or while encoding. The movie is Transformers.
In general, I find that SP1 does bring good things for Vista on which, in general, I'm having a better experience than on XP.
aguilpa1 - Wednesday, February 27, 2008 - link
From that list you don't use any heavy duty applications, so yes you probably wouldn't notice a difference...Spivonious - Wednesday, February 27, 2008 - link
Photoshop, SQL Server, and VS2008 aren't "heavy-duty" applications? Just what is heavy-duty in your opinion?Griswold - Wednesday, February 27, 2008 - link
I bet using his favourite browser, posting crap like that in comments like this, is what he considers "heavy-duty".