Windows Vista build 5048
|Build of Windows Vista|
|Architecture||x86, x64, IA-64[note 1]|
|Timebomb||+180 days after original install date|
Windows Vista build 5048 is a pre-Beta 1 build of Windows Vista. It is the official Longhorn Developer Preview, which was released to attendants of WinHEC 2005 on 24 April 2005. The checked/debug versions of this build were uploaded on 26 December 2021.
Being a pre-beta 1 build, it is noticeably closer to Windows XP and Windows Server 2003 than to pre-reset builds. It is also an
idx02 build, which suggests that it was recompiled several times, and therefore is behind regular builds compiled at the time. The x64 version of this build is similar to the x86 build, but it has a different End-user license agreement and Windows XP x64 Edition brand wallpaper instead of the Windows Server 2003 brand wallpaper which is named as
Unlike other post-reset Vista builds, it was compiled in evaluation mode, and it can be installed on the current date. The timebomb in evaluation mode behaves just like pre-reset builds; if the timebomb expires, the user is automatically logged out.
This is the last available Windows build to include the Luna theme, although it is noticeably broken and uses Slate graphics for the right pane of the Start menu. It is also the last known build of Windows to include the game 3D Pinball Space Cadet, as well as the last to include the login prompt used in Windows 2000 build 1946.1 and onward, and the logoff prompt used in Windows 2000 build 2031.1 and onward.
Setup[edit | edit source]
Although previous builds of post-reset Vista used the older i386 installation process, this build reimplements the Windows Preinstallation Environment installation process from later builds of Longhorn, retaining the older Slate design as well. However, a few changes have been made. The launching WinPE screen does not show anymore, now leaving you without any option of pressing F6 to load in certain drivers during boot. However, the user still can load drivers by selecting the "Load Driver" option at the page where the user decides where Windows will be installed, signified by an F6 key icon.
The starting setup screen has also been altered, and now features the Windows flag. The ClearType functionality originally seen in most pre-reset builds' Preinstallation Environments has been disabled, and the step numbers on the progress bar no longer glow. The hardware portion of setup now also includes a dummy progress bar at the bottom of the screen[note 2], and the Windows flag has been added to the middle of the page. A minimum hardware limit of 256MB RAM has also been imposed in an effort to reduce the chances of installation failure. Asides from all of these minor changes, setup is overall mostly similar to what was found in later pre-reset builds of Longhorn. Unlike other Longhorn builds, however, the Windows Classic visual style is present in a similar fashion to build 4093 and early builds of Windows 8.
New features and changes[edit | edit source]
A majority of features that were added in this build were the result of feature backporting from builds compiled prior to the development reset.
- This build includes Windows System Assessment Tool (shortly WinSAT) and Windows Diagnostic Infrastructure (WDI). However, WinSAT is non functional and links lead to an intranet website instead.
- Windows Media Player 10 and Internet Explorer 6 SP2 are also now present.
- Sync Manager (Later known as Sync Center) has been introduced.
- Many of the icons from later pre-reset builds have returned, some with minor alterations. A few icons are also new to this build. However, the Control Panel and Printers icons are from Windows 95, just like late pre-reset builds.
- This build uses the legacy login dialog in place of the regular Windows XP login screen. The aformentioned login screen can be enabled through the User Accounts Control Panel applet, and is a leftover that would be removed before build 5098.
- This build uses
BOOTMGRas the default bootloader, but still includes
NTLDRas an alternative way to boot, and can be observed if dual booted with an earlier version of Windows.
- A zoom slider has been added to Paint.
- Self-Healing NTFS was reintegrated from pre-reset build 4074.
- Instant Search was implemented in this build.
- The Control Panel was revamped, bearing a similar design that is comparable to the RTM build.
- The Microsoft Anna speech synthesizer first seen in pre-reset build 4093 was reintroduced.
- This build changes the
AUTOCHKscreen to blue, and the text black.
Windows Boot Manager[edit | edit source]
This is the first known build to include the Windows Boot Manager (
NTLDR used since the Windows NT 3.1 October 1991 build. Though it still uses
BOOT.INI instead of BCD.
Unlike later builds, the error screen is red in this build, leading to it being called a red screen of death. Furthermore, the advanced boot options screen is blue. Text mode is also used at all times, while later versions use a framebuffer console in a VESA-compatible mode if possible.
This is also the first build to require ACPI support, as it is required by the new boot loader and trying to start Windows on a non-compliant system results in an error.
- My Computer has been renamed to Computer, as with late pre-reset builds.
- File checkboxes and scalable icons (first seen in pre-reset builds) have been reintroduced.
[edit | edit source]
The start menu received a number of updates, which include (but are not limited to) a search box, transparency and an inline menu replacing the original All Programs context menu.
Windows Aero[edit | edit source]
- This build marks the debut of the Aero theme (which is loaded by default without DWM), and features two glass theme variants.
- The alternate caption button incorporates a design similar to later builds of Vista, the only difference being that the maximize/minimize buttons are directional arrows.
- The Aero theme is now the default theme overall system, along with its visual effects and wizards.
Desktop Window Manager[edit | edit source]
This build of Vista reintroduces the Desktop Window Manager, which was originally absent since the development reset. The window manager will crash on startup if no GPU driver is installed, and software rendering is required if no compatible driver is available. Although LDDM drivers are now included by default, which claim to feature support for most GPUs at the time of compilation, there has currently been no success in attempts focusing on enabling the driver stack (even with drivers that were ported from other builds), highlighting the possibility that the graphics stack may not be functional. However, this build's DWM subsystem can run with a regular XPDM driver as long as a whitelisted GPU is either installed or if the whitelist is bypassed through means of registry modification.
There are two different ways of initializing DWM, one is modifying the registry, while the other is initializing a DLL via
rundll32.exe. The more simpler rundll32.exe method is simply opening up the command prompt, and typing
rundll32 udwm.dll,DwmClientStartup. This, however, randomizes the effects used with DWM. The other method of initializing DWM can be done via opening the Registry Editor, navigating to
HKEY_LOCAL_MACHINE\Software\Microsoft, creating a new key called DWM, then creating the following DWORDs inside the key:
|EnableMachineCheck||1 - enables machine check, which restricts DWM support to the ATI Radeon 9800 and NVIDIA GeForce FX 5900 series[note 3]
0 - disables machine check
|ForceSoftwareD3D||1 - forces software rendering
0 - hardware rendering
|Metal||1 - makes the titlebar yield an opaque style similar to Jade in Windows Longhorn build 4074
0 - transparent Aero titlebars like in build 4050
|UseAlternateButtons||1 - square-like buttons
any other value - build 4050's Aero buttons (downscaled to a smaller size due to a bug)
After making these changes, log out (and vice versa) to initialize DWM. The functionality can be toggled on and off using Ctrl+Shift+F9 like in most other builds featuring DWM.
Glass effects in Windows Classic theme
User Account Control[edit | edit source]
This is the first build after the development reset to include a preliminary version of User Account Control.
Removed features[edit | edit source]
- MSN Gaming Zone
- Windows NetMeeting (which would be replaced with Windows Meeting Space later during development)
- Windows XP Tour
- Filmstrip view in Windows Explorer
Bugs and quirks[edit | edit source]
- There is a limit of 50 files able to be browsed per folder, but it can be bypassed by viewing icons in groups.
- Enabling auto login for the default user account while having the new login screen enabled can make the login screen throw up an error. This can be safely ignored.
Turn off computeroption is missing from the new login screen.
- With fast user switching enabled, the "Switch user" option doesn't appear when selecting "Log Off". Instead, the Log Off dialog is always the one Windows XP would display with fast user switching disabled. It is still possible to switch users using the key combination Windows+L.
- Help and Support does not open due to a missing
helpctr.exe, but an updated help application, called
HelpPane.exe, can be found in the Windows folder.
- The Windows logo has a white background on the hibernation screen.
Installation[edit | edit source]
- The setup switches to 16-bit color 800x600 video mode after briefly using 24-bit 640x480 during its startup, resulting in a noticeable dithering effect of the background during setup.
- Although this build can partition properly during setup, the partitioning page doesn't refresh properly, requiring you to reboot your system in order to see the new partition.
- The timer located at the bottom-right corner in setup is not functional, as it always displays
15-25 minutes left...regardless of the progress.
- The debug version may cause a red screen crash after installation because the BCD is not created normally.
Upgrading[edit | edit source]
While this build requires build 5019 or higher to upgrade to,
preupgradenotice.txt in the sources folder lists various bugs that will be encountered when an upgrade takes place.
Longhorn ReadMe File for Internal Upgrades Quality Statement Build to build CBB upgrades complete OS migration successfully without data loss or a reinstallation of the OS, and a functional migration of the following items: 1. Applications · Office 2003 · Product Studio 2. Developers’ Environment · Razzle Environment · Visual Studio 2005 Beta 1 · Visual Studio 2003 3. System Settings · Domain Membership, Security accounts with password, Computer Name Measurement is based on a minimum of 100 systems installs (50 Lab and 50 Self Host system upgrade completions) and meeting the Longhorn Quality Gates. For more detail on the release criteria, see http://winweb/warteam/_content.asp?id=46&r=905 ** Restricted upgrade scenarios ** Upgrade is *NOT* supported in the following scenarios for this RI: 1. OS being upgraded is a build lower than 5019 * 2. OS being upgraded is an INF build (only CBB -> CBB upgrades are supported) * 3. OS being upgraded is newer than the one being installed 4. OS being upgraded is 64-bit, setup being run is x86 5. OS being upgraded is a server build 6. OS being upgraded is LH Home, setup being run is LH Pro 7. OS being upgraded has multiple OS’s installed on the target partition * Upgrade support is planned for these scenarios in future milestones. ** Known Migration Issues ** Some system settings don’t migrate For this RI, system settings are not expected to migrate correctly yet – this is by design. Known issues include the failure to migrate: · Mapped network drives · IE pop-up blocker – allowed sites · IE toolbars · Proxy server info · Printers & faxes · Folder attributes (sharing, compression, redirection, etc.) · Some desktop shortcuts System setting migration will be supported by Beta 1. ** Drivers do not migrate ** Some drivers (e.g. out-of-box video drivers) do not migrate. You’ll need to reinstall drivers for now. Going forward, more robust driver migration will be supported. (Bug 1061700) ** Upgrading a laptop results in loss of network connectivity. ** Temporary workaround is to use a wired connection and rejoin the domain. (Bug 1062094) ** Product Activation (WPA) timer is not reset on migration ** If Windows is not activated prior to migration, the 15-day activation timer continues to count down post-migration from the date of the last clean install. The simple workaround is to activate Windows. (Bug 1062178) ** Fonts installed by applications are not installed to the system. ** Temporary workaround is to retrieve the font from the Quarantine folder. (Bug 1060342) ** Outlook shortcut icon is not displayed in Start menu after migration; icon used doesn’t launch Outlook. ** Shell settings are slated to be migrated properly in the last RI prior to Beta 1. (Bug 1059072) ** The home page of the .Net framework documentation becomes www.msn.com. ** This is an IE setting, also slated for migration in the last RI prior to Beta 1. Workaround is to repair the .Net framework install. (Bug 1056495) ** Visual Studio .NET 2003 Command Prompt -- one of the .NET tools is not migrated on the target machine. ** Command prompt still works fine – just the shortcut is missing. Workaround = Start -> Run -> “cmd”. (Bug 10565056)
File differences[edit | edit source]
The following files have been introduced, renamed or removed from build 5001:
|wmstream.dll||Windows Media Streamer DLL||22.214.171.12487|
|wmvadvd.dll||Windows Media Video 9 Decoder||10.0.0.3646|
|wmvadve.dll||Windows Media Video 9 Decoder||10.0.0.3646|
|WMVDECOD.DLL||Windows Media Video Decoder||10.0.0.961|
|WMVENCOD.DLL||Windows Media Video 9 Encoder||10.0.0.961|
|WMVSDECD.DLL||Windows Media Screen Decoder||10.0.0.961|
|WMVSENCD.DLL||Windows Media Screen Encoder||10.0.0.260|
|WMVXENCD.DLL||Windows Media Video Encoder||10.0.0.961|
|wpdconns.dll||WPD Connection Objects||5.2.3790.3658|
|wpdmtpus.dll||Usbscan transport layer for MTP driver||5.2.3790.3658|
|wscmisetup.dll||Installers for Winsock Transport and Name Space Providers||6.0.5048.0|
|WSDApi.dll||Web Services for Devices API DLL||6.0.5048.0|
|wshBth.dll||Windows Sockets Helper DLL|
|wshirda.dll||Windows Sockets Helper DLL||6.0.5048.0|
|WUDFCoinstaller.dll||Windows Driver Foundation - User-mode Platform Device Co-Installer||6.0.5048.0|
|WUDFHost.exe||Windows Driver Foundation - User-mode Driver Framework Host Process||6.0.5048.0|
|WUDFPlatform.dll||Windows Driver Foundation - User-mode Platform Library||6.0.5048.0|
|WUDFSvc.dll||Windows Driver Foundation - User-mode Driver Framework Services||6.0.5048.0|
|wups2.dll||Windows Update client proxy stub 2|
|xmlrw.dll||Microsoft XML Slim Library||2.00.3526.0|
|Old filename||New filename||Old description||New description||Version|
|Red moon desert.jpg||RedMoon.jpg|
|wmvdmod.dll||Windows Media Video Decoder||10.0.0.3646|
|wmvdmoe2.dll||Windows Media Video Encoder||10.0.0.3646|
|wowfax.dll||Windows 3.1 Compatible Fax Driver DLL||0.2.0.0|
|wshatm.dll||Windows Sockets Helper DLL||6.0.5001.0|
|wshisn.dll||NWLINK2 Socket Helper DLL||6.0.5001.0|
Gallery[edit | edit source]
Notes[edit | edit source]
- Debug symbols only.
- The progress bar continues to fill up until it has.
- Only the EnableMachineCheck DWORD is required in order to enable DWM composition. The requirement can also be bypassed if substrings
9800are present in the GPU device driver name.