If you are thinking about formatting a drive from BIOS, pause before changing the boot order or deleting a partition. A normal BIOS or UEFI setup screen does not provide the Windows command that creates a file system. It can detect hardware and choose what starts next. Actual formatting happens in another environment, such as Windows Setup or a disk-management tool started from bootable media. If the drive still holds files you need, retrieve and verify those files before using either one.
What BIOS can show you about the drive
The firmware screen appears before Windows. Its storage or information page may show a drive model, capacity, and connection type. Its boot page may list Windows Boot Manager, an SSD, a USB installer, or network boot. Those entries answer different questions: whether the machine can see a device and which boot target it will try first. Neither tells you that the contents of the drive have been safely copied elsewhere.
Names vary by manufacturer. One PC says BIOS Setup; another says UEFI Firmware Settings. A laptop may hide storage details under Information, while a desktop board shows them under SATA or NVMe Configuration. Write down the drive model and approximate capacity before you make changes. A 1 TB internal SSD and a 1 TB external backup drive can look deceptively similar in a later installer. The model is a better identifier than a drive letter, because letters assigned in a recovery environment may not match those in your normal Windows session.
If the expected drive is absent in firmware, formatting is not the next test. Check a single known-good power or data connection if the device is accessible without dismantling a sealed laptop. Disconnect nonessential USB storage to reduce confusion. If the drive repeatedly disappears, reports the wrong capacity, makes clicking sounds, or triggers severe read errors, stop. Repeated installation attempts and scans may reduce the chance of recovering important data. A specialist image or professional recovery assessment is safer than trying to force a format.
A one-time boot menu only chooses what code starts. Selecting a USB installer may eventually display disk options, but that is Windows Setup running after the firmware has handed off control. The difference matters because the words Delete, New, and Format in Setup act on the selected disk. They are not harmless BIOS preferences that can be reversed by restoring firmware defaults.
Decide whether the target is truly empty
Before changing a disk, confirm which physical drive it is, what files or Windows partitions it contains, and whether you have opened a backup copy. Cloud sync alone is not proof: files may be missing, outdated, or never fully uploaded.
If Windows starts, copy essential files to a separate healthy drive, including Desktop, Documents, Pictures, Downloads, project folders, and data stored elsewhere. Check the copy’s size and open sample files. Save your BitLocker recovery key before moving the drive or changing boot settings.
If Windows does not start, check whether firmware consistently detects the drive at the correct capacity. A stable drive may allow file copying through a recovery environment or another Windows PC; avoid installing software on it. If detection is unreliable, avoid repeated scans and consider controlled imaging or professional help.
As the guide to unallocated disk space explains, a missing partition does not necessarily mean its files are gone. Do not create a volume or format the disk until you have confirmed its old contents are expendable.
When Drecov can help before a format
PandaOffice Drecov is Windows data-recovery software for files on a stable, recognizable source. In this situation its job is to retrieve needed data before Windows Setup deletes or formats a partition. It can scan a hard drive, SSD, USB device, memory card, or a lost partition when that is the actual loss state. Quick Scan and Deep Scan let you search for documents, photos, video, audio, email data, and archives; filtering and preview help you decide which results are worth saving. Recovery is directed to another healthy location. Drecov does not format a drive inside BIOS, repair a physically failing device, or guarantee that already overwritten files will return.
⚠ Warning: Install it on a drive different from the one where your data was lost to prevent overwriting.
This route requires a working Windows environment and a source that remains stable enough to read. If the original PC cannot boot, attach the drive to another suitable Windows computer or use an appropriate recovery environment before opening the program. Do not install Drecov on the affected partition. Prepare a separate destination with enough free space for the files you intend to keep. If the source disappears, changes capacity, or becomes noisy during access, stop scanning and seek an image or specialist assistance.
Step 1: Open Drecov and choose the original location
Open Drecov on the working Windows computer. Select the original drive or partition that held the files, using its model, capacity, and former folder location to avoid choosing the backup destination. If the partition itself has vanished, use the verified Lost Partition Recovery mode rather than pretending a new empty volume is the old one. Do not initialize or recreate the partition just to make it appear in File Explorer.
Step 2: Scan, then decide whether a deeper search is justified
Start Quick Scan and inspect the folder tree and likely file categories. This is the first pass for missing files on a readable source. If important folders are absent and the drive remains stable, run Deep Scan. A deeper scan can take more work from the device; it is not the right response to clicking, disconnections, or escalating I/O errors. Stop and preserve the source if its condition worsens.
Step 3: Narrow the results and inspect representative files
Filter or browse by file type, former path, or filename. Check a handful of critical documents, pictures, and archives with preview where that file type is supported. A preview can show that the displayed sample is readable, but it does not prove that every page of a long document, every frame of a video, or every member of an archive is intact. Select the needed files rather than recovering every temporary item without review.
Step 4: Recover elsewhere and test the copy
Save the selected files to the prepared healthy drive, never back to the source that may be formatted. If the output is not under the former folder path, check the Drecov folder or Recovery folder at the selected destination. Open a representative set of recovered documents, images, and archives. Compare important project folders with a backup or expected file list. Only when the copies you need are present and usable should you return to partition changes or Windows installation.
⚠ Warning: Install it on a drive different from the one where your data was lost to prevent overwriting.
Use Windows installation media for the actual disk change
Once the target is verified empty or its files are safely backed up, use Microsoft’s Windows installation media instructions to make an installer on a separate USB drive. Creating the installer erases that USB, so never use one holding the only backup. Boot from the USB in the intended UEFI mode. In Windows Setup, check the target disk’s model and capacity against your notes, and disconnect unrelated external drives where possible. If the target is missing or you cannot distinguish Disk 0 from Disk 1, stop and identify it outside Setup.
Setup can partition and format a confirmed empty target. Deleting partitions on a used disk may hinder recovery; small EFI, recovery, and reserved partitions are normal. For the specific error, see the Windows 11 partition selection errors guide. Do not use DiskPart clean or switch between UEFI and Legacy merely to make formatting available. Either choice can affect the wrong disk or an existing boot path.
If the goal is repair rather than a fresh installation
Sometimes “format from BIOS” is a proposed fix for a Windows PC that will not start. Formatting does not repair the cause of a startup failure; it replaces the file system and may erase the only available copy of personal data. First determine whether the disk appears normally in firmware and whether Windows Recovery Environment can open. A consistent device at the expected capacity invites software diagnosis after data protection. A missing or unstable device points toward connection or hardware work instead.
If Windows Recovery Environment opens, its startup tools can investigate certain boot problems without immediately reinstalling. The exact option depends on the symptom and recovery screen. Startup Repair, uninstalling a recent update, and System Restore have different effects, so record what recently changed before choosing one. A full reset or clean installation is a separate, potentially destructive decision. The article on reinstalling Windows while preserving files and apps deals with that broader choice. It does not remove the need to verify a backup.
If the drive was only recently added and has never held data, initialization and volume creation in Windows Disk Management may be simpler than booting an installer. That path applies to a secondary data disk, not the active system drive. Identify the blank physical disk by model and capacity, choose the intended partition style, create a volume, and select a file system suited to the devices that will use it. Do not initialize a disk with missing files, an unexpected RAW status, or a prior partition that disappeared. Those states deserve diagnosis before a new structure is written.
Verify the result before using the drive normally
After an intended fresh installation, remove the installer when Setup directs you to restart. Confirm that the machine starts from the correct internal drive, that Windows reports the expected storage capacity, and that the separate backup remains connected only when you need to copy data back. Open several recovered files from their destination before moving them. A filename in File Explorer is not enough to prove that a document or video survived the original problem.
For a secondary drive, copy a small test file to the new volume and reopen it. Safely remove and reconnect an external device if appropriate, then confirm the file is still readable. If the volume disappears, reports the wrong capacity, or becomes unusually slow, stop adding new files. Formatting again is unlikely to resolve an unstable connection or failing media and will complicate recovery of anything you just wrote.
The practical answer is therefore conditional. Use firmware to confirm detection and select a boot device. Use Windows Setup or Disk Management only when you have identified the correct, dispensable target. Use recovery tools before those steps when old files still matter. Keeping those jobs separate prevents a misleading “BIOS format” instruction from becoming accidental data loss.
Conclusion
Formatting a drive from BIOS is usually the wrong description of the task: firmware can point the PC to a bootable tool, but the tool performs the disk change. Check the device identity and protect valuable files first. On a stable recognized Windows source, Drecov can scan the original location, help you preview what remains, and recover selected files to another healthy drive. Verify that copy before allowing Windows Setup or Disk Management to format anything.
⚠ Warning: Install it on a drive different from the one where your data was lost to prevent overwriting.
