A systems administrator is creating a bootable USB drive to install a new server operating system. The administrator formats a 32GB USB drive with a FAT32 file system and begins to copy the extracted files from the OS installation ISO. The copy operation fails with an error stating a file within the 'sources' directory is too large for the destination file system. Which of the following actions should the administrator take to create a functional bootable USB drive for a modern UEFI-based server?
Change the server's boot mode from UEFI to Legacy BIOS to improve compatibility.
Use a USB 2.0 port on the server instead of a USB 3.0 port.
Reformat the USB drive using the NTFS file system before copying the installation files.
Convert the USB drive's partition table from MBR to GPT.
Reformatting the USB drive to NTFS eliminates the 4 GB single-file limitation imposed by FAT32, allowing large installation images such as install.wim to be copied without error. Although the UEFI specification guarantees support for FAT but not NTFS, many current server platforms-and third-party bootloaders such as Rufus's UEFI:NTFS driver-can read NTFS partitions during boot, so an NTFS-formatted stick usually works for Windows Server media. Switching to Legacy BIOS, changing from MBR to GPT, or using a different USB port does not change the underlying file-system restriction that caused the copy failure.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
Why does FAT32 have a file size limitation?
Open an interactive chat with Bash
What is the difference between FAT32 and NTFS?
Open an interactive chat with Bash
What is UEFI, and how does it differ from Legacy BIOS?