Windows 10: Can't access Asus P5LD2 BIOS after Windows 10 update Threshold 2 10586

It's due to the fact that after uninstalling the update, it defers the upgrade until the next Operating System release. I reverted a Windows 10 machine back to Windows 7, and the free upgrade was no longer an option until 10586 was released. They probably assume if you revert, you don't the OS again.

 

So you forget how to enter the BIOS setup, then accuse Microsoft. Sweet.

 

I've testing this more than a dozen times now.

* Disable Fast Startup in Windows Control Panel Power settings and completely power the system down. Do a cold reboot, hit DEL at post beep. System boots into BIOS setup.

* Boot back into Windows 10 and re-enable Fast Startup. Completely power the system down. Do a cold reboot, hit DEL at post beep. System boots into Windows 10.

If anyone can explain how that happens without Windows 10 modifying the boot order in BIOS they''ll have my rapt attention.

 

Fast startup is designed to do that. That's why on UEFI systems they have the fast boot options that allow between 2 to 10 second boot from power on to desktop. Non UEFI systems are the same way, except they go through a full post, but bypass the ability to enter BIOS because you are basically "resuming Windows". When resuming from the Hiberfil.sys file, you won't be able to boot into BIOS with fast startup enabled. You will need to either restart to get into BIOS, or just turn fast startup off if you require frequent BIOS access.

 

Windows 10 has serious compatibility issues with Socket 775 motherboards (at least those with nforce chipsets). These issues include (but are not limited to):
- TDR Errors falsely referencing to graphic cards
- failures while awaking from sleep/hibernate states
- southbridge only freezes (mouse and keyboard, if you then newly connect usb mouse it works and system runs).
- whole system freezes; this happens after the last cumulative update
All problems are related to extremely bad Win10 code for ACPI/SMBus on older systems which are 100% reliable in Windows 7. And yes, the last cumulative update makes things even worse, hardly tuned-up systems suddenly freeze completely.

So the problem may be caused by frozen keyboard which is revived only by Windows initialization, or by complete shutdown. Not necessarily a user mistake.

Furthermore, Windows does not modify BIOS. Instead, upon startup Windows takes control over system and devices, so BIOS is no longer needed - until next boot.

My recommendations:
- have other usb mouse and try to connect it AFTER keyboard/mouse failure
- assign Hibernate function to Power button; you can use it to hibernate/awake system (it resets peripherals) without loss of data.

You may try original chipset drivers for Windows 7 too. Good luck, my experience is rather bad. Socket 775 is definitely dead now.

 

I've tested many socket 775 Boards on Windows 10 and have not had any issues.

I don't have any with the NVIDIA Chipset though. I've worked on the P35 and P17 Chipset and ICH7, ICH9R, and haven't had issues.

 

Ran into a few problems testing the Asus Win10, and ended up restoring the drive image I'd made. It ended up being another good dry run if I have to do it on the Toshiba. So I haven't updated it yet.

But after booting up the restored copy, I found something very interesting that contradicts the initial installation. No longer does Fast Startup keep me from entering BIOS at boot with the DEL key. Not from a cold boot or a warm reboot. In fact Fast Startup didn't work at all.

Scratched my head for a while, and decided to actually press the power button on the tower instead of shutting down via the Start Menu. Then Windows went into its pseudo Fast Startup / hibernation function.

If I reboot via the Start Menu it takes 15 seconds to shut down and 2 min 30 seconds to boot to the desktop. Powering down with the power button takes 30 seconds to shut down and 50 to start up.

So I got Fast Startup working again in another incarnation, and it's still the reason I'm not getting into BIOS when its working by the physical button. But it's just frustrating not knowing how things got set the 1st time around that resulted in Fast Startup working from the Start Menu power menu.

 

I didn't run into any problems upgrading to 10586 lmaneke. I had thought media creation tool would just update files, but it basically installed the complete Windows 10 10586 over 10240. It took 3 hours to download the compete ISO, another 2 hours to download updates and about an hour to finish installation. And it left about 20GB in Windows.old, $Windows~BT, and $Windows~WS folders I'll just leave probably. I understand they might be automatically removed after 30 days.

10586 runs just as fast if not perhaps faster than 10586. It fixed the sketchy Elan touchpad drivers that made scrolling jittery in some programs. And I'm not longer having the display problem that left Firefox and a couple other programs with blank areas of their windows after minimizing and maximizing them again. Hibernation seems to be more reliable too. That's been sketchy for me in Windows all the way back to Win2000.

And the upgrade didn't create any extra partitions as you pointed out people have seen. I checked that running GParted after booting into Linux. Funny thing I noticed a while back is that Win10 from the factory had created a 4th 16MB msfres partition that isn't visible in Disk Management or any other Windows partitioning software I've used. That intrigues me. Can't wonder if it's related to the other new security functions Win10 has instituted.

So far things are looking great. Thanks for your feedback on this lmaneke.