Windows XP Service Pack 3 now on Windows Update Options

[Tarun]

Microsoft Windows XP Service Pack 3 started appearing on Windows Update early this morning. Windows XP Service Pack 3 covers all previously released updates. Also included will be some private hotfixes that you could only acquire through special request. There are genuinely new features - not just patches and security updates, but services that could substantially improve system security without overhauling the kernel like with Windows Vista. These new features will not significantly change customers experience with the operating system.

Windows XP SP3 Build 5512 is the final release, also known as the Release To Manufacturing (RTM) build that made it's way to TechNet, MSDN and OEMs. Service Pack 3's size for the English release is 316MB. Other language releases may vary. There are several new features that come with SP3, they are Network Access Protection (NAP), Kernel Mode Cryptographic Module (KMCM) and the hardening of the TCP/IP stack with the new "black hole router" detection.

Network Access Protection (NAP) has been added with the release of Service Pack 3. This will help System Administrators to ensure that their network is both secure and healthy. Sysadmins will be able to set policies that determine if a computer is healthy or not by meeting set system health requirements. Examples of those requirements can be having the most recent OS updates installed, having the latest version of the anti-virus software including detection definitions, or if the computer has a host-based firewall installed and enabled.

Kernel Mode Cryptographic Module (KMCM) is a FIPS 140-1 Level 1 compliant, general-purpose, software-based, cryptographic module residing at the Kernel Mode level of the Windows Operating System. It runs as a kernel mode export driver (a kernel-mode DLL) and encapsulates several different cryptographic algorithms in an easy-to-use cryptographic module accessible by other kernel mode drivers. It can be linked into other kernel mode services to permit the use of FIPS 140-1 Level 1 compliant cryptography. It premiered in Windows 2000, and its first implementation in a Windows client was for the first edition of Vista.

Microsoft is also hardening the Windows IP stack. With this addition comes Microsoft's new "black hole router" detection. Black hole router detection is a way for routers to detect in advance the shortest path to send a large number of datagrams, without having to fragment them too seriously along the way. As it turned out, some receiving routers that were pegged by sending ones as PMTU members were responding to datagrams with "do not fragment" messages by simply throwing them out. These were referred to as "black hole routers," and have been a perennial plague to streaming operations. The new router detection scheme enables IP routers along the way to flag misbehaving PMTU candidates in advance and steer around them.

Downloads: Windows XP SP3 English | Windows XP SP3 German | Windows XP SP3 Russian | Windows XP SP3 Spanish | Windows XP SP3 Polish | Windows XP SP3 French | Windows XP SP3 Chinese
Link: Windows Update
Source: Lunarsoft

[Hardhead]

Microsoft is delaying the release of Service Pack 3 for Windows XP users due to a "compatibility issue" with the bundle of updates and a supply-chain solution the company markets to small- and medium-sized businesses. The software giant had previously said SP3 would be released to XP customers today via Windows Update and its software download center.

In a written statement, Microsoft said:

"In order to make sure customers have the best possible experience we have decided to delay releasing Windows XP SP3 to Windows Update and Microsoft Download Center.

http://blog.washingtonpost.com/securityfix...ml?nav=rss_blog

[DaChew]

I just wonder how many builds we will see?

I have seen 2 already, both from microsoft

[Tarun]

http://blog.washingtonpost.com/securityfix...ml?nav=rss_blog

That's only for users of Microsoft Dynamic RMS.

I just wonder how many builds we will see?

I have seen 2 already, both from microsoft

Build 5512 is RTM/Final

[DaChew]

That's only for users of Microsoft Dynamic RMS.


Build 5512 is RTM/Final

http://download.microsoft.com/download/5/3...SP3-x86-enu.exe

http://download.windowsupdate.com/msdownlo...e2300ebfde4.exe

2 different links with slightly different file sizes

[AdvancedSetup]

Well we use Dynamics and CRM - not RMS but don't need to take the chances of messing up my desktop computers.
We can wait...

As for that being the final RTM well it won't be as it "should" get a new incremental build number when the fix for RMS is completed.

[DaChew]

Well there's been an XP SP2b and then an XP SP2c

at least they finally, sort of released SP3, after what a year or two delay?

[Tarun]

The build numbers won't change from what I've heard. There's no reason to for a minor fix. There will be a hotfix before you can get SP3 (and I'm not sure but I believe it's only if you have Microsoft Dynamic RMS) and if you've already installed SP3 there will be one after. It might post in the next few days.

[AdvancedSetup]

The build numbers won't change from what I've heard. There's no reason to for a minor fix. There will be a hotfix before you can get SP3 (and I'm not sure but I believe it's only if you have Microsoft Dynamic RMS) and if you've already installed SP3 there will be one after. It might post in the next few days.

If they follow your scenario I agree no change needed. But if they change 1 bit in the code it should have a new number to reflect that in my opinion. Almost a pet peeve when programmers don't change the build numbers for minor things.

[Tarun]

It's been re-released onto Windows Update. The build number is still 5512, as said.

[AdvancedSetup]

It's been re-released onto Windows Update. The build number is still 5512, as said.

Thanks - just need to see how they implemented the fix for the Dynamics stuff.
If integrated and no build number change then as I said not good.
In my opinion this version should be an MD5 match and if it's not then it should have a new build number.

[Tarun]

A small hotfix change isn't going to change the build number. A revision to a core binary, maybe so. But a hotfix for ActiveX Data Objects (ADO) that isn't even in the service pack? No way.

FYI: MD5 is the same.

[Hardhead]

Its available on WU and I just finished installing SP3.

If I have any problems I will post back.

[DaChew]

ServicePackFiles

564MB

$NtServicePackUninstall$

some weird sizes reported

overall windows grows a gig

Wednesday, April 23, 2008, 5:40:24 PM

gone very good

[Hardhead]

Its hosed Windows Live Messenger but repaired it with no problems.
Also heres a little info from WinPatrol.

 Livem2.GIF ( 23.37K ) Number of downloads: 83


 Wp1.GIF ( 9.07K ) Number of downloads: 84


 Ax2.GIF ( 27.89K ) Number of downloads: 86


No problems here.

[Hardhead]

Typical download size: 66.9 MB , 28 minutes
Windows XP Service Pack 3 (SP3) is an update to Windows XP that addresses key feedback from our customers and is a cumulative update that includes all previously released updates for Windows XP, including security updates. Windows XP SP3 contains a small number of new updates and should not significantly change the Windows XP experience. After you install this item, you may have to restart your computer.

Details...

Available through Windows Update

[AdvancedSetup]

A small hotfix change isn't going to change the build number. A revision to a core binary, maybe so. But a hotfix for ActiveX Data Objects (ADO) that isn't even in the service pack? No way.

FYI: MD5 is the same.

Agreed that if some other method or file is used to correct the issue then that's fine, but if the main SP3 file changes by just a single bit then it's plain poor management control not to change the build number. Every build should be documented and incremented in my opinion.

[AdvancedSetup]

Microsoft warns of IE7 lock-in with XP SP3

Users can't revert to IE6 after updating