Windows 95 build 90c

Windows 95 build 90c is an internal Milestone 6 build of Windows 95, which was originally scene-leaked and considered lost, but was later found and uploaded to BetaArchive by Battler on 17 November 2017. It is a re-compile of builds 90 and 90b, based on the letter following the build number. In general, this build has a very similar feature set to build 89e, including all of the bugs from the previous build.

New features and changes

 * This build includes an application to play CD Audio. It can be run via, but it fails to load due to insufficient memory.
 * The Games folder has been moved to inside the Accessories folder.
 * This build now offers the user to boot into clean mode if regular boot fails. This would later evolve into fail-safe mode and then into Safe mode. To boot into it, press F5 before the boot screen appears.

Setup

 * Setup now features an option to recover the setup process when launching it after a crash. This would later evolve into SmartRecovery and then into Safe Recovery.
 * On the "Customize" page, the "Select directory" button has been moved to a new "Advanced.." page.
 * The final message has been changed to prompt the user to remove all floppy disks from the floppy drives.
 * The "User Information" page has the company field filled out with "Microsoft Corp. (Build90)". There is now also a "Product Identification Number", also being filled out by a string of letters.

Windows 94 and 4.0 references
This build is the only known build of Microsoft Chicago that includes a reference to Windows 94. A dialog used by setup mentioning Windows 94 was discovered by the BetaArchive member Lucas Brooks. This find is interesting as the first build to use Windows 95 branding was build 189, which was compiled six months after build 90c.

This find also suggests Chicago was planned to be called Windows 94 in the first part of 1994. It's also possible this was one of a few final names considered at the time.

In addition there is also a Windows 4.0 reference. When creating an emergency boot disk, setup will prompt the user to label the disk as "Windows 4.0 Emergency Boot Disk".

Setup

 * Due to missing files, there will be two errors that a file could not be copied during setup; one of them being . They can be safely skipped in order to allow setup to continue. This does not apply for some copies.
 * After system detection, an error will appear that Windows Help could not be initialized.
 * It is currently not possible to upgrade to this build due to an error appearing after system detection. Clicking on OK will exit setup.
 * This is the first build where you are not able to initialize setup from an existing Windows installation. It is possible that this block was implemented due to setup still being buggy when launching it from there. It was removed temporarily in the official Beta 1 and permanently in build 267.

File differences
The following files have been introduced or removed compared to build 89e: