Unsatisfying resolution, wiped windows disk, cleared partitions, and let windows do an automatic install. Interestingly it decided to install a windows boot manager alongside the Linux one.
I was going to ask if you'd checked if the windows boot drive shows as an option in the BIOS setup but you already wiped it.
Hope you backed up beforehand.
I know this is too late for you, but something like this happened to me recently, so I'm writing for the sake of anyone who might find this thread in the future.
In my case it was because the NixOS installer had booted up in legacy/BIOS mode, so grub was in BIOS mode, and it can't boot a UEFI OS (e.g. Windows 10) from that state.
In fact I couldn't get the NixOS installer to boot in EFI mode at all. Odd, as both Windows and other distros work fine. Actual installed NixOS also works, it's just the installer that fails.
So what I did was to boot a different distro's live medium (EndeavourOS, but it shouldn't matter) in EFI mode and did a manual NixOS install from there.
It probably also would have worked to just switch grub to EFI mode in the config, except I had also failed to clock that the new SSD I was installing to had an MBR partition table, so I had to nuke the original install to make it gpt anyway.
tl;dr: osprobe can find OSes on other drives just fine; what it can't do is find an EFI bootloader while in legacy mode.
NixOS
NixOS is a Linux distribution built on top of the Nix package manager. Its declarative configuration allows reliable system upgrades via several official channels of stability and size.
This community discusses NixOS, Nix, and everything related.