VIDEO Windows 7 Service Pack 1 (SP1) Download Available

[Mike]

Windows 7 Service Pack 1 (SP1), or KB976932, was confirmed as being pre-released to OEM manufacturers on February 9, 2011. The build had leaked to the Internet around January 14th. The official Windows Team Blog confirmed authenticity of build 1850 as the final RTM ("release to manufacturer") bits after much delay, debate, and discussion across the Internet. The release to manufacturer build contains the final bits which will ultimately be sent to MSDN customers, TechNet subscribers, Volume License Holders, and the general public. Before that, it is sent to OEMs. ("original equipment manufacturers").

Windows Server 2008 R2 SP1 and Windows 7 SP1 was released to manufacturers ("RTM") on February 9, 2011.

Microsoft has confirmed the RTM build number is 7601.17514.win7sp1_rtm.101119-1850 and we now have the highest level of certainty that these files are Windows 7 Service Pack 1 "Release to Manufacturer" (RTM), as we previously announced on January 14th. Microsoft TechNet Russia initially identified this build as the release to manufacturer version on January 14, 2011, but issued a warning that it had not yet been released to OEM partners.

Although the files have already leaked, we now have dates for the official release timetable:

TechNet/MSDN/Volume Licenses: February 16, 2011
Official Public Availability: February 22, 2011

The 32-bit and 64-bit versions are compatible with all languages. The 64-bit version also includes the Windows Server 2008 R2 Service Pack 1 RTM. Here is the following information:

We recommend that you:

• Download any files at your own risk. We are not responsible for lost data or damage.
• Observe best practices, including backing up your data prior to the installation of any operating system updates or modifications.
• We, again, strongly recommend that you thoroughly backup your system prior to the installation of any operating system update.

These files have been digitally signed by Microsoft, preventing unauthorized tampering or modification at the time of signing. The digital certificates have not been altered or tampered with.

The files have been tested on various types of hardware, without problem or difficulty. This does not guarantee that Service Pack 1 will work for you.

Temporarily disable your anti-virus, save all of your work, and turn off all programs before running the installer. This will improve the likelihood of a proper installation. Follow all on-screen instructions.

​

Windows 7 Service Pack 1 (SP1) 32-bit
Filename: windows6.1-KB976932-X86.exe
Filesize: 563,934,504 bytes
File Verification:
MD5 Checksum: 4bf28fc00d86c936c89e2d91ef46758b
SHA-1: C3516BC5C9E69FEE6D9AC4F981F5B95977A8A2FA
CRC: 5EB0FA87
Build Version: 7601.17514.101119-1850
Release Version: 7601.17514.win7sp1_rtm.101119-1850
Digitally Signed by Microsoft Corporation: ‎Sunday, ‎November ‎21, ‎2010 5:40:14 AM

Windows 7 Service Pack 1 (SP1) 64-bit
Windows Server 2008 R2 Service Pack 1 (SP1)
Filename: windows6.1-KB976932-X64.exe
Filesize: 947,070,088 bytes
File Verification:
MD5 Checksum: 28d3932f714bf71d78e75d36aa2e0fb8
SHA-1: 74865EF2562006E51D7F9333B4A8D45B7A749DAB
CRC: 068C79C6
Build Version: 7601.17514.101119-1cdn850
Release Version: 7601.17514.win7sp1_rtm.101119-1850
Digitally Signed by Microsoft Corporation: ‎Monday, ‎November ‎22, ‎2010 8:57:13 PM
Link Removed

One the most prominent features of Service Pack 1 is a new feature known as RemoteFX, more information on RemoteFX here. Service Pack 1 is completely compatible with the recent February Patch Tuesday updates.

How To Reduce Disk Space by Removing the Uninstall Files
Once Service Pack 1 is installed you may opt to remove old information regarding old hot fixes and the SP1 un-installation tool as well. Note that if you perform this step you can NEVER remove SP1! This is NOT recommended. On most systems you should expect between 500MB and 1.5GB of space recovered by running this program. To run you must launch a command prompt with Administrator privileges, then execute the following command:

dism /online /cleanup-image /spsuperseded

This command will take between 5 and 15 minutes to complete, when completed you will now have SP1 fully integrated with no un-installation option. Enjoy the reclaimed disk space!

Blocking SP1 from automatically installing
Prior to any installation, if you find that you wish to block the installation of SP1 automatically via Windows Update, please see the Link Removed. This will block the Service Pack from installing "valid for 12 months following general availability of the Service Pack".

How To Integrate or Slipstream Windows 7 Service Pack 1 (SP1) Into Installation DVD, ISO
To create an ISO or new DVD that includes Service Pack 1 as a slipstreamed (seamless) installation you can follow the tutorial here, please note that this tutorial is not an "official" method for creating a bootable SP1 installation media... however users have reported that this method works.

Additional Official Documentation (Requires Microsoft Link Removed and Link Removed Viewer):

Link Removed

Link Removed

