Planning a 25-PC training lab upgrade for Windows 11 and a 9.5 GB legacy ISO
A district skill-training centre runs a 45-day course on 25 desktop PCs. Inventory: 12 PCs with Core i3-4130 (4th generation), 4 GB RAM, 500 GB hard disk, no TPM; 9 PCs with Core i3-8100 (8th generation), 4 GB RAM, 1 TB hard disk, TPM 2.0 enabled; 4 PCs with Core i5-10400, 8 GB RAM, 256 GB SSD, TPM 2.0. The revised syllabus requires Windows 11, 8 GB RAM for a browser-based 3D design tool, and a legacy 32-bit accounting package supplied as a 9.5 GB ISO. That ISO and a Windows 11 installation image containing a 6.8 GB install.wim are both kept on one 32 GB pen drive, and both copies fail with 'the file is too large for the destination file system'. On one of the 4 GB machines the design tool freezes whenever three browser tabs and the accounting package are open together. The centre has a fixed upgrade budget and can replace only a few machines.
1. Diagnose the copy failure and recommend the correct fix, explaining why the obvious fix can break the Windows installation media.
Read the worked answer
The pen drive is formatted FAT32, which caps any single file at 4 GB minus one byte. Both files exceed that: the 9.5 GB ISO and the 6.8 GB install.wim.
Reformatting to exFAT or NTFS fixes the copy but can break the Windows media: UEFI firmware boots from a FAT32 partition and has no built-in NTFS driver, so an NTFS-only stick may simply not appear in the boot menu. The fix that works depends on what the drive is for.
For the Windows 11 installer, keep FAT32 and split the image: dism /Split-Image /ImageFile:install.wim /SWMFile:install.swm /FileSize:3800 This produces install.swm plus one or more install2.swm files, all under 4 GB, which Windows Setup reads natively. The alternative is a tool that builds two partitions: a small FAT32 boot partition plus an NTFS data partition holding the large file.
For the legacy accounting ISO, which is data rather than boot media, just copy it to an exFAT pen drive; exFAT is preferable to NTFS if the same drive must also be readable on non-Windows machines. Do not reformat the boot stick to exFAT to solve a data problem, and do not use a 32 GB drive as the only copy of either image.
2. The centre must run Windows 11 on as many of the 25 machines as possible on a limited budget. Produce the upgrade plan and justify the priority order.
Read the worked answer
Sort the fleet by the actual Windows 11 gates: a supported processor (8th generation or newer), TPM 2.0, UEFI with Secure Boot, 4 GB RAM minimum and 64 GB storage.
Group 1, the four Core i5-10400 units: already compliant and already at 8 GB. Do nothing.
Group 2, the nine Core i3-8100 units: processor and TPM are fine, RAM is not. Add memory to reach 8 GB, buying a matched pair rather than a mismatched single module where slots allow. These become the main teaching machines; an SSD is a later upgrade, not a blocker, though the design tool will feel slow on a 1 TB spinning disk.
Group 3, the twelve Core i3-4130 units: 4th generation is outside the supported processor list and there is no TPM 2.0, so no RAM or firmware change rescues them. Replace as many as the budget allows and reimage the rest as Linux or thin clients for the legacy accounting package, which does not need Windows 11.
Two points that change the arithmetic: the 32-bit accounting package runs fine under WoW64 on 64-bit Windows 11, so there is no reason to preserve a 32-bit OS for it; and buying Windows licences for machines that will never be compliant is wasted money. Spend in order: replacements, RAM, SSDs.
3. Diagnose the freeze on the 4 GB machine and state what you would measure before recommending a purchase.
Read the worked answer
A freeze that appears only when three browser tabs and a memory-hungry package are open on a 4 GB machine is the classic signature of memory pressure and paging, not a corrupt install.
Measure before buying: open Task Manager, Performance tab, and Resource Monitor. Look for committed memory approaching 3.8 GB of 4 GB physical, 'available' down to a few hundred megabytes, and a disk queue length that climbs above 2 exactly when the freeze occurs. In Resource Monitor, the 'Hard Faults/sec' spike identifies paging. Also check that the page file is system-managed and has not been disabled by an earlier 'optimisation' tip, and close the browser's hardware-acceleration setting as a test.
If the numbers confirm paging, the correct fix is 8 GB of RAM, matching the syllabus requirement. Fitting an SSD helps the symptom, because paging to flash is far less painful, but it does not remove the cause, so do it second.
If the freeze persists at 8 GB, the problem is elsewhere: the 3D design tool likely needs WebGL2 and a discrete GPU that the integrated graphics on these generations may not provide, and that is a hardware constraint no RAM upgrade fixes. Test by running the tool on the newest Core i5 machine before spending on the older ones.