Windows Longhorn build 4088

From BetaWiki
Jump to navigation Jump to search

Build of Windows Longhorn
OS family
Timebomb2005-01-02 (+180 days)
Works in
Preinstallation Environment
TCB.png TCBGallery.png

Windows Longhorn build 4088 is a Milestone 7 build of the Microsoft Windows Longhorn operating system. Previously, only the Preinstallation Environment for this build had leaked. On 13 January 2015, BetaArchive user Daniel uploaded the full version of this build to the aforementioned site's FTP server.[1]

Changes and fixes[edit | edit source]

  • This build no longer shows the boot screen upon initializing Preinstallation Environment and Setup. The boot screen when starting setup and WinPE was reused in Windows Vista build 5048.
  • WordPad can now be opened again, (unlike builds from 4081 to 4087).
  • The shortcuts in the quick launch are now present again on the sidebar and taskbar.

Bugs and quirks[edit | edit source]

  • Safe mode is broken and displays a BSOD.
  • CD and DVD drives behave like local drives.
  • When enabling the slideshow sidebar tile, explorer.exe restarts in a loop. Only fix is to remove the slideshow tile from the registry.
  • Help and Support causes an explorer.exe restart.
  • Computer Management displays script errors.
  • The Windows Classic theme will not function due to a broken Windows Classic.theme file.
  • Outlook Express does not start.
  • Hardware and Devices folder does not open.
  • Phone and Modem Options Control Panel applet name is empty.
  • Enabling VGA Mode is required after installing video drivers or the system will initiate a BSOD with a error code 0x000000B4.

Installation[edit | edit source]

  • As typical of builds in this build range, it tends to take a long time to install and can be unstable.
  • Partition and format a drive from a previous or later build prior to starting installation.

Timebomb[edit | edit source]

It is one of the notable Longhorn builds that has a broken timebomb and can be installed on the current date.

No mouse driver in WinPE[edit | edit source]

On some computers and virtualizers, the WinPE doesn't support the mouse, so you must use the keyboard to navigate the WinPE. This seems to be related to using a PS/2 mouse, as USB mice seems to work fine for the setup.

TCP/IP bug[edit | edit source]

The TCP/IP stack can tend to malfunction, as it will result in a BSOD with a error code 0x000000D1.

Gallery[edit | edit source]

References[edit | edit source]