Link Removed

Link Removed

Link Removed

Link Removed

Our Video Review of Windows 7 Service Pack 1:

​

 

[Veegertx]

Yes been nice to see MD5 but we will soon

So WinRumors was first this morning in Google search and correct. He must have friends also. Thank you.

 

[mcnaugha]

Well what do you know the leak is the RTM. Brandon LeBlanc confirmed the build number. MD5 stuff probably won't matter. I think we would have heard by now if it contained malware as some sort of fake. I'm pretty sure this is the first time the RTM has leaked well in advance of Brandon's blog.

 

[fjgold]

Well what do you know the leak is the RTM. Brandon LeBlanc confirmed the build number. MD5 stuff probably won't matter. I think we would have heard by now if it contained malware as some sort of fake. I'm pretty sure this is the first time the RTM has leaked well in advance of Brandon's blog.

Here is Brandon's blog.
Announcing Availability of Windows 7 and Windows Server 2008 R2 SP1

He confirms the build number in the comments.

Does this increase confidence level or what?
Works for me.

 

[Joe S]

It would be nice to know if the hashes match.
Joe

 

[Mike]

I would like to thank all of you who had faith in this announcement from the start, and those who had the confidence to speak their opinion, irregardless of the outcome. Debate is at the heart of all good discussion. Sadly, I became a naysayer for a few hours, of files that even I originally announced must be the RTM bits. We know now, with 100% certainty, that this build is the RTM. This confirmation has come from Microsoft. I am glad we have been able to make these files available for such a long duration of time, wherefore, a great deal of analysis and resources went into checking authenticity.

Questioning the legitimacy of these files was acceptable, and for a short time, I did a complete 180 and became concerned these weren't the files. A quick examination of how the Service Pack functioned after the February Patch Tuesday releases created confidence between the admin team that this was the RTM once again. External forces had shaped differing opinions, but it is good that at the end of the day, we stuck to our principles.

The files will remain online so that members who desire the Service Pack can use them right now. Thanks to Microsoft, for giving out the build number details and confirmation of RTM status. We are excited to be able to provide these files for those who feel they absolutely need SP1 today.

 

[fjgold]

I would like to thank all of you who had faith in this announcement from the start, and those who had the confidence to speak their opinion, irregardless of the outcome. Debate is at the heart of all good discussion. Sadly, I became a naysayer for a few hours, of files that even I originally announced must be the RTM bits. We know now, with 100% certainty, that this build is the RTM. This confirmation has come from Microsoft. I am glad we have been able to make these files available for such a long duration of time, wherefore, a great deal of analysis and resources went into checking authenticity.

Questioning the legitimacy of these files was acceptable, and for a short time, I did a complete 180 and became concerned these weren't the files. A quick examination of how the Service Pack functioned after the February Patch Tuesday releases created confidence between the admin team that this was the RTM once again. External forces had shaped differing opinions, but it is good that at the end of the day, we stuck to our principles.

The files will remain online so that members who desire the Service Pack can use them right now. Thanks to Microsoft, for giving out the build number details and confirmation of RTM status. We are excited to be able to provide these files for those who feel they absolutely need SP1 today.

You're very welcome Mike.
BTW, this thread has been very entertaining as well as being informative.

 

[Merc]

Well I appreciate having the SP1 available, even if we weren't positive it was the real SP. I installed it on four machines and then my laptop became corrupted due to a problem Roxio Creator 2011 has with IE-9 beta (Don't install IE-9 if you have Creator folks, until Roxio puts out a patch). Ended up reinstalling Win 7 and used the SP from here so I could avoid the drudgery of installing a few hundred patches. Nice to know it is the correct version, afterall but even if it wasn't, I planned on using it until the "real patch" arrived.

BTW on all 4 machines, the latest patches installed without a hitch and they were all different types of machines. AMD laptop with 32 bit, a Core 2 duo laptop with 32 bit, a Core 2 duo desktop with 32 bit and a Core 2 Quad with 64 bit.

 

[Seventy Nine]

Seems to me that Windows Media Player version 12.0.7601.17514 that comes with SP1 does not write the HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\CurrentMetadata key any more. I was using it to get the WMP track title and album art in a Rainmeter skin but the registry entry seems to have dissapeared.

Is it just me or do other people have that key and some info that gets updated in their registry?

UPDATE: Fixed it now.....seems it was my fault for not re-installing the Song Signature plugin after installing SP1!

 

[fjgold]

Seems to me that Windows Media Player version 12.0.7601.17514 that comes with SP1 does not write the HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\CurrentMetadata key any more. I was using it to get the WMP track title and album art in a Rainmeter skin but the registry entry seems to have dissapeared.

Is it just me or do other people have that key and some info that gets updated in their registry?

No HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\CurrentMetadata key here either.
Win 7 Home Premium SP1.

I also don't find the skin you mention in the list of "official" skins on the MS WMP skin site either.
Could be a bug with Rainmeter.

 

