Just updated to Parallels 26 - now my virtual windows machine fails to start

This is a long established VM, which has worked for years through multiple Mac OS, Parallels and windows version upgrades.
I will attach a screen shot = "no operating system"
However, if I "ESC" from the "virtual" shell, I can select boot options and it will run, eg selecting: Windows Boot, EFI drive, etc.
I tried to change the boot order within the shell dialog, but it seems to only exist for the current session - ie save does NOT survive a shut-down restart of the vitual machine.
I does not appear that any options within Parallels can manage at the required level.

 

followup by OP: today I "reverted"; downloaded Parallels 18.3.3 and installed.
That fixed my problem - now the virtual machine starts perfectly.
Do these postings generate bug reports, or is there some other requirement?????

 

yesterday I did file a support request and was assisted to try boot option unsuccessfully;
then to revert to the latest version 20 with a successful VM start.

I believe they are continuing to review the "technical reports" I submitted, so hopefully a revision can be made to Parallels 26, or some incorrect/obsolete settingcan be corrected in my VM

 

followup by OP: it has been escalated through tier 1, and tier 2 of support, and is now sent to Development. A workaround is to change the setting within Boot Order to "tick" the "Select Boot order at startup". Then, when the machine starts, you can get to a BIOS to select "boot Manager", and pick "Windows Boot Manager".

 

after return from vacation, I updated to the current 26.3.1.
I tested resetting to 'untick' "Select boot device on startup".
It now starts correctly!
Problem solved!