installing linuxCNC 2.7.14 under Hyper-V Manager

Installation step failed
An installation step failed.  You can try to run the failing item again from the menu, or skip it and choose something else.  The failing step is: install the system.

Anyone else see this and found a solution?

Using Hyper-V is probably a bad idea.

QEMU will probably be better.

Though you will get awful latency compared to a bare-metal install.

latency does not matter for simulation

TBH this is not really an Linuxcnc issue but a Hyper-V Debian issue as the standard Debian installer is used.
What you can try is to install Debian bookworm from a Debian ISO with XFCE desktop then follow the instructions in the Linuxcnc docs to install the Linuxcnc packages. This is about the best suggestion I can come up with.
Personally I use VirtualBox, as it's basically flawless.

I am now trying to install under VirtualBox. It never completes. End of log:
00:01:24.910162 VUSB: Detached 'HidMouse' from port 1 on RootHub#1
00:01:24.910963 E1000#0: Interrupt attempts: 1
00:01:24.910970 E1000#0: Interrupts raised : 0
00:01:24.910972 E1000#0: Interrupts lowered: 0
00:01:24.910974 E1000#0: ICR outside ISR : 0
00:01:24.910976 E1000#0: IMS raised ints : 0
00:01:24.910980 E1000#0: Interrupts skipped: 0
00:01:24.910983 E1000#0: Masked interrupts : 1
00:01:24.910985 E1000#0: Early interrupts : 0
00:01:24.910986 E1000#0: Late interrupts : 0
00:01:24.910988 E1000#0: Lost interrupts : 0
00:01:24.910990 E1000#0: Interrupts by RX : 0
00:01:24.910991 E1000#0: Interrupts by TX : 0
00:01:24.910993 E1000#0: Interrupts by ICS : 0
00:01:24.910995 E1000#0: Interrupts by RDTR: 0
00:01:24.910996 E1000#0: Interrupts by RDMT: 0
00:01:24.910998 E1000#0: Interrupts by TXQE: 0
00:01:24.911000 E1000#0: TX int delay asked: 0
00:01:24.911001 E1000#0: TX delayed: 0
00:01:24.911003 E1000#0: TX delay expired: 0
00:01:24.911005 E1000#0: TX no report asked: 0
00:01:24.911006 E1000#0: TX abs timer expd : 0
00:01:24.911008 E1000#0: TX int timer expd : 0
00:01:24.911009 E1000#0: RX abs timer expd : 0
00:01:24.911011 E1000#0: RX int timer expd : 0
00:01:24.911013 E1000#0: TX CTX descriptors: 0
00:01:24.911015 E1000#0: TX DAT descriptors: 0
00:01:24.911018 E1000#0: TX LEG descriptors: 0
00:01:24.911020 E1000#0: Received frames : 0
00:01:24.911021 E1000#0: Transmitted frames: 0
00:01:24.911023 E1000#0: TX frames up to 1514: 0
00:01:24.911025 E1000#0: TX frames up to 2962: 0
00:01:24.911028 E1000#0: TX frames up to 4410: 0
00:01:24.911029 E1000#0: TX frames up to 5858: 0
00:01:24.911031 E1000#0: TX frames up to 7306: 0
00:01:24.911032 E1000#0: TX frames up to 8754: 0
00:01:24.911034 E1000#0: TX frames up to 16384: 0
00:01:24.911036 E1000#0: TX frames up to 32768: 0
00:01:24.911037 E1000#0: Larger TX frames : 0
00:01:24.911039 E1000#0: Max TX Delay : 0
00:01:24.911911 GIM: KVM: Resetting MSRs
00:01:24.912967 vmmR3LogFlusher: Terminating (VERR_OBJECT_DESTROYED)
00:01:24.913083 Changing the VM state from 'DESTROYING' to 'TERMINATED'
00:01:24.913094 Console: Machine state changed to 'PoweredOff'
00:01:24.942548 GUI: Request for async QApp quit.
00:01:24.944297 GUI: Cannot notify guest about VM window out-of-focus event
00:01:24.956701 GUI: UICommon: Handling aboutToQuit request..
00:01:26.425803 GUI: UICommon: aboutToQuit request handled!

I'll have a look tomorrow, what ISO are you using, exact filename will make life easier, any particular reason for 2.7.14 ?
Windows or Linux host ?

Deleted.

Host System Linux Mint 22.2 Xia
VirtualBox 7.18
Guest
32 Bit System 4GB Ram 16GB HDD
Bridged Network

Install went fine about 5 or 10 miuntes, boots fine.
Obviously Wheezy is EOL so upgrades maybe a bit funky
Linuxcnc upgrade were fine
Installation of Midnight Commander & Geany went fine
Axis sim run as expected
Shutdown was clean

Langdons, before commenting please try to read the other posts.
VirtualBox was suggested
The last error log was from VirtualBox
This behaviour only frustrates people.

Exported the VM as an appliance

drive.google.com/file/d/1KW0E5-DjnCoSU8D...VQe/view?usp=sharing

Perhaps just some sort of Windows-related issue?

An incompatibility of some sort?