this solution came from the above url:
bcdedit /set hypervisorlaunchtype auto
excellent advice from this url:
https://www.reddit.com/r/WindowsHelp/comments/wjtyhf/bootrec_rebuildbcd_the_requested_system_device/?rdt=64041
OK, by the look of partition’s on “Disk 1” you have 2 EFI boot partitions; this may be confusing UEFI firmware, it’s probably trying to boot from EFI boot partition with index 1 instead of EFI boot partition with index 4.
I have seen this issue happen when disk was converted from MBR to GPT with Microsoft’s mbr2gpt tool, it creates new EFI partition by shrinking Windows partition (in your case partition with index 3) and creating new EFI boot partition (in your case EFI boot partition with index 4) and leaving original EFI boot partition (in your case EFI boot partition with index 1).
First, I would try to enter CMOS setting (BIOS / UEFI firmware settings) and specify to boot from “Disk 1 / Partition 4” instead of “Windows Boot Loader” entry that it detected.
If that does not work I would delete partition 4 from “Disk 1” and try to fix the the EFI boot partition under index 1.
Steps in DiskPart:
select disk 1
sel part 3
assign letter c
select part 4
del part override
sel part 1
format fs=fat32 quick label=Boot
assign letter s
exit
In command prompt now re-create EFI boot partition contents using BCDBOOT command like this:
bcdboot c:\windows /s S: /f UEFI
In order for this to work properly you need to make sure that windows partition (where Windows folder is located) is mounted with letter “C” as in “C:\Windows” and that EFI boot partition is mounted with letter “S” as in “S:\EFI”.
After this you should be able to boot into your Windows system but the recovery tools will be busted…
To fix Windows Recovery Environment follow one of the methods in this video: https://www.youtube.com/watch?v=94QInTcTWt4
You will need to fiddle around with BCDBOOT.EXE to get the GUID of your “Windows Boot Loader” entry and REAGENTC.EXE from Command Prompt.