PATCHER OF INSECURE SOFTWARE Microsoft has announced that Windows 7 Service Pack 1 (SP1) has hit the release to manufacturing (RTM) stage.
The Vole says its Windows Volume Licensing customers will be able to get their hands on Windows 7 SP1 and Windows Server 2008 R2 on 16 February, while users will see it through Windows Update from 22 February.
Microsoft has always said that Windows 7 SP1 would be little more than an aggregation of security patches and various updates, and senior technical product manager Michael Kleef barely mentioning Windows 7 SP1 in the announcement. Instead, Kleef talked about the two new features in Windows Server 2008 R2, Dynamic Memory and RemoteFX.
Both Dynamic Memory and RemoteFX focus on server virtualisation, however RemoteFX can virtualise GPUs, which allows users to divvy up the hundreds of cores found in high-end GPUs to particular virtual machines. Kleef claims the software will "deliver next-generation rich media and 3D user experiences".
The Vole has played down the importance of Windows 7 SP1 in an attempt to entice customers to buy Windows 7 sooner rather than later. For businesses, the release of SP1 has traditionally been the maturity milestone that triggers upgrades, however Microsoft has hoped that by keeping Windows 7 SP1 a low-key affair, it could encourage customers to jump onto its latest product sooner.
That strategy has had only limited success, so it will be interesting to see whether the slow take-up of Windows 7 improves once SP1 is out. µ
Tags: Microsoft
It is already available in form of an ISO image with standalone SP1 for x86, x64 and Itanic as well as an ISO image with full OS install with SP1 integrated.
Just visit your favorite torrent search engine.
Microsoft will always say Windows 7 has had limited success until they can crack the business market.
They can easily push home sales by enforcing resellers to push the latest products and by giving the older products their de-listing dates.
The problem is a service pack now-a-days just isn't going to make a business stand up and think 'yeah I need to upgrade all my XP/2000 machines to 7'...
MS need to give businesses something to want 7 rather than hoping a service pack will show the product has matured.
There's no doubt that 7 as a product beats the Vista era hand's down but nobody is going to just upgrade for the sake of it.....
Don't tell the boss but I'm reading this at workson Microsoft Windows XP, so yes.
What they do is, if you want a new Windows XP licence currently, you have to be a business and then to buy Windows 7 but be allowed to install Windows XP instead. Also available to businesses is Windows XP installed -inside- Windows 7, so that your XP stuff still runs.
As for the service pack - (1) apparently they're -talking- about the update release which you haven't seen before.
But on a Windows 7 system already fully patched, will it do anything at all? When you try to download it, will it inspect your disk, shrug, and say - correctly - "My work is done"?
Typical anti-MS article. And as typical also are the errors in it.
"That strategy has had only limited success, so it will be interesting to see whether the slow take-up of Windows 7 improves once SP1 is out."
Win7 is fastest selling OS in the history.
So how is that "limited success"...?
SP1 is actually quite old, all things considered. The actual SP1 build is from mid November, by the time it is released it will literally be 3 months old. It also has its faults too, a common one seems to be that if you install SP1 on top of an existing copy, regardless of how the original was updated, there's a couple of files that aren't updated like they should be. The issue affects USB system drivers, such as USBport.sys. The new version exists in the system repository, but isn't updated to the system32\drivers folder. On a fresh SP1 installation, the error doesn't exist as the RTM version of this fil (and other affected files) don't exist, yet device manager driver details tab will still show that the file version is the RTM version, even if its the SP1 version that is used and being checked!
Its a bug that will probably be easily fixed with an update, but still it shouldn't exist.