[Seventy Nine]

I also don't find the skin you mention in the list of "official" skins on the MS WMP skin site either.
Could be a bug with Rainmeter.

It was a Rainmeter skin that was I was working on and it was working just fine until I installed SP1 with the newer (?) version of WMP 12. I can't see what WMP would have used the registry key for anyway so maybe they just decided it was a waste of time having it write the currentmetadata everytime a new track or movie was played.

 

[fjgold]

It was a Rainmeter skin that was I was working on and it was working just fine until I installed SP1 with the newer (?) version of WMP 12. I can't see what WMP would have used the registry key for anyway so maybe they just decided it was a waste of time having it write the currentmetadata everytime a new track or movie was played.

Ah it's kinda like Conky in Ubuntu but developed for Windows.
Obviously the folks developing Rainmeter need to upgrade to be compatible with SP1.
Check with the Rainmeter forums.

 

[Mike]

FRAPS also seems to not work at all with Service Pack 1...

 

[fjgold]

FRAPS also seems to not work at all with Service Pack 1...

I have no use for FRAPS but installed the free version to check this.
It seems to work fine for me.

 

[Mike]

It could be an internal problem. I have tried this on several OS installations and its still not working. I have contacted their support.

 

[Mike]

I have no use for FRAPS but installed the free version to check this.
It seems to work fine for me.

What kind of video card are you using, and you have Aero enabled? After some extensive testing, here was what Josephur and I found:

"I have done further testing and it seems that the issue is the overall system hook that FRAPS uses to hook to the video source it wants to capture. If my screen contains any kind of overlay (such as a 3d game, screen saver preview window, or any other program that uses the OS's overlay function) then FRAPS attempts to use that overlay instead of the overall system overlay. I suspect that FRAPS will have to be updated to understand how 7 SP1 handles overlay. My guess is FRAPS sets a win32 API hook to capture Overlay 0, and Windows 7 has changed the Overlay to 1 (or whatever). So I suspect the issue is the new Service Pack's Direct3D stack, possibly this was changed because of the new RemoteFX features as well, as they need access to the overlay."

This information has been sent to Beepa Support for them to take a look at.

(Images of FRAPS overlay on applications, but not on appearing on the desktop itself)

This is regarding the inability to record DWM (Aero) workspace, including the entire desktop. It works fine pre-SP1

 

[fjgold]

What kind of video card are you using, and you have Aero enabled? After some extensive testing, here was what Josephur and I found:

"I have done further testing and it seems that the issue is the overall system hook that FRAPS uses to hook to the video source it wants to capture. If my screen contains any kind of overlay (such as a 3d game, screen saver preview window, or any other program that uses the OS's overlay function) then FRAPS attempts to use that overlay instead of the overall system overlay. I suspect that FRAPS will have to be updated to understand how 7 SP1 handles overlay. My guess is FRAPS sets a win32 API hook to capture Overlay 0, and Windows 7 has changed the Overlay to 1 (or whatever). So I suspect the issue is the new Service Pack's Direct3D stack, possibly this was changed because of the new RemoteFX features as well, as they need access to the overlay."

This information has been sent to Beepa Support for them to take a look at.

(Images of FRAPS overlay on applications, but not on appearing on the desktop itself)

This is regarding the inability to record DWM (Aero) workspace, including the entire desktop. It works fine pre-SP1

I'm not a gamer hence my comment about having no use for FRAPS.
As to video card it is an ATi Mobility Radeon X1400 with 128 MB builtin Vram.
This is in an Acer 5672WLMi notebook.
ATi doesn't support this card anymore so the latest drivers are dated around Feb 2009.
The drivers and the Catalyst Control Center came from Acers support site an were designed for Vista but work fine in Win 7.
I can easily run Aero but choose not to.

I guess I will try FRAPS in Aero to see if that makes a difference.

 

[Mike]

We are specifically talking about the ability to record/screenshot/FPS the entire desktop itself and not just a game. We are almost 100% positive it is SP1

 

[fjgold]

We are specifically talking about the ability to record/screenshot/FPS the entire desktop itself and not just a game. We are almost 100% positive it is SP1

I guess I don' know what you want this program to do.
For me, the free version captures video perfectly with framerates displayed, will take screenshots of a playing video again with framerates.
This in Aero.
It performs benchmarks as well, though I don't know how to read them (.csv file).
I can't get it to take a screenshot of my desktop, but my desktop is static so why would I need FRAPS to do that?

 

[Mike]

No. This is not Aero. This is DirectX. When you play a DirectX game, it has nothing to do with the Aero desktop interface. We are specifically talking about benchmarking the desktop, recording the desktop, and taking the screenshots. This is a specific piece of functionality that does not work in Windows 7 Service Pack 1.

 

[Super Sarge]

Well today is the day (Feb. 16 2011) that it will known for sure by you techie gurus whether the SP1 posted initially on Softpedia was truly the RTM everyone touted it was