Windows Vista SP1 Detailed Changes (Changelog)

Setup and Deployment Improvements

  • Enables global organizations to more easily deploy SP1 in a multi-lingual environment, as SP1 includes all 36 language packs. However, this change contributes to the increased size of the standalone package.
  • Enables users to get updated Help content via a separate downloadable package. This package will be released around SP1 release.
  • Enables support for hotpatching, a reboot-reduction servicing technology designed to maximize uptime. It works by allowing Windows components to be updated (or “patched”) while they are still in use by a running process. Hotpatch-enabled update packages are installed via the same methods as traditional update packages, and will not trigger a system reboot.
  • Improves migration and upgrade scenarios relating to the component that allows alternate text input “modalities” like speech, handwriting, and multi-byte character input editors in applications that were not written specifically to support them.
  • Improves OS deployment by enabling 64-bit versions of Windows Vista to be installed from a 32-bit OS. This will allow IT professionals to maintain just a single WinPE image.
  • Improves OS deployment by supporting the installation of offline boot critical storage drivers. WinPE will automatically look to a hidden partition for drivers. It will search that partition recursively, and if boot critical drivers are present they will be loaded. Non-boot critical drivers will be picked up and staged, but not loaded prior to the OS coming online.
  • Improves patch deployment by retrying failed updates in cases where multiple updates are pending and the failure of one update causes other updates to fail as well.
  • Enables reliable OS installation by optimizing OS installers so that they are run only when required during patch installation. Fewer installers operating results in fewer points of potential failure during installation, which leads to more robust and reliable installation.
  • Improves overall install time for updates by optimizing the query for installed OS updates.
  • Improves robustness during the patch installation by being resilient to transient errors such as sharing violations or access violations.
  • Improves robustness of transient failures during the disk cleanup of old OS files after install.
  • Improves the uninstallation experience for OS updates by improving the uninstallation routines in custom OS installation code.
  • Improves reliability of OS updates by making them more resilient to unexpected interruptions, such as power failure.
  • Improved instrumentation allows additional data to be sent to Microsoft via the CEIP (Customer Experience Improvement Program) when enabled. This telemetry data led to the identification of numerous issues that are addressed in SP1 and resulted in improvement in the reliability of OS servicing. (CEIP is respectful of personally identifiable information and adheres to terms discussed in the EULA.)
  • After the SP1 version of the OPK (OEM pre-installation kit) is installed, further OPK updates will not be required if a servicing stack update is issued. (The servicing stack is the underlying set of binaries used to update the system). Post SP1, offline images may be updated using the servicing stack binaries contained in the image rather than the servicing stack binaries in the OPK.

Interoperability Improvements

  • SP1 exposes Ideal Send Backlog (ISB) information to Winsock2 clients to enable better throughput over high bandwidth, high latency links when communicating with Windows Server 2008. Applications that are modified to use the new ISB info will provide better throughput when sending large amounts of data over such links to other Windows Vista or Windows Server 2008 machines. Applications not modified to take advantage of this change will function as before.
  • SP1 includes throughput improvements to Send in TransmitFile/TransmitPackets and ftp.exe, when communicating with Windows Server 2008 over high bandwidth, high latency links. Ftp.exe and other applications using TransmitFile/TransmitPackets on Windows Vista SP1 will achieve better throughput when sending files over such links to other Windows Vista or Windows Server 2008 machines.

Feature or API Changes

  • GPMC (Group Policy Management Console) will be uninstalled with Service Pack 1 and GPEdit will default to Local Group Policy editing. Following these changes, SP1 users can download an updated version of GPMC which will include new Group Policy capabilities including adding comments to GPOs or individual settings and searching for specific Group Policy settings.
  • The MSN Connection Center Dial-up Internet Access connector was removed from the Windows Vista Connection Wizard.
  • Includes a new Offline Files interface that exports the dirty byte count for a file that is modified offline. This interface is exposed both through the COM APIs and WMI provider for Offline Files.

General Improvements and Enhancements

  • SP1 includes a number of changes which allow computer manufacturers and consumers to select a default desktop search program similar to the way they currently select defaults for third-party web browsers and media players. That means that in addition to the numerous ways a user could access a third party search solution in Windows Vista, they can now get to their preferred search results from additional entry points in the Start Menu and Explorer Windows in Windows Vista with SP1. 3rd party software vendors simply need to register their search application using the newly provided protocol in Windows Vista SP1 to enable these options for their customers.
  • With SP1, Windows Vista will report the amount of system memory installed rather than report the amount of system memory available to the OS. Therefore 32-bit systems equipped with 4GB of RAM will report all 4BG in many places throughout the OS, such as the System Control Panel. However, this behavior is dependent on having a compatible BIOS, so not all users may notice this change.
  • SP1 reduces the number of UAC (User Account Control) prompts from 4 to 1 when creating or renaming a folder at a protected location.
  • Improvements in the Licensing User Interface and User Experience including more details in the help about activation and what happens if user does not activate; more detailed and descriptive dialog text; raw error codes replaced with easily comprehensible text.
  • SP1 modifies the text in the Ultimate Extras Control Panel to describe the Ultimate Extras program in more general terms.
  • Upon scanning a photo with the Vista scanning experience, SP1 will open Explorer rather than opening Windows Photo Gallery.
  • Users are now required to enter a password hint during the initial setup of Windows Vista SP1. This change was made based on feedback from top PC manufactures that many customers frequently do not remember their password and because the administrator account is turned off by default on Windows Vista, these users do not have a way to access to their PCs. A password hint helps avoid this frustrating scenario.
  • Improves compatibility with 3rd party diagnostic tools that rely on raw sockets by applying the same delivery logic to control (ICMP v4 and v6) and regular packages.
  • While not reflected in the initial release candidate this week, we will also be making changes effective with SP1 in how we differentiate the experience customers have using non-genuine versions of our software. This is based on feedback we heard from volume license customers in particular as part of our Windows Genuine Advantage program.
  • Also coming with SP1 but not in the current release candidate, we will also be including updates that deal with two exploits we have seen, which can affect system stability for our customers. The OEM Bios exploit, which involves modifying system files and the BIOS of the motherboard to mimic a type of product activation performed on copies of Windows that are pre-installed by OEMs in the factory. The Grace Timer exploit, which attempts to reset the “grace time” limit between installation and activation to something like the year 2099 in some cases.

