Well... I don't know what to say 
New testing shows Build#231116, no issues... with Build#240110, no issues... with Build#240105, no issues (repeated these tests). Previously... Build#240105 failed... Build#231116, no issues... Build#240105 failed once again.
As mentioned, I don't know what to say
No System configuration changes during original reported testing phase, only simple Beta testing of HBS going forward.
...and for the third time, I don't know what to say
Maybe "we" should just move on
... sorry for the interruption.
There are other issues I'm dealing with in relation to this Dell Latitude 5290 2-in-1 platform but not blaming Hasleo just yet
. If I clean install Windows on an unformatted disk... no problem with BiOS recognizing configuration (and seeing the Windows BOOT Manager as a BOOTable option). If I image that System configuration and restore it to an unformatted disk, via Hasleo, Windows refuses to see a valid BOOT device... regardless of what partition I tell the BiOS to BOOT from (pointing to the EFI in most cases). The BiOS no longer sees the Windows BOOT Manager either. It looks like some weird BiOS issue (it is fully updated but did the same thing with the original delivered BiOS) that I just may not understand as of yet. So as you can see... plenty of fun ahead 
New testing shows Build#231116, no issues... with Build#240110, no issues... with Build#240105, no issues (repeated these tests). Previously... Build#240105 failed... Build#231116, no issues... Build#240105 failed once again.As mentioned, I don't know what to say
No System configuration changes during original reported testing phase, only simple Beta testing of HBS going forward....and for the third time, I don't know what to say
Maybe "we" should just move on
... sorry for the interruption.There are other issues I'm dealing with in relation to this Dell Latitude 5290 2-in-1 platform but not blaming Hasleo just yet
. If I clean install Windows on an unformatted disk... no problem with BiOS recognizing configuration (and seeing the Windows BOOT Manager as a BOOTable option). If I image that System configuration and restore it to an unformatted disk, via Hasleo, Windows refuses to see a valid BOOT device... regardless of what partition I tell the BiOS to BOOT from (pointing to the EFI in most cases). The BiOS no longer sees the Windows BOOT Manager either. It looks like some weird BiOS issue (it is fully updated but did the same thing with the original delivered BiOS) that I just may not understand as of yet. So as you can see... plenty of fun ahead