UEFI Windows 10 USB Will Not Boot - Stuck in Splash Screen

Dec 24, 2018
1
0
10
0
I have just assembled a new PC build with the following:

Motherboard: Gigabyte Z390 Aorus Pro Wifi
CPU: i7-8700k
Cooling: Cooler Master Masterliquid ML360R
RAM: Corsair Vengeance 16GB 3200MHz
OS Drive: Samsung 970 EVO NVMe
Graphics: Gigabyte RTX-2080
OS Media: Windows 10 Home USB (purchased not made)

When attempting to boot from the USB, a black screen with white text appears, titled Windows Boot Manager, and prompts to choose between Windows Setup (64-bit) and Windows Setup (32-bit). The screen allows an F8 press to specify an advanced option for this choice.

After choosing Windows Setup (64-bit), a "Loading Files..." progress bar appears and fills over time. Once complete, the screen blacks out and the Aorus splash screen appears. This screen remains indefinitely.

I have configured my BIOS as follows:
Boot Option #1: UEFI: KDI-MSFTWindows 10 PMAP, Partition 1
Boot Option #2: Disabled
Boot Option #3: Disabled
Fast Boot: Disabled
Storage Boot Option Control: UEFI
Other PCI devices: UEFI

The Peripherals>NVMe Configuration shows my EVO 970 is installed.

I have tried the following, to no avail:
- Removed VGA during boot and used MOBO HDMI for display
- Tried to boot from 1 RAM stick in each slot
- Repeated the 1 RAM boot attempt in each slot with 2nd RAM stick
- Booting from each USB port on the MOBO
- Moving to the other M.2 socket for the EVO 970
- Change the RAM speed to 3200 Hz from 2133 Hz in Advanced Memory Settings
- Shorting CMOS terminals to reset BIOS to default
- Removed all components and rebuilt
- Reseated all connections
- Verified proper connection of CPU cooler fans and pump

I am about to create a new boot USB and attempt to boot from that.

Does anyone have any suggestions or experience with this issue?

Thank you for your time and assistance.

Update: Prior to this issue, I could not get verification of post. I removed all components, checked CPU socket pins for bent pins and correct CPU orientation, verified proper application of thermal paste, and reassembled. This resolved my post issue and brings us to the current scenario.

2nd Update: Just pulled out my Elementary OS boot USB and the build booted up fine. The Windows boot USB is now the suspect. Currently trying to format a new boot USB using the Windows Media Tool.

3rd Update: As answered below, the problem was resolved by creating my own boot USB using the Windows Media Tool. I used a 16GB flash drive for the process and had no issues. Hopefully this experience helps others if they find themselves in this scenario.
 

Vic 40

Titan
Herald

Have had experience with that and making your own usb stick via their own way will likely sort it out.
https://www.microsoft.com/en-us/software-download/windows10/?tduid=
 

Vic 40

Titan
Herald

Have had experience with that and making your own usb stick via their own way will likely sort it out.
https://www.microsoft.com/en-us/software-download/windows10/?tduid=
 

ASK THE COMMUNITY

TRENDING THREADS