Windows 95 build 180

Windows 95 build 180 is the Beta 1.3 release of Windows 95. It was scene leaked in 1994 and mislabeled as build 177, then found again and shared on OSBetaArchive on 13 December 2015, along with builds 302 and 311. It comes on 14 floppy disks (disk 1 is 1.44MB, the others are DMF-formatted).

This is the latest available build to exclusively refer to itself as Chicago.

Changes

 * Added back Network Neighborhood and the Recycle Bin back to the desktop under the name Wastebasket.
 * Changed the date on the boot screen to be labeled as September 1994 instead of May and removed the Beta 1 text on it.
 * Setup has been updated to resemble the RTM even more.
 * Calculator received a minor interface update, with the most notable change being the new sharp-cornered buttons rather than rounded ones.
 * "Events Scheme" has been separated from Multimedia Properties and is now known as "Properties for Sound Events". The applet received an interface update as well.

LAYOUT.INF issue
in  on disk 2 is for the 19 disk 1.44MB floppy release of this build. This means setup cannot find files in the CAB archives it expects, which makes the installation impossible without modifications. One way to bypass this problem is to swap the wrong  with a fixed one during installation. To do this:


 * 1) Start the installation as usual and get to the welcome screen.
 * 2) You have to save the state of the virtual machine (depends on the hypervisor/emulator you're using) as you cannot leave setup to swap  . However, if you're running setup on Windows 3.1x, you can also switch to File Manager via Alt-Tab or Task Manager to change the file.
 * 3) Mount the virtual hard disk (VHD) in Disk Management. This step can be skipped if setup was run from Windows 3.1x.
 * 4) Navigate to   and replace   you will find there with the one provided separately with the installation disks.
 * 5) Dismount the VHD (or close File Manager), then resume the virtual machine.
 * 6) Install the build as usual.

It is important you do this after setup has already copied files it needs from disks 1 and 2 to the hard drive and before it reads  for file locations in CAB archives. Therefore, this is best done on the welcome screen.

An alternative solution is to place the requested files on another floppy disk and point to the setup to those files.