Windows 7 Service Pack 1 Leaks

A number of readers have asked me this week why I've not touched on the recent leak of an early build of Windows 7 Service Pack 1. It's a fair question. I know that Microsoft plans to add little in the way of interesting functional updates in Windows 7 SP1 (whereas the server version is a far different story). But that's no excuse. So I downloaded the leaked build and am installing it now on a physical PC. I'll do a VM-based install as well and take some screenshots.

And there is some documentation that accompanies this build (6.1.7601.16537), which was made on March 27, 2070 and can be considered a pre-beta version. It notes:

Service Pack 1 for Windows 7 will include previously released updates.

The impact of SP1 on the Windows 7 client operating system is considered to be minimal. Included changes are expected to address minor usability issues in specific scenarios. While Microsoft always recommends that users deploy the latest service pack as quickly as possible in order to maintain the best levels of support, security and user experience, we are strongly recommending to customers and partners that deployment of SP1 should not be considered a blocking issue for the adoption of Windows 7. In other words, organizations do not need to wait for SP1 to begin receiving the value of Windows 7 today as we don’t anticipate the SP1 for Windows 7 to be substantial.

Changes specific to Windows 7

Additional support for communication with third-party federation services
Additional support has been added to allow Windows 7 clients to effectively communicate with third-party identity federation services (those supporting the WS-Federation passive profile protocol). This change enhances platform interoperability, and improves the ability to communicate identity and authentication information between organizations.

Improved HDMI audio device performance
A small percentage of users have reported issues in which the connection between a computer running Windows 7 an HDMI audio device is lost after a system reboot. Updates have been incorporated into SP1 to ensure that connections between Windows 7 computers and HDMI audio devices are consistently maintained.

Corrected behavior when printing mixed-orientation XPS documents
Prior to the release of SP1, some customers have reported difficulty when printing mixed-orientation XPS documents (documents containing pages in both portrait and landscape orientation) using the XPS Viewer, resulting in all pages being printed entirely in either portrait or landscape mode. This issue has been addressed in SP1, allowing users to correctly print mixed-orientation documents using the XPS Viewer.

Changes common to both client and server platforms

More efficient power consumption
SP1 introduces functionality that enables user-mode use of the invariant Time Stamp Counter (TSC). When utilized by application workloads such as SQL Server, the invariant-TSC provides a high resolution multimedia timer (necessary for functionality such as OLTP, data warehouse processing, and so on) at far greater power efficiency than previously available alternatives.

Change to behavior of "Restore previous folders at logon" functionality
SP1 changes the behavior of the “Restore previous folders at logon” function available in the Folder Options Explorer dialog. Prior to SP1, previous folders would be restored in a cascaded position based on the location of the most recently active folder. SP1 changes that behavior so that all folders are restored to their previous position.

Enhanced support for additional identities in RRAS and IPsec
Support for additional identification types has been added to the Identification field in the IKEv2 authentication protocol. This allows for a variety of additional forms of identification (such as E-mail ID or Certificate Subject) to be used when performing authentication using the IKEv2 protocol.

I'll have some screenshots and, if necessary, my notes available a bit later.

Discuss this Article 27

