Jump to content

BIOS Settings Might Affect Windows 10 2004 Update Success

By a lot of Blood, Sweat, Tears, Some Thunder of Thor's Hammer and a lot of crying, we got Update 2004 for Windows 10 to work though it required a fresh install and a BIOS update.
 
It's unclear if the BIOS update really helped, because we had one successful Boot before the update, and we also had failed boots after the BIOS update. But I kept messing with the settings until it started working. Here's what the settings are (NOTE: These are for a Socket TR4 ASUS ROG Zenith Extreme so your mileage may vary):
 
Set Optimized Defaults
Fast Boot = Disabled
 
Boot Config
  • Boot Logo = Full Screen
  • Option ROM Messages = Disable
  • Interrupt 19 Capture = Disabled
Boot CSM
  • Launch CSM = Enabled
  • Boot Device Control = UEFI Only
  • Boot Network Device = Ignore
  • Boot from Storage Device = UEFI Drive First
  • Boot from PCI-E Device = UEFI Drive First
Secure Boot
  • OS Type = Other OS
 
Boot Option Priorities = UEFI: USB Device (we were using Windows 10 installer on a USB stick)
 
The USB disk had a copy of Windows 10 2004 on it (revision 19041.264) and made with Windows Media Creation Tool.
 
What's strange is the CSM is on, but set to boot EFI only. At the same time, the BIOS display is set to the ROG logo, but not allowed to be overlaid with the spinning dots. It replaces the ROG logo with the default blue Windows logo with spinning dots.
 
I didn't change anything else.
 
So, it was:
 
1. USB disk failed to boot a bunch of times, except once, which told me it could work.
2. I updated the BIOS and loaded the Defaults.
3. USB disk continued to fail to boot, but I continued to mess around with the above settings.
4. When I tried the above settings, I started getting 100% reliable boots.
5. If I changed one of the above settings, it started failing again.
 
There was nothing on the drives for the install, I did a wipe of the disk, so the C Drive had no effect on this. Now that we have Windows 10 Pro 64-bit installed with Update 2004 working we changed the BIOS setting back to our regular settings and everything works. We have no way of really testing this but it kinda looks like BIOS settings maybe have an effect on installing this update. I hope this maybe helps anyone else having problems getting this update installed. It might also make a good subject for an LTT video.
--Michael "TheZorch" Haney
Content Creator for Zorch Central and Gamers Bay
 
Personal/Streaming Rig
  • AMD Ryzen 5 3600
  • 32 GB DDR4
  • 1 TB Intel 660p SSD
  • Gigabyte Radeon RX 5600 XT Windforce OC
  • Thermaltake 600 W 80+ Gold
Adobe Editing Rig
  • AMD Threadripper 1950X
  • 32 GB DDR4
  • 512 GB Samsung 960 Pro
  • x2 SLI Nvidia GeForce 1080 ti
  • Corsair 1200 W 80+ Platinum
Link to comment
Share on other sites

Link to post
Share on other sites

I have to admit touch wood i've not had any issues with Windows 10 and the 2004 update.

MAIN PC (Beast) - Asus ROG Crosshair Hero VII WIFI  with BIOS 4703, AMD Ryzen R9 3900XT + Corsair H115i Pro RGB XT Cooling, 32GB G.Skill 3200Mhz 16,18,18,38 1.35v DDR4, Inno3d HerculeZ Design Nvidia GTX 1080 X2 8GB GDDR5,  1 x Samsung U28E590D & 1 x Samsung U32J59XUQ 3840 x 2160 4K, 1 x Samsung Evo 970 Evo Plus NVME PCI-E 1TB, 1 x Samsung Evo 850 250GB, 1 X Sandisk Ultra II SSD 240GB + 2 X 3TB Seagate Barracuda SATA III, 1 x LG BH16NS40 16x BR\DVDRW, ICYBOX IB3740-C31 & ICYBOX IB3640-03,  MZHOU 7 Ports PCIe USB 3.0 Card, 1 x XIAOLO 2.5G Intel I225V Ethernet Card, 2 x UGREEN Hard Drive Enclosure 3.5 inch External SATA Disk Caddy Reader USB 3.0 2.5 3.5 HDD SSD 16TB UASP Case Dock Station With 12V 2A Power Adapter For Windows with 6TB Seagate Barracuda SATA III, Corsair Obsidian 750D Wind Force Edition Case + 5 Corsair ML140 140mm Case Fans, EVGA 750 g3 750w Gold 80+ PSU, Logitech MX Vertical Mouse, Logitech MX Vertical & MX Ergo Trackball Mouse using same USB unifying device, Microsoft Ergonomic Keyboard, Windows 11 Pro x64 Retail, Synology ds215j NAS + 1x3TB WD Reds connected to a 6TB Seagate USB 3.0 Backup Plus Hub, Blue Yeti Microphone, Logitech C922 Pro HD,  Logitech C920 Pro HD, Bit Defender Total Security 2021.

 

