Windows XP build 2474 (main)

Windows XP build 2474 is a pre-RC1 build of Windows XP, which was released internally on 17 May 2001. However, the Personal SKU was identified fake. However, a screenshot of it can be found in Alan Simpson's bible for Windows XP.

Changes

 * Most Whistler references were replaced with Windows XP.
 * Added an animated Windows flag on the login screen, which would later be removed in build 2481.
 * Graphical Setup now identifies itself as "Windows XP RC1" and now contains a progress bar when upgrade setup is restarting the computer.
 * The safe to shutdown screen was updated to now include Windows XP-style branding. It replaces the version that was previously in use since build 2257.
 * Added five new sample pictures that aren't present in previous builds. The Winter sample picture is introduced for the first time starting with this build, albeit with slight visual differences and a different name, Winter forest.
 * Updated the throbber that is used in Windows Explorer, Internet Explorer and Outlook Express to the Windows XP logo, replacing the one in use since Windows 98.
 * This is one of the first builds to use the modern Windows XP Logo Testing implementation, this can easily be seen when upgrading to this build as almost all hardware will result in the warning that such hardware may not work and cause instability.
 * Some of the icons were updated and changed.
 * The system crash screen's font is changed to  rather than the kernel mode font used in Windows 2000.

Boot screen
A new boot screen was added to replace the Whistler version in use since build 2428. The only differences from the RTM boot screen are the following:
 * There is a breathing "loading..." string instead of the animated blue bar seen in build 2481.
 * The copyright date is at the bottom center instead of the bottom left seen in build 2481.
 * The "version 2002" tag is present.

Installation

 * When upgrading to this build, setup may complain that the network driver cannot be found. Pointing to  and then pressing OK will typically resolve this error.