F5F Stay Refreshed Hardware Desktop AB350M - Gaming 3 motherboard fails to boot USB flash drive using Windows installer tool

AB350M - Gaming 3 motherboard fails to boot USB flash drive using Windows installer tool

AB350M - Gaming 3 motherboard fails to boot USB flash drive using Windows installer tool

K
Kaisetsu
Senior Member
651
08-22-2016, 07:27 PM
#1
I recently returned from my first semester at college and left my tower at home. I planned a complete overhaul of my hard drives and reinstalled Windows 10. I used a 14.5 GB USB flash drive with the Windows Installer tool, but it didn’t boot successfully. The drive appears to work, yet whenever I try to start it via F12 using the Gigabyte BIOS, it loops back to the normal Windows 10 setup. I tested both UEFI and legacy boot settings without success. I also swapped USB ports from 3.0 to 3.1 and then to the standard 2.0 slots on my motherboard, but nothing changed. The drive is formatted with FAT32, and it worked fine on my laptop. Additionally, the "Reset this PC" feature failed because it showed an error: "could not find the recovery environment." I ran the command `reagentc /enable` to try enabling it, but it remains disabled—even though Disk Management lists a 488 MB recovery partition. At this stage, I’m exhausted and unsure how to properly format my computer and drives again to improve performance.
K
Kaisetsu
08-22-2016, 07:27 PM #1

I recently returned from my first semester at college and left my tower at home. I planned a complete overhaul of my hard drives and reinstalled Windows 10. I used a 14.5 GB USB flash drive with the Windows Installer tool, but it didn’t boot successfully. The drive appears to work, yet whenever I try to start it via F12 using the Gigabyte BIOS, it loops back to the normal Windows 10 setup. I tested both UEFI and legacy boot settings without success. I also swapped USB ports from 3.0 to 3.1 and then to the standard 2.0 slots on my motherboard, but nothing changed. The drive is formatted with FAT32, and it worked fine on my laptop. Additionally, the "Reset this PC" feature failed because it showed an error: "could not find the recovery environment." I ran the command `reagentc /enable` to try enabling it, but it remains disabled—even though Disk Management lists a 488 MB recovery partition. At this stage, I’m exhausted and unsure how to properly format my computer and drives again to improve performance.

_
_boat
Member
127
08-22-2016, 11:35 PM
#2
It seems the file system might be set to FAT32. Windows 10 works best with NTFS, so consider creating a bootable NTFS drive.
_
_boat
08-22-2016, 11:35 PM #2

It seems the file system might be set to FAT32. Windows 10 works best with NTFS, so consider creating a bootable NTFS drive.

Z
Zarwati
Junior Member
4
08-28-2016, 11:03 PM
#3
Here are the details rephrased:

- Processor: AB350-Gaming with a 3 GHz clock speed
- CPU: Ryzen 1600 GTX
- Graphics: 1660 TI
- RAM: 24 GB
- Storage: 1 TB for gaming, 2 TB for Windows 10
- Operating System: Windows 10
Z
Zarwati
08-28-2016, 11:03 PM #3

Here are the details rephrased:

- Processor: AB350-Gaming with a 3 GHz clock speed
- CPU: Ryzen 1600 GTX
- Graphics: 1660 TI
- RAM: 24 GB
- Storage: 1 TB for gaming, 2 TB for Windows 10
- Operating System: Windows 10

T
TheAdamYT
Member
158
08-30-2016, 11:54 PM
#4
Alright, let's give it a shot.
T
TheAdamYT
08-30-2016, 11:54 PM #4

Alright, let's give it a shot.

L
luluj2015
Member
188
09-18-2016, 07:44 PM
#5
It doesn't appear to function properly. Attempted both legacy and UEFI boot settings.
L
luluj2015
09-18-2016, 07:44 PM #5

It doesn't appear to function properly. Attempted both legacy and UEFI boot settings.

S
StreetHobo
Senior Member
568
09-23-2016, 11:01 PM
#6
I faced a similar problem too. It was fixed by updating the BIOS two times. Initially, I needed to reach version 31 for better USB support, then installed the 51b edition. This allowed me to configure everything in UEFI mode and successfully booted from USB. When I first attempted to flash the BIOS to the newest release, it reported an error, which is why a second update was necessary.
S
StreetHobo
09-23-2016, 11:01 PM #6

I faced a similar problem too. It was fixed by updating the BIOS two times. Initially, I needed to reach version 31 for better USB support, then installed the 51b edition. This allowed me to configure everything in UEFI mode and successfully booted from USB. When I first attempted to flash the BIOS to the newest release, it reported an error, which is why a second update was necessary.

S
Stick_xx
Junior Member
19
09-26-2016, 04:49 PM
#7
Did you fix the issue I’m facing? The same problem persists with a brand-new USB created from the media tool—it functions on other PCs/MBs but keeps looping and returning to BIOS on the AB 350. I’m unable to make it bootable, and I’ve tried switching between UEFI legacy CSM ON/OFF without success.
S
Stick_xx
09-26-2016, 04:49 PM #7

Did you fix the issue I’m facing? The same problem persists with a brand-new USB created from the media tool—it functions on other PCs/MBs but keeps looping and returning to BIOS on the AB 350. I’m unable to make it bootable, and I’ve tried switching between UEFI legacy CSM ON/OFF without success.