Second PC (Cyclops) - MSI 990FXA Gaming, AMD FX 8370 4Ghz, Corsair 16GB Vengeance Red 9-9-9-24 1600Mhz, Arctic Cooling Freezer 13, Asus Strix 1050TI 4GB, 1 X Acer 27" Full HD Monitor, 1 X Sandisk Ultra II SSD 240GB, 1 x Samsung Evo 850 250GB, 2 X Seagate Barracuda 2TB, 1 X WD Black 2TB, 1 x ASUS 16x DVDRW, X-Case Eagle III Case, 3 X Corsair AF 120 Case Fans, EVGA 850 G2 80+ Gold + PSU, Logitech MX Master Mouse, Corsair K30 Keyboard, Logitech C920 Webcam, R0DE NT1-A Microphone, Scarlet 212 Audio Interface (Revision 2), Windows 10 Pro X64 Retail, Bit Defender Total Security 2021, 2TB Seagate Expansion USB Hard Drive.

 

Third PC (Old Trustie) - Acer Aspire M3400, OEM Mainboard, AMD FX Athlon II X3 425 2.7Ghz, 16GB Corsair Value 1600Mhz Ram, OEM CPU Cooler, AMD R7 260 2GB GPU, 1 X Acer 27" Full HD Monitor, 1 X Sandisk Ultra II SSD 240GB, 2TB Samsung SATA III, 1 X OEM 16X DVDRW, 1 X Acer OEM Case, 1 X Corsair AF120 Case Can, Corsair CX500 Bronze+ CPU, Logitech MX Master Mouse, Corsair K30 Keyboard, Windows 10 Home X64 OEM, Logitech C920 Webcam, Bit Defender Total Security 2021.

 

Printers Include - Canon MG5750, Canon, IP8750,  Canon Pixma Mega tank G5050 & 2 X Samsung Xpress C410W.

 

1 X Zexrow Xbox360 Wired Game Controller.

 

TP Link Archer AX6000 Cable Router Wifi6 with a Virgin Media Hub 4.0 in Modem only mode running 1GB Fibre internet.

 

Samsung Galaxy S21+ 256GB Mobile Phone.

 

Internet Speed.....

https://www.speedtest.net/result/9935039193

Link to comment
Share on other sites

Link to post
Share on other sites

My research into our issue found that running into problems with this update is completely RANDOM. Two people with the exact same specs can install Windows 10 on their machines. One has no issues and everything works. The other has nothing but constant problems. It baffles me as to why but it is true. 

 

The problem with Microsoft, in their purge of staff years ago their QA Team has been massively reduced. Now, you can't go a month without seeing articles about how a new Windows update breaks something. It would be funny as hell if weren't so sad. 

--Michael "TheZorch" Haney
Content Creator for Zorch Central and Gamers Bay
 
Personal/Streaming Rig
  • AMD Ryzen 5 3600
  • 32 GB DDR4
  • 1 TB Intel 660p SSD
  • Gigabyte Radeon RX 5600 XT Windforce OC
  • Thermaltake 600 W 80+ Gold
Adobe Editing Rig
  • AMD Threadripper 1950X
  • 32 GB DDR4
  • 512 GB Samsung 960 Pro
  • x2 SLI Nvidia GeForce 1080 ti
  • Corsair 1200 W 80+ Platinum
Link to comment
Share on other sites

Link to post
Share on other sites

  • 7 months later...
On 7/15/2020 at 3:30 AM, TheZorch said:
By a lot of Blood, Sweat, Tears, Some Thunder of Thor's Hammer and a lot of crying, we got Update 2004 for Windows 10 to work though it required a fresh install and a BIOS update.
 
It's unclear if the BIOS update really helped, because we had one successful Boot before the update, and we also had failed boots after the BIOS update. But I kept messing with the settings until it started working. Here's what the settings are (NOTE: These are for a Socket TR4 ASUS ROG Zenith Extreme so your mileage may vary):
 
Set Optimized Defaults
Fast Boot = Disabled
 
Boot Config
  • Boot Logo = Full Screen
  • Option ROM Messages = Disable
  • Interrupt 19 Capture = Disabled
Boot CSM
  • Launch CSM = Enabled
  • Boot Device Control = UEFI Only
  • Boot Network Device = Ignore
  • Boot from Storage Device = UEFI Drive First
  • Boot from PCI-E Device = UEFI Drive First
Secure Boot
  • OS Type = Other OS
 
Boot Option Priorities = UEFI: USB Device (we were using Windows 10 installer on a USB stick)
 
The USB disk had a copy of Windows 10 2004 on it (revision 19041.264) and made with Windows Media Creation Tool.
 
What's strange is the CSM is on, but set to boot EFI only. At the same time, the BIOS display is set to the ROG logo, but not allowed to be overlaid with the spinning dots. It replaces the ROG logo with the default blue Windows logo with spinning dots.
 
I didn't change anything else.
 
So, it was:
 
1. USB disk failed to boot a bunch of times, except once, which told me it could work.
2. I updated the BIOS and loaded the Defaults.
3. USB disk continued to fail to boot, but I continued to mess around with the above settings.
4. When I tried the above settings, I started getting 100% reliable boots.
5. If I changed one of the above settings, it started failing again.
 
There was nothing on the drives for the install, I did a wipe of the disk, so the C Drive had no effect on this. Now that we have Windows 10 Pro 64-bit installed with Update 2004 working we changed the BIOS setting back to our regular settings and everything works. We have no way of really testing this but it kinda looks like BIOS settings maybe have an effect on installing this update. I hope this maybe helps anyone else having problems getting this update installed. It might also make a good subject for an LTT video.

I literally created an account just so I could say thank you for posting this solution!

 

I just spent the whole day trying to install Windows using UEFI, with multiple usb drives and all sorts of settings. This finally helped. Thank you!

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×