FreeBSD media boots Windows DevKit 2023 but VHDX copied from the media does not boot under Win11Pro Hyper-V

I took a 224 GiByte or so FreeBSD boot media that
boots the Windows DevKit 2023 just fine:

From gpart show -p from such a boot:

=>       40  468862048    da0  GPT  (224G)
         40      32728         - free -  (16M)
      32768     532480  da0p1  efi  (260M)
     565248    7864320  da0p2  freebsd-swap  (3.8G)
    8429568     524288         - free -  (256M)
    8953856    8388608  da0p3  freebsd-swap  (4.0G)
   17342464    8388608  da0p4  freebsd-swap  (4.0G)
   25731072  440401920  da0p5  freebsd-ufs  (210G)
  466132992    2729096         - free -  (1.3G)

From gpart show -pl  from the boot:

=>       40  468862048    da0  GPT  (224G)
         40      32728         - free -  (16M)
      32768     532480  da0p1  PBefi  (260M)
     565248    7864320  da0p2  PBswp3p75  (3.8G)
    8429568     524288         - free -  (256M)
    8953856    8388608  da0p3  PBswp4a  (4.0G)
   17342464    8388608  da0p4  PBswp4b  (4.0G)
   25731072  440401920  da0p5  PBsmallUFS  (210G)
  466132992    2729096         - free -  (1.3G)

It has both package base kernels and personal builds:

# strings -f /boot/kernel*/kernel | grep ": FreeBSD [0-9][0-9]\.[0-9]-" | sort -k4,5 | sed -e "s@: @% @" | tr % "\n"
/boot/kernel.CA76-NODBG.old/kernel
 FreeBSD 15.0-CURRENT #2 main-n268827-75464941dc17-dirty: Sun Mar 17 18:44:08 PDT 2024
/boot/kernel.CA76-DBG.good/kernel
 FreeBSD 15.0-CURRENT #6 main-n271165-cb18ba9df52d-dirty: Fri Jul 12 11:09:16 PDT 2024
/boot/kernel.CA76-NODBG.good/kernel
 FreeBSD 15.0-CURRENT #6 main-n271165-cb18ba9df52d-dirty: Fri Jul 12 11:09:16 PDT 2024
/boot/kernel.CA76-DBG/kernel
 FreeBSD 15.0-CURRENT #7 main-n271413-1f7df7570174-dirty: Sat Jul 27 09:11:21 PDT 2024
/boot/kernel.CA76-NODBG/kernel
 FreeBSD 15.0-CURRENT #7 main-n271413-1f7df7570174-dirty: Sat Jul 27 09:11:21 PDT 2024
/boot/kernel.GENERIC-DEBUG.good/kernel
 FreeBSD 15.0-CURRENT main-n271137-d68d12481778 GENERIC
/boot/kernel.GENERIC-NODEBUG.good/kernel
 FreeBSD 15.0-CURRENT main-n271137-d68d12481778 GENERIC-NODEBUG
/boot/kernel/kernel
 FreeBSD 15.0-CURRENT main-n271408-4fab5f005482 GENERIC
/boot/kernel.GENERIC-MMCCAM/kernel
 FreeBSD 15.0-CURRENT main-n271408-4fab5f005482 GENERIC-MMCCAM
/boot/kernel.GENERIC-NODEBUG/kernel
 FreeBSD 15.0-CURRENT main-n271408-4fab5f005482 GENERIC-NODEBUG

The boot world is a package base world.

I used the Windows 11 tool that can make a VHDX copy of
physical media to make such a copy.

Attempting to boot the result gets as far as showing the
EFI framebuffer information, which looks reasonable. But
the mask line is the last output in the console window.
All the kernel selections from the loader do that.

Is this expected? Is there a known potential work round?

Note: the context is for ssh based use, not video based
use. But it is go to see console messages if any occur.

Why Hyper-V? It is the context that I've usually used
to test (smaller) RAM and core-count combinations that I
do not have examples of. But I've done such on amd64
historically, not aarch64, other than possibly one prior
time. On amd64 the drive was internal PCI hardware and
no production of a VHDX file was required. On aarch64
with the USB based drive, direct use of the drive is
blocked, thus the use of a VHDX file produced from the
original media.

===
Mark Millard
marklmi at yahoo.com