Windows Vista theme by NaViTo
Download: Vista_NaViTo.p3t
(3 backgrounds)
Version of the Windows NT operating system | |
Developer | Microsoft |
---|---|
Source model | |
Released to manufacturing | November 8, 2006[2] |
General availability | January 30, 2007[3] |
Final release | Service Pack 2[4] (6.0.6002.24170) / July 21, 2017[5] |
Marketing target | Consumer and Business |
Update method | |
Platforms | IA-32 and x86-64 |
Kernel type | Hybrid (NT) |
Userland | Windows API, NTVDM, SUA |
License | Proprietary commercial software |
Preceded by | Windows XP (2001) |
Succeeded by | Windows 7 (2009) |
Official website | Windows Vista (archived at the Wayback Machine) |
Support status | |
Mainstream support ended on April 10, 2012[6] Extended support ended on April 11, 2017[6] |
Part of a series of articles on |
Windows Vista |
---|
New features |
Siblings |
Windows Vista is a major release of the Windows NT operating system developed by Microsoft. It was the direct successor to Windows XP, released five years earlier, which was then the longest time span between successive releases of Microsoft Windows. It was released to manufacturing on November 8, 2006, and over the following two months, it was released in stages to business customers, original equipment manufacturers (OEMs), and retail channels. On January 30, 2007, it was released internationally and was made available for purchase and download from the Windows Marketplace; it is the first release of Windows to be made available through a digital distribution platform.[7]
Development of Windows Vista began in 2001 when it was codenamed "Longhorn"; originally envisioned as a minor successor to Windows XP, it gradually included numerous new features from the then-next major release of Windows codenamed "Blackcomb", after which it was repositioned as a major release of Windows, and it consequently underwent a protracted development that was unprecedented for Microsoft. Most new features were prominently based on a new presentation layer codenamed Avalon, a new communications architecture codenamed Indigo, and a relational storage platform codenamed WinFS — all built on the premature .NET Framework; however, this proved to be untenable due to incompleteness of technologies and ways in which new features were added, and Microsoft changed the project in 2004. Many new features were eventually reimplemented during development, but Microsoft ceased using managed code to develop the operating system.[8]
New features of Windows Vista include a graphical user interface and visual style referred to as Windows Aero; a content index and desktop search platform called Windows Search; new peer-to-peer technologies to simplify sharing files and media between computers and devices on a home network; and new multimedia tools such as Windows DVD Maker. Windows Vista included version 3.0 of the .NET Framework, allowing software developers to write applications without traditional Windows APIs. There are major architectural overhauls to audio, display, network, and print sub-systems; deployment, installation, servicing, and startup procedures are also revised. It is the first release of Windows built on Microsoft's Trustworthy Computing initiative and emphasized security with the introduction of many new security and safety features such as BitLocker and User Account Control.
The ambitiousness and scope of these changes, and the abundance of new features earned positive reviews, but Windows Vista was the subject of frequent negative press and significant criticism. Criticism of Windows Vista focused on driver, peripheral, and program incompatibility; digital rights management; excessive authorization from the new User Account Control; inordinately high system requirements when contrasted with Windows XP; its protracted development; longer boot time; and more restrictive product licensing. Windows Vista deployment and satisfaction rates were consequently lower than those of Windows XP, and it is considered a market failure;[9][10] however, its use surpassed Microsoft's pre-launch two-year-out expectations of achieving 200 million users[11] (with an estimated 330 million users by 2009).[12] On October 22, 2010, Microsoft ceased retail distribution of Windows Vista; OEM supply ceased a year later.[13] Windows Vista was succeeded by Windows 7 in 2009.
Mainstream support for Windows Vista ended on April 10, 2012 and extended support ended on April 11, 2017.[6]
Development[edit]
Microsoft began work on Windows Vista, known at the time by its codename "Longhorn", in May 2001,[14] five months before the release of Windows XP. It was originally expected to ship in October 2003 as a minor step between Windows XP and "Blackcomb", which was planned to be the company's next major operating system release. Gradually, "Longhorn" assimilated many of the important new features and technologies slated for Blackcomb, resulting in the release date being pushed back several times in three years. In some builds of Longhorn, their license agreement said "For the Microsoft product codenamed 'Whistler'". Many of Microsoft's developers were also re-tasked to build updates to Windows XP and Windows Server 2003 to strengthen security. Faced with ongoing delays and concerns about feature creep, Microsoft announced on August 27, 2004, that it had revised its plans. For this reason, Longhorn was reset to start work on componentizing the Windows Server 2003 Service Pack 1 codebase, and over time re-incorporating the features that would be intended for an actual operating system release. However, some previously announced features such as WinFS were dropped or postponed, and a new software development methodology called the Security Development Lifecycle was incorporated to address concerns with the security of the Windows codebase, which is programmed in C, C++ and assembly. Longhorn became known as Vista in 2005. Vista in Spanish means view.[15][16]
Longhorn[edit]
The early development stages of Longhorn were generally characterized by incremental improvements and updates to Windows XP. During this period, Microsoft was fairly quiet about what was being worked on, as their marketing and public relations efforts were more strongly focused on Windows XP, and Windows Server 2003, which was released in April 2003. Occasional builds of Longhorn were leaked onto popular file sharing networks such as IRC, BitTorrent, eDonkey and various newsgroups, and so most of what is known about builds before the first sanctioned development release of Longhorn in May 2003 is derived from these builds.
After several months of relatively little news or activity from Microsoft with Longhorn, Microsoft released Build 4008, which had made an appearance on the Internet around February 28, 2003.[17] It was also privately handed out to a select group of software developers. As an evolutionary release over build 3683, it contained several small improvements, including a modified blue "Plex" theme and a new, simplified Windows Image-based installer that operates in graphical mode from the outset, and completed an install of the operating system in approximately one third the time of Windows XP on the same hardware. An optional "new taskbar" was introduced that was thinner than the previous build and displayed the time differently. The most notable visual and functional difference, however, came with Windows Explorer. The incorporation of the Plex theme made blue the dominant color of the entire application. The Windows XP-style task pane was almost completely replaced with a large horizontal pane that appeared under the toolbars. A new search interface allowed for filtering of results, searching for Windows help, and natural-language queries that would be used to integrate with WinFS. The animated search characters were also removed. The "view modes" were also replaced with a single slider that would resize the icons in real-time, in the list, thumbnail, or details mode, depending on where the slider was. File metadata was also made more visible and more easily editable, with more active encouragement to fill out missing pieces of information. Also of note was the conversion of Windows Explorer to being a .NET application.
Most builds of Longhorn and Vista were identified by a label that was always displayed in the bottom-right corner of the desktop. A typical build label would look like "Longhorn Build 3683.Lab06_N.020923-1821". Higher build numbers did not automatically mean that the latest features from every development team at Microsoft was included. Typically, a team working on a certain feature or subsystem would generate their working builds which developers would test with, and when the code was deemed stable, all the changes would be incorporated back into the main development tree at once. At Microsoft, several "Build labs" exist where the compilation of the entirety of Windows can be performed by a team. The name of the lab in which any given build originated is shown as part of the build label, and the date and time of the build follow that. Some builds (such as Beta 1 and Beta 2) only display the build label in the version information dialog (Winver). The icons used in these builds are from Windows XP.
At the Windows Hardware Engineering Conference (WinHEC) in May 2003, Microsoft gave their first public demonstrations of the new Desktop Window Manager and Aero. The demonstrations were done on a revised build 4015 which was never released. Several sessions for developers and hardware engineers at the conference focused on these new features, as well as the Next-Generation Secure Computing Base (previously known as "Palladium"), which at the time was Microsoft's proposed solution for creating a secure computing environment whereby any given component of the system could be deemed "trusted". Also at this conference, Microsoft reiterated their roadmap for delivering Longhorn, pointing to an "early 2005" release date.[18]
Development reset[edit]
By 2004, it had become obvious to the Windows team at Microsoft that they were losing sight of what needed to be done to complete the next version of Windows and ship it to customers. Internally, some Microsoft employees were describing the Longhorn project as "another Cairo" or "Cairo.NET", referring to the Cairo development project that the company embarked on through the first half of the 1990s, which never resulted in a shipping operating system (though nearly all the technologies developed in that time did end up in Windows 95 and Windows NT[19]). Microsoft was shocked in 2005 by Apple's release of Mac OS X Tiger. It offered only a limited subset of features planned for Longhorn, in particular fast file searching and integrated graphics and sound processing, but appeared to have impressive reliability and performance compared to contemporary Longhorn builds.[20] Most Longhorn builds had major Windows Explorer system leaks which prevented the OS from performing well, and added more confusion to the development teams in later builds with more and more code being developed which failed to reach stability.
In a September 23, 2005 front-page article in The Wall Street Journal,[21] Microsoft co-president Jim Allchin, who had overall responsibility for the development and delivery of Windows, explained how development of Longhorn had been "crashing into the ground" due in large part to the haphazard methods by which features were introduced and integrated into the core of the operating system, without a clear focus on an end-product. Allchin went on to explain how in December 2003, he enlisted the help of two other senior executives, Brian Valentine and Amitabh Srivastava, the former being experienced with shipping software at Microsoft, most notably Windows Server 2003,[22] and the latter having spent his career at Microsoft researching and developing methods of producing high-quality testing systems.[23] Srivastava employed a team of core architects to visually map out the entirety of the Windows operating system, and to proactively work towards a development process that would enforce high levels of code quality, reduce interdependencies between components, and in general, "not make things worse with Vista".[24] Since Microsoft decided that Longhorn needed to be further componentized, work started on builds (known as the Omega-13 builds, named after a time travel device in the film Galaxy Quest[25]) that would componentize existing Windows Server 2003 source code, and over time add back functionality as development progressed. Future Longhorn builds would start from Windows Server 2003 Service Pack 1 and continue from there.
This change, announced internally to Microsoft employees on August 26, 2004, began in earnest in September, though it would take several more months before the new development process and build methodology would be used by all of the development teams. A number of complaints came from individual developers, and Bill Gates himself, that the new development process was going to be prohibitively difficult to work within.
As Windows Vista[edit]
By approximately November 2004, the company had considered several names for the final release, ranging from simple to fanciful and inventive. In the end, Microsoft chose Windows Vista as confirmed on July 22, 2005, believing it to be a "wonderful intersection of what the product really does, what Windows stands for, and what resonates with customers, and their needs". Group Project Manager Greg Sullivan told Paul Thurrott "You want the PC to adapt to you and help you cut through the clutter to focus on what's important to you. That's what Windows Vista is all about: "bringing clarity to your world" (a reference to the three marketing points of Vista—Clear, Connected, Confident), so you can focus on what matters to you".[26] Microsoft co-president Jim Allchin also loved the name, saying that "Vista creates the right imagery for the new product capabilities and inspires the imagination with all the possibilities of what can be done with Windows—making people's passions come alive."[27]
After Longhorn was named Windows Vista in July 2005, an unprecedented beta-test program was started, involving hundreds of thousands of volunteers and companies. In September of that year, Microsoft started releasing regular Community Technology Previews (CTP) to beta testers from July 2005 to February 2006. The first of these was distributed at the 2005 Microsoft Professional Developers Conference, and was subsequently released to beta testers and Microsoft Developer Network subscribers. The builds that followed incorporated most of the planned features for the final product, as well as a number of changes to the user interface, based largely on feedback from beta testers. Windows Vista was deemed feature-complete with the release of the "February CTP", released on February 22, 2006, and much of the remainder of the work between that build and the final release of the product focused on stability, performance, application and driver compatibility, and documentation. Beta 2, released in late May, was the first build to be made available to the general public through Microsoft's Customer Preview Program. It was downloaded over 5 million times. Two release candidates followed in September and October, both of which were made available to a large number of users.[28]
At the Intel Developer Forum on March 9, 2006, Microsoft announced a change in their plans to support EFI in Windows Vista. The UEFI 2.0 specification (which replaced EFI 1.10) was not completed until early 2006, and at the time of Microsoft's announcement, no firmware manufacturers had completed a production implementation which could be used for testing. As a result, the decision was made to postpone the introduction of UEFI support to Windows; support for UEFI on 64-bit platforms was postponed until Vista Service Pack 1 and Windows Server 2008 and 32-bit UEFI would not be supported, as Microsoft did not expect many such systems to be built because the market was quickly moving to 64-bit processors.[29][30]
While Microsoft had originally hoped to have the consumer versions of the operating system available worldwide in time for the 2006 holiday shopping season, it announced in March 2006 that the release date would be pushed back to January 2007 in order to give the company—and the hardware and software companies that Microsoft depends on for providing device drivers—additional time to prepare. Because a release to manufacturing (RTM) build is the final version of code shipped to retailers and other distributors, the purpose of a pre-RTM build is to eliminate any last "show-stopper" bugs that may prevent the code from responsibly being shipped to customers, as well as anything else that consumers may find troublesome. Thus, it is unlikely that any major new features would be introduced; instead, work would focus on Vista's fit and finish. In just a few days, developers had managed to drop Vista's bug count from over 2470 on September 22 to just over 1400 by the time RC2 shipped in early October. However, they still had a way to go before Vista was ready to RTM. Microsoft's internal processes required Vista's bug count to drop to 500 or fewer before the product could go into escrow for RTM.[31] For most of the pre-RTM builds, only 32-bit editions were released.
On June 14, 2006, Windows developer Philip Su posted a blog entry which decried the development process of Windows Vista, stating that "The code is way too complicated, and that the pace of coding has been tremendously slowed down by overbearing process."[32] The same post also described Windows Vista as having approximately 50 million lines of code, with about 2,000 developers working on the product. During a demonstration of the speech recognition feature new to Windows Vista at Microsoft's Financial Analyst Meeting on July 27, 2006, the software recognized the phrase "Dear mom" as "Dear aunt". After several failed attempts to correct the error, the sentence eventually became "Dear aunt, let's set so double the killer delete select all".[33] A developer with Vista's speech recognition team later explained that there was a bug with the build of Vista that was causing the microphone gain level to be set very high, resulting in the audio being received by the speech recognition software being "incredibly distorted".[34]
Windows Vista build 5824 (October 17, 2006) was supposed to be the RTM release, but a bug, where the OOBE hangs at the start of the WinSAT Assessment (if upgraded from Windows XP), requiring the user to terminate msoobe.exe by pressing Shift+F10 to open Command Prompt using either command-line tools or Task Manager prevented this, damaging development and lowering the chance that it would hit its January 2007 deadline.[35]
Development of Windows Vista came to an end when Microsoft announced that it had been finalized on November 8, 2006, and was concluded by co-president of Windows development, Jim Allchin.[36] The RTM's build number had also jumped to 6000 to reflect Vista's internal version number, NT 6.0.[37] Jumping RTM build numbers is common practice among consumer-oriented Windows versions, like Windows 98 (build 1998), Windows 98 SE (build 2222), Windows Me (build 3000) or Windows XP (build 2600), as compared to the business-oriented versions like Windows 2000 (build 2195) or Server 2003 (build 3790). On November 16, 2006, Microsoft made the final build available to MSDN and Technet Plus subscribers.[38] A business-oriented Enterprise edition was made available to volume license customers on November 30, 2006.[39] Windows Vista was launched for general customer availability on January 30, 2007.[3]
New or changed features[edit]
New features introduced by Windows Vista are very numerous, encompassing significant functionality not available in its predecessors.
End-user[edit]
- Windows Aero is the new graphical user interface, which Jim Allchin stated is an acronym for Authentic, Energetic, Reflective, and Open.[40] Microsoft intended the new interface to be cleaner and more aesthetically pleasing than those of previous Windows versions, and it features advanced visual effects such as blurred glass translucencies and dynamic glass reflections and smooth window animations.[41] Laptop users report, however, that enabling Aero reduces battery life[42][43] and reduces performance. Windows Aero requires a compositing window manager called Desktop Window Manager.
- Windows Shell offers a new range of organization, navigation, and search capabilities: Task Panes in Windows Explorer are removed, with the relevant tasks moved to a new command bar. The navigation pane can now be displayed when tasks are available, and it has been updated to include a new "Favorite Links" that houses shortcuts to common locations. An incremental search search box now appears at all times in Windows Explorer. The address bar has been replaced with a breadcrumb navigation bar, which means that multiple locations in a hierarchy can be navigated without needing to go back and forth between locations. Icons now display thumbnails depicting contents of items and can be dynamically scaled in size (up to 256 × 256 pixels). A new preview pane allows users to see thumbnails of items and play tracks, read contents of documents, and view photos when they are selected. Groups of items are now selectable and display the number of items in each group. A new details pane allows users to manage metadata. There are several new sharing features, including the ability to directly share files. The Start menu also now includes an incremental search box — allowing the user to press the ⊞ Win key and start typing to instantly find an item or launch a program — and the All Programs list uses a vertical scroll bar instead of the cascading flyout menu of Windows XP.[41]
- Windows Search is a new content index desktop search platform that replaces the Indexing Service of previous Windows versions to enable incremental searches for files and non-file items — documents, emails, folders, programs, photos, tracks, and videos — and contents or details such as attributes, extensions, and filenames across compatible applications.[41]
- Windows Sidebar is a translucent panel that hosts gadgets that display details such as feeds and sports scores on the Windows desktop; the Sidebar can be hidden and gadgets can also be placed on the desktop itself.[41]
- Internet Explorer 7 is a significant revision over Internet Explorer 6 with a new user interface comprising additional address bar features, a new search box, enhanced page zoom, RSS feed functionality, and support for tabbed browsing (with an optional "quick tabs" feature that shows thumbnails of each open tab). Anti-phishing software is introduced that combines client-side scanning with an optional online service; it checks with Microsoft the address being visited to determine its legitimacy, compares the address with a locally stored list of legitimate addresses, and uses heuristics to determine whether an address's characteristics are indicative of phishing attempts. In Windows Vista, it runs in isolation from other applications (protected mode); exploits and malicious software are restricted from writing to any location beyond Temporary Internet Files without explicit user consent.
- Windows Media Player 11 is a significant update to Microsoft's Windows Media Player for playing and organizing photos, tracks, and videos. New features include an updated GUI for the media library, disc spanning, enhanced audio fingerprinting, instant search capabilities, item organization features, synchronization features, the ability to share the media library over a network with other Windows Vista machines, Xbox 360 integration, and