Mike

Windows Forum Admin
Staff member
Premium Supporter
Joined
Jul 22, 2005
Messages
9,139
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:

 
Last edited:
Anybody else try slipstreaming this? I used the RTseven lite and it faults out. It integrated the individual updates OK.
Joe
 
Anybody else try slipstreaming this? I used the RTseven lite and it faults out. It integrated the individual updates OK.
Joe
It worked for me. I used RT7 and just followed the directions at the link provided by fjgold in post #29. It took about an hour and a half and it heated my processor up higher than I've ever seen it. But it will boot and my system lived through it just fine.
 

Dude, my point was that Microsoft don't hide the fact when something goes RTM. The Russian Microsoft employee that said it had gone to OEM's subsequently updated saying that it has not gone RTM. If it had then the US team's blog(s) would acknowledge it within 24hrs as they normally do. Yes there's a delay with the official marketing sites, etc. but not on the employee blogs. It's never longer than 24-48 hrs when we hear it has gone RTM. That didn't happen with this build and they have officially said it is not the RTM.

My worry is the poor innocents installing this when it's still essentially an RC and not the RTM. People can get excited about another RC if they like, but what about the people who believe this is the RTM?

Here is the original blog which started this off and you'll see it now includes an official statement updating the situation:

http://blogs.technet.com/b/vm/archi...-pack-1-windows-7-windows-server-2008-r2.aspx

Sites like Link Removed will also confirm it when it really has gone RTM.
 

Yeah, I forgot to mention that it is very processor intensive.
My Core2Duo got to about 180 F.
Intel says max is 212 F.
I run a tray app that reports core temp in realtime.
 

This isn't an RC They promised there will only be 1 RC and be RTM in the 1st Q1 of this year, That means either January or Febuary of this year. SP1 has already gone to OEM's so it'll come through Windows up date at the end of the month or Feb's patch tuesday, If it doesn't well there's something wrong. I installed it lake many people and as I said that this version, when, installed there is no watermark/s or Time bombs/Stamps. evaluations. this is 100% working full version (Not a test/beta/RC) If it was it would have the watermark and a time bomb. We here have 80% chance this is it, Personally if it turns out not to be the RTM, I would be wondering what it could be. baring in mind this is digitaly signed by MS, and all other factors said alredy
 
Well Nero 8 consistently reports "power calibration" in SP1.
I haven't tried reinstalling Nero yet mainly because Nero makes it such a PITA.

I'm posting from the pre SP1 image and can report no burn issues with the pre SP1 Win 7.
I'm reasonably sure that Nero 8 isn't playing well with SP1.
It is likely Nero's fault and will need a fix by them.
I could pay for an upgrade to the latest Nero I suppose.

I will try uninstalling and reinstalling first.
 
Stuey
I got it. I was running in VMware and only had about 10 G free space I deleted some junk an had about 15G clear and it ran fine. Apparently it needs alot more free space than I thought.
Joe
 


Generally Q1 refers to the financial year making it April onwards
 
I ununstalled and reinstalled Nero 8 a couple of times.

Still issues "power calibration" error though not always.
I think it's just crappy media.
 
I ununstalled and reinstalled Nero 8 a couple of times.

Still issues "power calibration" error though not always.
I think it's just crappy media.

Sorry to hear you have problems with nero and sp1

Use imageburn, its simpler, works with sp1(tested) and best of all it's free

Goodluck.
 

Fantastic.

Thanks Mike.
 
I gave up on Nero a few years back. I really like ImgBurn.

The Official ImgBurn Website
 
Be patient. The process is both time consuming and processor intensive.
Expect at least an hour to complete.
Yep. Mine took over an hour and the processor temp was sometimes in the high 160's. It usually runs in the 110's and 120's.
 
I gave up on Nero a few years back. I really like ImgBurn.

The Official ImgBurn Website
Just tried ImageBurn. cool.
No coasters.
What sucks is the fact that I have money tied up in Nero.
When I install it all I ever install is the burning software part.
The rest of the stuff in the bloated product is crap.
I even paid a little for a Nero Linux 4 license.

Installing is a PITA and they don't even include help files.
You have to D\L those separately.
Nero says thats to keep the program D\L small, like an additional 5 MB will make a difference.

ImageBurn seems to be pretty simple and easy to use.
 
Yeah the guides under the help menu are well written. Also any coasters I burn are because of media problems. I just finished a package of Verbatim DVD+r disks that refused to burn on my laptop. They worked on my old desktop though. Now I'm using Verbatim DVD-r's that burn great. Sometimes burners and media just don't mix.