Dr. Daniel Jackson
on Apr 13, 2010
"Improved HDMI audio device performance " Much needed I have had alot of problems with this
chrishedlund
on Apr 13, 2010
Wouldn't this be considered a 'Much Ado About Nothing' article? Are you gonna post some Windows 2.0 screenshots?
beaker
on Apr 13, 2010
What? :) "And there is some documentation that accompanies this build (6.1.7601.16537), which was made on March 27, 2070 and can be considered a pre-beta version." I concur on the HDMI performance. It has been a frustration for me as well.
ShayaanF
on Apr 13, 2010
Paul, any idea whether or not SP1 will add support for multiple desktops? I've been waiting for this simple feature for a LONG time now!
pthurrott
on Apr 13, 2010
Chris H. Sure. But this is the SuperSite for Windows. I can't just say "nothing to see here," though I've been saying that since last year.
pthurrott
on Apr 13, 2010
ShayaanF: I will check, but I expect no improvements like that, sorry.
Dr. Daniel Jackson
on Apr 13, 2010
"In other words, organizations do not need to wait for SP1 to begin receiving the value of Windows 7 today as we don’t anticipate the SP1 for Windows 7 to be substantial." Even Microsoft says "nothing to see here"
scottbakertemp
on Apr 13, 2010
does Ultimate or Professional SP1 include the server part of remoteFX or just server 2008?
Grannyville
on Apr 13, 2010
SP1 sounds pretty much what I was expecting it to be. I hope it fixes the problem I have of Windows logging me into a temproary account which I have to log out of before actually can access my own, which I get every so often.
benjwah
on Apr 13, 2010
Snore. I don't mean that snarkily, just 'snore' because it's a service pack. I think at this point I'm completely cured of the expectations I once had for Service Packs: The first one I ever got was XP SP2, however by now I realise that that was a giant aberration. Still, if I ever have to re-install (which is pretty unlikely), this'll be nice. Any idea when it'll be released into the wild?
rr0de74@live.com
on Apr 13, 2010
Is firewire performance fixed? Its horrible right now, unless you switch to legacy driver. http://social.answers.microsoft.com/Forums/en/w7files/thread/a57e4e87-fc...
pthurrott
on Apr 13, 2010
When I was first told about SP1 last year, the plan was GA + one year, which would be October 2010. We'll see if that happens, of course.
Waethorn
on Apr 13, 2010
@Grannyville: When you have that problem, run SpinRite on your drive.
Waethorn
on Apr 13, 2010
@rrode: No problems here. I have an old 1394 drive that I keep for legacy archives, but I have no problems whatsoever. Stuff transfers as quickly as it did on XP, and that performance has been equal since my first dealings of IEEE 1394 with my first purchase of an OHCI IEEE 1394 PCI card for a Pentium 3 computer I had years ago - the same computer that I bought that hard drive for. It's a 20GB hard drive, btw.
Grannyville
on Apr 13, 2010
@pthurrott Do you believe Microsoft will release a public beta of the service pack?
subzerohitman721
on Apr 14, 2010
I hope Microsoft looks at shoring up or improving ASLR & DEP issues identified by various hackers at the CanSecWest's PWN 2 OWN contest in SP1. If Microsoft does anything else with SP1, I'd really like them to further shore up the security defenses.
Delmont
on Apr 14, 2010
Granny, I get that login thing too with a temp account. Weird. About once a month.
Waethorn
on Apr 14, 2010
@moonmonkey: Good question. I'll be trying that out for deployment on new machines myself. They never had DISM for Windows Vista, and when SP1 came out, they still required that it be an "online" installation (meaning it has to be run from within Windows, not just patch some files through WinPE). The reason was because the servicing stack couldn't be patched offline for whatever reason. With DISM, that could change. Since it appears that the servicing stack for Windows 7 isn't modified in this service pack, DISM may indeed work. I don't recall if DISM works with Windows Vista, but here's something you could try in the mean time: Grab a copy of Vista SP1 (since it already has the latest servicing stack), and try DISM with SP2. If that works, then it should also work with Windows 7 SP1. Be aware that DISM only patches with .MSU updates, and .CAB packages, so you can't just use the .EXE installer. Don't forget that the standard INSTALL.WIM on disc has multiple installation images too. You might want to recompress the WIM with maximum compression after you're done patching all of the images, otherwise single-instance-storage support for the WIM file won't be as efficient.
EricoF3
on Apr 14, 2010
Why releasing SP1 if it change near nothing to the system? @Paul : This SP1 will install automatically the Update that broke the Windows 7 Crack?
EricoF3
on Apr 14, 2010
@Paul : The SP1 will install the KB971033 update automatically?
pthurrott
on Apr 14, 2010
Eric ... Not sure. I'll try to find out. But MS did say that the WPA update would always be optional.
Waethorn
on Apr 14, 2010
@Delmont, granny: The only times I've ever experienced that problem on a standalone machine was when there was either some major problem with the folder structure on the disk (corrupt files), or the disk was failing mechanically. In either case, the drive had to be replaced. Sometimes it happens on a system with a roaming profile that can't authenticate to a domain controller properly, but if you aren't on a domain network, scan your hard drive with SpinRite and check for errors. Keep an eye on the SMART Status screen in SpinRite. High error counts (even if they are self-corrected) are not a good sign. Red blocks on the SMART screen are likewise not good. When one of the bars fills up with red blocks, you'll get an error during POST telling you to replace the drive, so any red blocks to begin with are a good indication that drive failure is imminent.
meason
on Apr 14, 2010
I think Windows 7 is the first Windows version where right out of the box I was not prey for a quick SP1 release..... I have had no problems what so ever even with my franken self built PC.
redunion1940
on Apr 14, 2010
EricoF3 the more prudent question is, why are you concerned if it brakes the hack to use Windows without providing money for the product and service it provides. The only problem I have been having is my sound not working after sleep mode sometimes, I have to as a fix that sometimes work, unplug my sound and then plug it back in, and even that doesn't work always so that I have to restart the entire machine, I dislike doing that.
rr0de74@live.com
on Apr 14, 2010
@wae if I follow that social.microsoft.com thread I linked and change my driver to "legacy" I get 70meg transfer rates to a Firewire 800 device. If I use the default Windows 7 driver I get around 5meg, which is slower than even the 20-25meg I get with USB 2.0. I have fixed it but only because I researched it and changed it to an old driver.
Grannyville
on Apr 14, 2010
@Waethorn I've already tried that and SpinRite comes back with no errors on the drive. And the problem still remains. However, it doesn't happen often enough to be a pain :)
Waethorn
on Apr 14, 2010
@rrode: Windows doesn't have a separate1394b driver because it's just not common, and controller manufacturers have had to tweak their chipsets because of general lack of support, both from the OS, but also from the industry in general. It's just not widely accepted. This issue is similar to how older OS's won't support 400Mbps networking over 1394a connections. Network support is limited to 100Mbps. The issue has to do with differences in hardware and error correction that's required by the driver for packet transfers to be successful over high speed protocols. 1394a transfers at a full 400Mbps for peripheral connections though, and even then, the issue only affects certain 1394 chipsets (again, similar to how early incarnations of 1394 were segmented before it became an OHCI standard). FWIW: I haven't seen this issue on Silicon Image or NEC 1394 controllers, but as far as 1394b controllers, I've probably seen only enough systems with it in the last few years to count on one hand. Also FYI: People experience performance issues relating to compatibility problems with 1394 on different OS's, and this is not unique to Windows 7. One of the people on that forum also mention that it happened on Windows XP, and another even said it affects 1394a controllers. The legacy driver doesn't have the performance of the new driver, but it's more compatible with differing controllers. The lack of backwards compatibility with 1394a is probably why 1394b never caught on. USB has used the same data port since 1.0, and eSATA is convertible from internal SATA. @granny: Dunno what it is then. In each case that it happened to a system here, it was a hard drive failure, and SpinRite confirmed it with a full surface scrub. SMART status was indicating early drive failure too. Replacing the drive and doing a clean install fixed the issue. The only other time I ever saw it happen was with a domain-joined system where the local copy of the user profile was botched because of an improper domain join, and the profile wouldn't be retrieved correctly from the DC. It happened every single attempt to log on though, not intermittently. If you notice odd things happening on the system from time to time (crashes, BSOD's, etc.) you might also want to check your RAM. Windows 7 preinstalls a memory checker that you can run. Click Start, and type "memory". Windows Memory Diagnostic will come up, so click on it. It'll reboot the system, run 2 scan passes on your RAM, then boot back into Windows and give you a summary of the results. You don't have to watch the scan as it runs. Memory problems can cause a number of intermittent problems with your system. A number of other components can do the same - bad motherboard, insuffient power/bad power supply, etc.

Please or Register to post comments.

IT/Dev Connections

Las Vegas
September 30th - October 4th

Paul ThurottYou'll have the opportunity to experience:
• 120 Technical
Sessions
• Networking with Peers
• Expert Speakers


Come See Paul Thurrott & Mary Jo Foley in Person!

Register Now

Office 365 InfoCenter

Get the latest insight and info from Paul

Read Now!

What I Use