Categories: Technology

Windows 10, January 19 3001 and the curious case of the Y3K bug

The latest version of Windows 10 has a curious bug: does not install on computers that have a BIOS date set from January 19 3001. Carey Holzman, Youtuber and hardware enthusiast, has discovered a problem already renamed Y3K, in order to remember the Millenium bug (Y2K), a great bogeyman of late 1999.

"It seems that if your motherboard's BIOS – AMD or Intel – allows you to set the date of January 19 3001 or later, Windows 10 1909 will not complete the installation, crashing during the second restart of the process, "Holzman explained to BleepingComputer – the problem was illustrated on video on Youtube.

"Also, if the BIOS date is changed, and you restart your PC in an attempt to complete the installation of Windows 10, guess what happens? Windows 10 crashes again and when you check the BIOS date, you will see that Windows 10 sets in automatic incorrect date in your BIOS! If you change the motherboard, trying to reboot from the failed installation, it will freeze again and report the wrong installation date in the BIOS of the new motherboard ".

The bug will continue to manifest any hardware changes you make, as long as you try to boot from the storage solution where the installation of Windows 10 1909 was initially attempted. The problem was shown on Gigabyte H370 HD3 (Intel) and Gigabyte x570 Aorus Elite (AMD) motherboards, where users can freely set the date, although Gigabyte says the maximum date is 2099. Fortunately there seems to be a loophole:

  1. First set the correct date in the BIOS
  2. Restart your PC from the storage media – USB or DVD – from which you install Windows 10
  3. Clean up all the partitions on the SSD or hard disk where you want to install Windows 10 and only then start the installation process again.

Obviously the bug is little more than a curiosity, and we'll see if it will be fixed in some way. "I think Gigabyte needs to fix the BIOS of every motherboard it sells and Microsoft needs to add a date check during the initial installation process," Holzman added to BleepingComputer.

The date set in the PC BIOS has always been a problem, and setting it incorrectly can lead to malfunctions of various kinds, sometimes unpredictable, such as sites that do not load due to expired certificates. In short, better not to dabble too much in "playing" with the date in the BIOS.

Miners Hashrate

Recent Posts

Mining RTX 3070 at NiceHash: Overclocking, tuning, profitability, consumption

Mining on RTX 3070. Overclocking, tuning, profitability, consumption: If you are interested in finding more…

6 months ago

Mining GTX 1660, 1660 Ti, 1660 Super: Overclocking, settings, consumption

Mining with GTX 1660, 1660 Ti, 1660 Super. Overclocking, settings, consumption, profitability, comparisons - If…

6 months ago

Mining RTX 2070 and 2070 Super: Overclocking, profitability, consumption

Mining with RTX 2070 and 2070 Super. Overclocking, profitability, consumption, comparison What the RTX 2070…

6 months ago

Mining with RTX 3060, 3060 Ti. Limitations, overclocking, settings, consumption

Mining with RTX 3060, 3060 Ti. Limitations, overclocking, settings, consumption, profitability, comparison Let's look at…

6 months ago

Alphacool Eisblock Aurora Acryl GPX-A Sapphire – test: 2.8 GHz++ are not an issue

Alphacool Eisblock Aurora Acryl GPX-A (2022) with Sapphire Radeon RX 6950 XT Nitro+ Pure in…

6 months ago

Corporate Crypto Strategies 4.0: Leading with Bitcoin Expertise

In the ever-evolving landscape of business strategy, Bitcoin has emerged as a pivotal asset. With…

6 months ago

This website uses cookies.


Notice: ob_end_flush(): failed to send buffer of zlib output compression (1) in /home/gamefeve/bitcoinminershashrate.com/wp-includes/functions.php on line 5420

Notice: ob_end_flush(): failed to send buffer of zlib output compression (1) in /home/gamefeve/bitcoinminershashrate.com/wp-includes/functions.php on line 5420