How to Change Hidden UEFI BIOS Settings (Settings that are not shown in BIOS Setup) - using AMI SCE Utility for AMI Aptio*-based UEFI BIOS

Note: The following procedure is applicable only to motherboards with AMI Aptio*-based UEFI BIOS. It was tested successfully on a MSI Z390-A PRO (MS-7B98) motherboard running the latest BIOS version as of this writing (7B98v1C). Please don't modify BIOS settings if you don't know what those particular settings do as it might cause your PC to no longer boot, thus requiring you to perform a CMOS reset (which might also not fix the problem if you changed the default setting as well!).

Some motherboard OEMs decide to hide certain settings from being shown in BIOS setup. If you need to change any of these settings, the following steps should help you to accomplish this.

1. Download "AMI BIOS ROM Utilities Collection 2020" from http://bit.ly/BIOSUtils.
2. Extract its contents and find the latest version of the AMI SCE Utility under the "AMI SCE All Versions 2020" folder. As of this writing, 5.03.1115 is the latest version currently available.
3. Open an elevated Command Prompt window and "cd" to the 32-bit or 64-bit SCEWIN folder (use the correct version for your system).
4. Run SCEWIN.exe /O /S BIOSSettings.txt (for 32-bit systems) or SCEWIN_64.exe /O /S BIOSSettings.txt (for 64-bit systems). You should get the following output (Note: The warning may or may not appear; this does not indicate an actual error if it indicates "Script file exported successfully."):
5. 
6. Open the exported file "BIOSSettings.txt". You should see something like the following:
7. 
8. For the purposes of this procedure, we will disable the "ACPI Wake Alarm" device (HW ID: *ACPI000E or ACPI\ACPI000E or ACPI\VEN_ACPI&DEV_000E) as an example since it is not supported in Windows 7. This device is enumerated in Device Manager as follows:
9. 
10. Locate the "System Time and Alarm Source" option by using the "Find" option in your text editor. Move the "*" to the desired option. Optionally, change the default option by copying the desired option next to the "=" sign for "BIOS Default".
11. BEFORE: 
12. AFTER: 
13. Once you are finished making changes, save the changes you made.
14. Run SCEWIN.exe /I /S BIOSSettings.txt (for 32-bit systems) or SCEWIN_64.exe /I /S BIOSSettings.txt (for 64-bit systems). You should get the following output (Note: You may ignore the warnings that appear if it indicates "Script file imported successfully."):
15. 
16. 
17. Restart your computer for the changes to take effect.
18. For this example, the "ACPI Wake Alarm" device disappeared from Device Manager upon reboot:
19. 

DISCLAIMER:

*Other names and brands may be claimed as the property of others.

DISCLAIMER OF WARRANTY

YOU ACKNOWLEDGE AND AGREE THAT THE ABOVE PROCEDURE (THE "PROCEDURE") IS PROVIDED "AS IS" AND WITHOUT WARRANTY OF ANY KIND. ALL WARRANTIES, CONDITIONS, REPRESENTATIONS, INDEMNITIES AND GUARANTEES WITH RESPECT TO THE PROCEDURE, WHETHER EXPRESS OR IMPLIED, ARISING BY LAW, CUSTOM, PRIOR ORAL OR WRITTEN STATEMENTS BY HHSOFT OR OTHERWISE (INCLUDING, BUT NOT LIMITED TO ANY WARRANTY OF MERCHANTABILITY, SATISFACTORY QUALITY, FITNESS FOR PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT) ARE HEREBY OVERRIDDEN, EXCLUDED AND DISCLAIMED.

DISCLAIMER OF DAMAGES

UNDER NO CIRCUMSTANCES WILL HHSOFT, ITS LICENSORS OR ITS OR THEIR RELATED COMPANIES BE LIABLE TO YOU FOR ANY DIRECT, CONSEQUENTIAL, INDIRECT OR SPECIAL, PUNITIVE OR INCIDENTAL DAMAGES RESULTING FROM YOUR USE OF THE PROCEDURE AS SPECIFIED ABOVE, WHETHER FORESEEABLE OR UNFORESEEABLE, BASED ON YOUR CLAIMS OR THE CLAIMS OF ANY THIRD PARTY, WHETHER BASED ON THIS AGREEMENT, ANY COMMITMENT PERFORMED OR UNDERTAKEN UNDER ON OR IN CONNECTION WITH THIS AGREEMENT OR OTHERWISE.

