New
#190
No. Remember, the BIOS doesn't need an OS, the OS needs the BIOS. And the BIOS deals with "hardware", not software. So unless the hardware was damaged or moved, the OS shouldn't say what the BIOS can and can't see. That even if a drive can no longer be booted by the BIOS because the OS hosed the boot files, as long as the drive isn't damaged the BIOS will still see the drive.
Had to revert to 1909 on an older laptop since 2004 complained about not being unable to find some mysterious device driver every time it started. The update isn't being offered to it on WU anyway, so maybe it's something that will get fixed somewhere down the road.
That was exactly what I got too. But the ISO installed OK on my spare HDD, so I suspect it doesn't like some software I use in my main OS.
But why then does my BIOS over the years has changed its BIOS boot options based on different Windows releases on the same drive? Sometimes it only showed the SSD as a boot option, other times it showed the SSD and a Windows Manager boot option? There's got to be some sort of interaction somewhere ...
There's a firmware Boot setting called Secure Boot which allows you to set UEFI or Other OS as a boot option. When this morning the Windows Manager boot drive option disappeared I had to boot the SSD as Other OS to get Windows up. Only after I used Paragon HD Manager's feature to clear the UEFI cache was I able to boot using the UEFI firmware option.
Wasn't offered via WU so I dl'd it via MCT and installed this morning. It messed up some of my settings but once I redo those and clean up I might regain some space. Got a 1909 image from 2 days ago in case things go south. All in all not too shabby.
Is it possible BIOS can't see the drive because the version is not compatible with pc/laptop?
I mean we need to upgrade (or maybe downgrade) the version of the BIOS?
Sometimes it happened when we get bios upgrade from windows update.