Windows Vista Alignment with Windows Server 2008

Windows Vista is aligned with Windows Server 2008, meaning that many files are common to both products. A result of this design is that there are cases where a common binary is modified to enable a server scenario that has limited or no effect on Windows Vista SP1 capabilities. Here are few examples:

  • File Sharing: The file sharing subsystem on Windows Vista only allows 10 concurrent inbound connections. Windows Server 2008 must scale to support thousands of concurrent connections. During the testing and customer feedback phase of Windows Server 2008 development, the file sharing subsystems are tuned and refined to optimize the file sharing stack for performance, scalability and reliability. This level of tuning and refinement are not typically applicable on a 10-connection limit client, but are critical to a file server role. Changes like this are done primarily for the server scenarios, although these changes may also benefit Windows Vista SP1.
  • IIS 7: IIS was included in some Windows Vista SKUs to enable web-based developers to write and test their applications. IIS in Windows Server 2008 is a significant server role which requires Internet-level scalability and performance requirements. The IIS7 components have gone through significant performance and reliability enhancements since Windows Vista originally shipped, in order to be a large-scale server component. These changes do not affect most Windows Vista users who do not even have the IIS7 components installed, however because Windows Vista and Windows Server are aligned, these changes are included in Windows Vista SP1.
  • Concurrent User Support: Key subsystems such as the Windows Logon process and the core kernel need only support user-switching scenarios on Windows Vista. However, on Windows Server 2008, where a Terminal Server may have thousands of users logged in simultaneously, these subsystems must be tuned for maximum performance and reliability. Changes like this are done primarily for the server scenarios, although they may also benefit Windows Vista SP1.

Pages: 1 2 3

5 Responses to “Windows Vista SP1 Detailed Changes (Changelog)”

  1. phone
    December 20th, 2008 23:43
    5

    hmdr

  2. basketball court plan view
    December 12th, 2008 10:28
    4

    ktfgr rlxvbwe hwnij gelsu

  3. non adjustable basketball hoop
    December 12th, 2008 09:53
    3

    nhbzusm

  4. basketball overseas
    December 12th, 2008 09:10
    2

    gnbj tbns

  5. Windows Vista Service Pack 1 Release Notes » My Digital Life
    March 19th, 2008 02:47
    1

    [...] For an overview of significant changes and improvements in this release candidate of SP1, see http://go.microsoft.com/fwlink/?LinkID=107921. [...]

Leave a Reply

You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Subscribe to comments feature has been disabled. To receive notification of latest comments posted, subscribe to My Digital Life Comments RSS feed or register to receive new comments in daily email digest.

New Articles

Incoming Search Terms for the Article

wsc helper tool - belkin cable Not enough storage is available to process this command - windows setup could not configure windows to run on this computer's hardware - WSC helper tool stopped working and was closed - what is wsc helper tool - notes smart upgrade error 8 - not enough storage is avaiable to process this command - not enough storage to process this command vista - wsc helper responding - wsc helper tools vista - microsoft management console has stopped working - windows vista's windows setup could not configure windows to run on this computer's hardware - "virtual patch protection system stopped" - 64 msdasql not enough storage - msdasql 64 not enough storage - not enough storage is available to complete this operation vista - kms server 2008 not enough storage is available to process this command - vista wsc helper tool - kms "not enough storage to process this command" - "concurrent user" "windows server 2008" - how windows vista changes lives - iis management console - vista "windows setup could not configure windows to run on this computers hardware" - windows genuine advantage not enough memory bitmap - "windows setup could not configure windows to run on this computer's hardware" - what is wsc helper - "windows setup could not install one or more boot-critical drivers - system change log windows vista - adobe bridge "not enough storage is available to complete this operation" - vista sp1 loader x32 - vista not enough storage to process command - windows 7: NetworkThrottlingIndex - not enough storage is available to process this command vista codec - not enough storage is available process this "command windows 7" - Powerdirector 8 "Not Enough Storage" - msdasql 64 bit 2008 missing - kms not enough storage - photo scanning - "wsc helper tool stopped" - "Windows Setup could not install one or more boot-critical drivers" - how to download wsc helper tool for vista - not enough storage ScreenSaver - wsc helper tool has stopped working -