Windows Vista build 5112

Build of Windows Vista
OS family
Architecturex86, x64
Timebomb2006-09-30 (+437 days)
Works in
LH5112 Winver.png
TCB.png TCBGallery.png

Windows Vista build 5112 is the official Beta 1 build of Windows Vista, which was officially released on 27 July 2005. It is one of the first Beta 1-class builds to be compiled, and certainly, the first Vista build to become widely available.

At this point in development, Microsoft had decided that Windows Vista would be the final name of the operating system, hoping to boost the image and perception of the product among end users. Jim Allchin himself expressed his feelings for the name, stating:

"'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."

However, the name Longhorn was still used in numerous areas, such as within the About Windows dialog box, the registry entry for Winlogon, and on the boot screen. This is to be expected, considering the point at which this build was compiled (it was compiled two days before the announcement of the name change to Vista). The name Vista was only mentioned on the desktop watermark.

Build 5099 or later is required to upgrade to this build, but it is possible to flawlessly upgrade from 5098 by replacing the sources folder (excluding install.wim) from 5098 itself.

Setup[edit | edit source]

Although setup is mostly similar to the previous build, the hardware portion of setup now contains a dummy progress bar again[note 1].

New features and improvements[edit | edit source]

  • List Pane for Static Lists
  • Media Foundation Protected Pipeline
  • The ability to create a list from the New section in context menus is removed.
  • Hibernation settings have been added to Power Options.

Aero theme updates[edit | edit source]

  • The Aero theme gained a slight update from 5098, featuring more distinct borders and fixed text color on some windows. Using a patched uxss.exe file created by LucasB, it is possible to initiate DWM with XPDM drivers. Otherwise, DWM could only be initialized with LDDM drivers, requiring the use of physical hardware with a LDDM-compatible graphics card (or a LDDM-compatible graphics card passed through to a VM using hypervisors such as QEMU). After replacing uxss.exe, navigate to HKEY_LOCAL_MACHINE\Software\Microsoft, create a new key called DWM, then create the following 3 DWORDs inside the key:
Key Values
EnableMachineCheck 1 - enabling machine check, which disallows the possibility of using XPDM drivers

0 - disables machine check

ForceSoftwareD3D 1 - forces software rendering

0 - hardware rendering

Glass 1 - transparent titlebars

0 - disables glass effects

UseAlternateButtons (optional) 1 - squished Vista-like buttons

0 - normal buttons

MagnificationPercent (optional, use at your own risk!) 0 or 100 (decimal) - normal scaling

any decimal value in range of 1 to 99 - downscaling percentage of windows

any decimal value more than 100 - upscaling percentage of windows

After making these changes, log out then log back on to initialize DWM. If DWM still doesn't start automatically, kill uxss.exe process.

Full Volume Encryption[edit | edit source]

  • Windows Full Volume Encryption API (fveapi.dll)
  • FVE Auto Convert Utility (fveauto.exe)
  • FVE Utility (fveconv.exe)
  • Windows Full Volume Encryption Tool (fvetool.exe)

New apps[edit | edit source]

  • Two new icons have been added to the desktop, one leading to a supplemental driver installer that simply installs drivers made for Windows XP that aren't ready to work on this build yet, while the other is a shortcut to a document talking about Avalon and Indigo.

Bugs[edit | edit source]

Installation[edit | edit source]

  • Although this build can partition as intended during setup, the partitioning page doesn't refresh properly, requiring you to reboot your system in order to see the new partition.

DWM rendering[edit | edit source]

  • On some configurations with patched uxss.exe, when ForceSoftwareD3D value is set to 0, the screen freezes (except for the cursor), until DWM is disabled, even if hardware acceleration is set to full. Along with that, if glass effects are enabled, there would be artifacts on non-Explorer window borders.

Gallery[edit | edit source]

Miscellaneous[edit | edit source]

Notes[edit | edit source]

  1. A dummy progress bar moves to the right by its own, until it reaches the end where it would go back to the start and repeat the same action.