Fix Missing or Nonfunctional Intel(R) Ethernet Controller After AMI BIOS Recovery

Fix Missing or Nonfunctional Intel(R) Ethernet Controller After AMI BIOS Recovery

After carrying out the AMIBOOT.ROM AMI BIOS Recovery on an AMIBIOS8 system, you may experience the Intel(R) Ethernet Controller no longer being detected or becoming nonfunctional (with message "This device cannot start. (Code 10)" being shown for the controller's device status in Device Manager).

In this case, this is due to the ethernet controller's firmware configuration being erased as part of BIOS recovery. You can check to see if this was the case by going to the Details tab for the device, and then selecting "Hardware Ids" from the dropdown menu. If the part after "SUBSYS_" is all zeros, then this means the adapter's firmware is likely not initialized.

If this is the case, you now need to check what the controller's original hardware ID was. To check it, open Registry Editor, then go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\.

Expand each of the keys within this key that start with "VEN_8086" (indicating manufacturer is Intel(R)), and click on the key underneath each one, until you find an entry with the "FriendlyName" value being the name of the Intel(R) ethernet controller.

Note down the value stored in "HardwareID".

Now, you will need to find a computer that has the same ethernet controller. For example, the Sony VAIO VGC-JS290J computer has the same model ethernet controller as the Sony VAIO VPC-L148FG computer. The computer does not necessarily need to have the same SUBSYS ID, it only needs to have the correct DEV ID. However, it will result in your target computer having an ethernet controller with the same SUBSYS ID as that of the computer from which you saved the firmware configuration (this still makes it functional). If you want it to have the original SUBSYS ID, you may be able to modify the file using a hex editor (WARNING: This may brick the adapter if there is a checksum enforced within the file), or follow the alternative method below (WARNING: I did not test this alternative procedure).

If you are able to find such a computer, download the Intel(R) Flash Programming Tool (part of the Intel(R) ME/CSME System Tools) at the following location: https://www.win-raid.com/t596f39-Intel-Management-Engine-Drivers-Firmware-amp-System-Tools.html. You will need to read the instructions on the page to determine the Intel(R) ME version on your computer (which is based on your computer's chipset).

WARNING: Intel(R) Flash Programming Tool (Intel(R) FPT) is a very powerful tool that can brick your computer's BIOS if you flash the wrong file or a file with the incorrect size! Make sure you specify "-GBE" at the end of the command or otherwise you will accidentally flash the ethernet controller configuration file to the wrong region of the BIOS chip and brick your computer!

On the computer with the functional ethernet controller, run "FPTW64 -d EthernetROM.bin -GBE" (use FPTW if your computer is 32-bit). This will dump the functional ethernet controller configuration to the same directory as the Flash Programming Tool. Copy this file, along with the correct version of the Flash Programming Tool, to the computer with the broken ethernet controller.

On the target computer, run "FPTW64 -f EthernetROM.bin -GBE" (use FPTW if your computer is 32-bit). This will flash the ethernet controller configuration with that of the other computer.

Restart your computer. If the configuration was suitable for your target computer, your ethernet controller should now be functional.

Alternative Method: If your computer manufacturer has a BIOS upgrade available on the support website:

WARNING: I have not tested this method to see if it works since the previous method worked for me.

Download the AMI BIOS ROM Utilities Collection from http://bit.ly/BIOSUtils. Also download the BIOS ROM file from your computer manufacturer and extract its contents until you get the raw .ROM file (you may need to run the executable file and go to %LOCALAPPDATA%\Temp\ to find the most recent folder, which will probably contain the BIOS file).

Open the BIOS ROM file in the newest version of MMTool (see within MMTool folder in the collection) that suits your BIOS version (for legacy AMIBIOS8 systems, use MMTool 3.26). Select the "RomHole" tab. Extract each of the RomHoles that has "YES" indicating something is stored inside that location. Using a hex editor, open each file, until you see one with hex values "86 80" (representing 8086 for Intel(R)) and then the hardware ID of the ethernet controller (reversed by each pair of digits).

Download the Intel(R) Flash Programming Tool (part of the Intel(R) ME/CSME System Tools) at the following location: https://www.win-raid.com/t596f39-Intel-Management-Engine-Drivers-Firmware-amp-System-Tools.html. You will need to read the instructions on the page to determine the Intel(R) ME version on your computer (which is based on your computer's chipset).

Copy the saved RomHole file with the hardware ID of your ethernet controller to the Flash Programming Tool directory as EthernetROM.bin.

Run "FPTW64 -f EthernetROM.bin -GBE" (use FPTW if your computer is 32-bit). This will flash the ethernet controller configuration with that from the BIOS ROM.

Restart your computer. If the configuration was suitable for your computer, your ethernet controller should now be functional.

If the ethernet controller still does not work, try using AFUWIN to flash the corresponding RomHole on your computer (use /? and consult the PDF within the suitable AFUWIN folder of the collection to see the suitable parameter for doing so).

DISCLAIMER:

DISCLAIMER OF WARRANTY
YOU ACKNOWLEDGE AND AGREE THAT THE ABOVE PROCEDURE (THE "PROCEDURE") IS PROVIDED "AS IS" AND WITHOUT WARRANTY OF ANY KIND. ALL WARRANTIES, CONDITIONS, REPRESENTATIONS, INDEMNITIES AND GUARANTEES WITH RESPECT TO THE PROCEDURE, WHETHER EXPRESS OR IMPLIED, ARISING BY LAW, CUSTOM, PRIOR ORAL OR WRITTEN STATEMENTS BY HHSOFT OR OTHERWISE (INCLUDING, BUT NOT LIMITED TO ANY WARRANTY OF MERCHANTABILITY, SATISFACTORY QUALITY, FITNESS FOR PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT) ARE HEREBY OVERRIDDEN, EXCLUDED AND DISCLAIMED.

DISCLAIMER OF DAMAGES
UNDER NO CIRCUMSTANCES WILL HHSOFT, ITS LICENSORS OR ITS OR THEIR RELATED COMPANIES BE LIABLE TO YOU FOR ANY DIRECT, CONSEQUENTIAL, INDIRECT OR SPECIAL, PUNITIVE OR INCIDENTAL DAMAGES RESULTING FROM YOUR USE OF THE PROCEDURE AS SPECIFIED ABOVE, WHETHER FORESEEABLE OR UNFORESEEABLE, BASED ON YOUR CLAIMS OR THE CLAIMS OF ANY THIRD PARTY, WHETHER BASED ON THIS AGREEMENT, ANY COMMITMENT PERFORMED OR UNDERTAKEN UNDER ON OR IN CONNECTION WITH THIS AGREEMENT OR OTHERWISE.

BIOS / UEFI Flashing Utilties Collection for AMI, Award, Phoenix, Insyde, Dell

BIOS / UEFI Flashing Utilities Collection:

The collection below contains the following utilities (various versions for American Megatrends [AMI], Award, Phoenix, Dell, Insyde BIOS and EFI platforms):

AFUWIN
AFUDOS
AFUEFI
AMIBCP
AMIMM
AMIDEWIN
AMIDEDOS
AMISCE (SCEWIN, SCEDOS, AMISCEW)
DMIEDIT
DMI16
AFUMFGWIN
SAFUWIN (HP)
MMTOOL
CBROM
AwardTool
AMIFLASH
AWDFLASH
CBROM32
MODBIN6
WinFlash
PhoenixTool (AndyP)
XSearch
BFlash
WinPhlash
PhoenixBIOSEditor
SYNCMOS
WinCrisis

Download: Google Drive.

American Megatrends (AMI) UEFI BIOS [Aptio] Recovery: Recover Bricked PC With No Floppy Disk Drive Showing Nothing On Screen While Powered On

American Megatrends (AMI) UEFI BIOS [Aptio] Recovery: Recover Bricked PC With No Floppy Disk Drive Showing Nothing On Screen While Powered On:

NOTE: This guide is for UEFI AMI Aptio BIOS only. For UEFI BIOS (AMI Aptio), the recovery BIOS file name is not necessarily AMIBOOT.ROM. You will need to use the steps below to determine the correct filename for your system.

Another version of this guide is available for non-UEFI AMI BIOS here.

You will need:

1. USB flash drive (preferably an older one with <= 4 GB capacity and with access indicator light)
2. BIOS ROM file from your device manufacturer
3. Working computer to prepare recovery flash drive
4. AndyP's PhoenixTool - This tool requires you to install Microsoft .NET Framework 4.7 or newer beforehand. You can download a copy of Version 2.73 at DataFileHost | Mega.nz. (SHA1 hash: 203FDE92728B501BDAFA19D26EDBED57E3ED7B4C). Find more details regarding this tool here: http://bit.ly/PhoenixTool.

Important Note: Please back up all files on the USB flash drive you will be using to recover the BIOS. All files will be erased when you format the flash drive.
There are multiple guides on the internet that step you through recovering the BIOS on an AMI-based PC. However, most of them only have detailed steps for recovering from a floppy disk or CD, and are mostly outdated. For instance, bricked all-in-one PCs typically will not issue any beep codes or beep during BIOS recovery.

There are several important things you should be aware of when using a USB flash drive for BIOS recovery:
1. This may not work at all on your bricked PC if its BIOS does not contain a boot block or it is corrupted/overwritten, or if it does not support USB flash drive recovery.
2. Your USB drive must be connected to one of the ports on the PC, not via a USB hub. Some PCs require you to connect the USB drive to a specific USB port - you may have to try each one and find out.
3. A USB flash drive with an access indicator light is recommended. Often, a bricked computer will not show anything on screen while the BIOS recovery is happening. The light on the USB will tell you whether the BIOS recovery is occurring.

Steps to follow:

1. Prepare the USB flash drive. First, format the drive as FAT16 (as FAT32 will not always work) using this guide (if your drive capacity is 4 GB or less, you don't have to resize the partition and can proceed straight to formatting as FAT16 - this is a different option from FAT32). All data on the USB drive will be erased.
2. Extract and copy the BIOS ROM file to the root of the USB flash drive from the device manufacturer's support page.
3. Download and run AndyP's PhoenixTool (run PhoenixTool.exe). Open the BIOS ROM file in the tool. Then, wait for the tool to process the file. Eventually, it will tell you the recovery filename. Rename the file to the name given by the tool (you may have to show all file extensions in Folder Options). (Note: If the tool gave you multiple filenames, make several copies of the BIOS ROM file and rename each copy to each of the filenames).
4. Make sure the bricked PC is plugged in and powered off. Insert the USB flash drive into one of the USB ports.
5. Attach a USB or PS/2 keyboard to the PC. PS/2 keyboard is preferred as it will be recognized sooner by the BIOS.
6. Press and hold the CTRL and HOME keys on the keyboard as you press the power button on the PC.
7. Keep holding down these keys until the USB drive indicator light has started flashing for several seconds (or for at least 5 seconds if your USB drive has no indicator light).
8. Wait up to 3 minutes. The computer will program the BIOS chip and automatically restart once recovery is complete. You may hear beeps while the BIOS is being recovered, but this is not always the case. For larger BIOS ROM images, the recovery process will take longer. Note: Your computer may not necessarily restart automatically at the end of the recovery process. If so, wait 15 minutes before restarting the computer yourself.
9. The computer will restart automatically and start up if recovery is successful.

Troubleshooting:

- Did you format the USB drive as FAT16?
- Did you try different ports on the computer?
- Did you try older USB drives?
- Is your USB drive USB 2.0 and older?
- Did you clear the CMOS on the computer by unplugging the computer, removing the CMOS battery and pressing power button for 5 seconds?
- Did you disconnect all other peripherals and drives?
- Is your monitor working properly?
- Did you download the correct version BIOS from your manufacturer?
- Did you extract the BIOS ROM file only and rename it correctly (showed all file extensions to be sure)?

Did you find the above guide useful? If so, share it with your friends. Comments on how to improve the guide are welcome below.

Sources (for ISO-9660 CD/Floppy Disk BIOS recovery methods and methods for recovering other brand BIOSes):

https://www.biostar.com.tw/app/en/support/faq_content.php?S_ID=392
https://forum-en.msi.com/faq/article/how-to-recover-the-bios
https://www.techsupportforum.com/forums/f15/bad-bios-checksum-need-hpbios-rom-62613.html

Fix Windows Update Standalone Installer getting stuck at "Searching for updates on this computer"

How to fix Windows Update Standalone Installer getting stuck at "Searching for updates on this computer" when you try to install a .MSU update:

While installing a standalone .MSU update for Windows Vista or newer, you may encounter Windows Update Standalone Installer seemingly get stuck at "Searching for updates on this computer". This can go on for 15 to 45 minutes, taking even longer in some circumstances e.g. your computer is not fully up-to-date.

To fix this, follow the steps below:

1. First, open Windows Update and see whether it is currently downloading and/or installing updates, or you have updates available for installation.
2. Once you are sure that neither of the above are true, disconnect your computer from the internet.
3. Then, open a Command Prompt window as administrator and enter the following commands:
   - taskkill /im wusa.exe /f
   - net stop wuauserv
4. Go back and try to install the .MSU file again. The "Searching for updates on this computer" step should now complete in less than 5 minutes.

The above procedure worked on Windows Vista SP2 and Windows 7 SP1.

Did you find the above guide useful? If so, share it with your friends. Comments on how to improve the guide are welcome below.

American Megatrends (AMI) BIOS [AMIBIOS8] Recovery: Recover Bricked PC With No Floppy Disk Drive Showing Nothing On Screen While Powered On

American Megatrends (AMI) BIOS [AMIBIOS8] Recovery: Recover Bricked PC With No Floppy Disk Drive Showing Nothing On Screen While Powered On:

NOTE: This guide is for legacy non-UEFI AMI BIOS. UEFI BIOS (AMI Aptio) has a different recovery procedure as the file name is not necessarily AMIBOOT.ROM.

Another version of this guide is available for UEFI AMI BIOS (AMI Aptio) here.

You will need:

1. USB flash drive (preferably an older one with <= 4 GB capacity and with access indicator light)
2. BIOS ROM file from your device manufacturer
3. Working computer to prepare recovery flash drive

Important Note: Please back up all files on the USB flash drive you will be using to recover the BIOS. All files will be erased when you format the flash drive.
There are multiple guides on the internet that step you through recovering the BIOS on an AMIBIOS-based PC. However, most of them only have detailed steps for recovering from a floppy disk or CD, and are mostly outdated. For instance, bricked all-in-one PCs typically will not issue any beep codes or beep during BIOS recovery.

There are several important things you should be aware of when using a USB flash drive for BIOS recovery:
1. This may not work at all on your bricked PC if its BIOS does not contain a boot block or it is corrupted/overwritten, or if it does not support USB flash drive recovery.
2. Your USB drive must be connected to one of the ports on the PC, not via a USB hub. Some PCs require you to connect the USB drive to a specific USB port - you may have to try each one and find out.
3. A USB flash drive with an access indicator light is recommended. Often, a bricked computer will not show anything on screen while the BIOS recovery is happening. The light on the USB will tell you whether the BIOS recovery is occurring.

Steps to follow:

1. Prepare the USB flash drive. First, format the drive as FAT16 (as FAT32 will not always work) using this guide (if your drive capacity is 4 GB or less, you don't have to resize the partition and can proceed straight to formatting as FAT16 - this is a different option from FAT32). All data on the USB drive will be erased.
2. Extract and copy the BIOS ROM file to the root of the USB flash drive from the device manufacturer's support page.
3. Rename the file to AMIBOOT.ROM (you may have to show all file extensions in Folder Options).
   - (For HP computers only: Make a copy of this file in the same directory. Rename it as HPBIOS.ROM).
4. Make sure the bricked PC is plugged in and powered off. Insert the USB flash drive into one of the USB ports.
5. Attach a USB or PS/2 keyboard to the PC. PS/2 keyboard is preferred as it will be recognized sooner by the BIOS.
6. Press and hold the CTRL and HOME keys on the keyboard as you press the power button on the PC.
7. Keep holding down these keys until the USB drive indicator light has started flashing for several seconds (or for at least 5 seconds if your USB drive has no indicator light).
8. Wait up to 3 minutes. The computer will program the BIOS chip and automatically restart once recovery is complete. You may hear beeps while the BIOS is being recovered, but this is not always the case.
9. The computer will restart automatically and start up if recovery is successful.

Troubleshooting:

- Did you format the USB drive as FAT16?
- Did you try different ports on the computer?
- Did you try older USB drives?
- Is your USB drive USB 2.0 and older?
- Did you clear the CMOS on the computer by unplugging the computer, removing the CMOS battery and pressing power button for 5 seconds?
- Did you disconnect all other peripherals and drives?
- Is your monitor working properly?
- Did you download the correct version BIOS from your manufacturer?
- Did you extract the BIOS ROM file only and rename it correctly (showed all file extensions to be sure)?

The above procedure worked correctly on Sony VGC-JS290J and HP TouchSmart 610-1020a all-in-one PCs.

Did you find the above guide useful? If so, share it with your friends. Comments on how to improve the guide are welcome below.

Sources (for ISO-9660 CD/Floppy Disk BIOS recovery methods and methods for recovering other brand BIOSes):

https://www.biostar.com.tw/app/en/support/faq_content.php?S_ID=392
https://forum-en.msi.com/faq/article/how-to-recover-the-bios
https://www.techsupportforum.com/forums/f15/bad-bios-checksum-need-hpbios-rom-62613.html

Format Large USB Drive As FAT16 In Windows

Format Large USB Drive As FAT16:

Maximum Volume and File Sizes for FAT16/FAT32/exFAT:
FAT16: Max volume size: 4 GB, Max file size: 2 GB.
FAT32: Max volume size: 2 TB, Max file size: 4 GB.
exFAT: Max volume size: 128 PB, Max file size: 16 EB.

If your USB flash drive partition size is larger than 4 GB, you need to resize it to 4 GB to format it as FAT16.

Steps to follow:

We will use DiskPart to Resize USB partition to 4 GB.
Warning: Back up ALL data on the USB as it will be completely erased by the formatting tool!

For each of the following commands, press ENTER on your keyboard after typing the command (denoted in this font).

1. Insert the USB to be formatted as FAT16.

2. Open a Command Prompt window as administrator.
   - On Windows XP: Log in as administrator. Press Windows key + R to open Run. Type cmd to open.
   - On Windows Vista and newer: Press the Windows key. Type cmd and wait for the option to appear. Right-click and select Run as Administrator. Click Yes when prompted by UAC.

3. Type DISKPART in this window to launch Microsoft DiskPart tool.

4. In the window, type: list disk

5. An example output is shown below:

DISKPART> list disk
 
  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          238 GB  1024 KB        *
  Disk 1    Online         7538 MB      0 B
6. In the above example, the USB drive is Disk 1 (7538 MB). This may NOT be in your case! Identify the disk # by the size. If you are unsure, select one of the disks with the following command (substitute # with the disk number): SELECT DISK # then type DETAIL DISK to see the disk name and assigned drive letters.

7. Select the correct disk by typing SELECT DISK # to select it. An example output is shown below:

DISKPART> select disk 1

Disk 1 is now the selected disk.

8. Type LIST PARTITION to double-check that you have selected the right disk. An example output is shown below:

DISKPART> list partition

  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Primary           7538 MB  1024 KB
9. Once you are sure you have selected the right disk, type CLEAN to delete all existing partition information from the selected disk. WARNING: THIS IMMEDIATELY DELETES ALL PARTITIONS ON THAT DISK!

DISKPART> clean

DiskPart succeeded in cleaning the disk.
10. To create a 4000 MB (4 GB) partition on the now-erased USB, type CREATE PARTITION PRIMARY SIZE=4000 to create it.

DISKPART> create partition primary size=4000

DiskPart succeeded in creating the specified partition.
11. Then, we will make this partition active by typing ACTIVE.

DISKPART> active

DiskPart marked the current partition as active.
12. Type ASSIGN to assign a drive letter to the drive.

DISKPART> assign

DiskPart successfully assigned the drive letter or mount point.
13. Type EXIT to close DiskPart. The Command Prompt window should remain open.

14. If a window pops up asking you to format the disk, you can follow the prompts to format the drive via the GUI (remember to select "FAT", NOT "FAT32" under "File system"!) and skip the remaining steps of this tutorial (you may type EXIT to close the Command Prompt window). Otherwise, continue below.

15. Now, we will format this newly-created partition as FAT16. First, open My Computer/Computer to see the drive letter of the USB drive.

16. Go back to the Command Prompt window. Type FORMAT X: /FS:FAT /Q where X is the drive letter of your USB, then type Y to confirm. This may take several minutes to complete.

17. The USB drive is now formatted as FAT16. Type EXIT to close the Command Prompt window.

If you would now like to return your USB drive partition back to FAT32 (or NTFS) to allow you to use the USB drive's full capacity again, just repeat the steps above, except at Step 10, where you will now type CREATE PARTITION PRIMARY (without the SIZE parameter) to create a single partition spanning the entire disk.

Did you found the above guide useful? If so, share it with your friends. Comments on how to improve the guide are welcome below.

Improved and extended steps from https://www.instructables.com/id/Format-USB-Flash-Drive-to-FATFAT16-not-FAT32/.