search

microsoft / MSLab

Azure Stack HCI, Windows 10 and Windows Server rapid lab deployment scripts
MIT License
1.2k stars 287 forks source link

mslab 24.06.2 release / dev - creating mslab VM (DC) with Windows Server vNext causing unexpected issue at first boot #607

Closed Karl-WE closed 3 days ago

Karl-WE commented 3 days ago

Scenario:

Host OS (Hyper-V): Windows Server 2025 (b26100, b26304) or Windows Server 2022 Guest OS (DC): Windows Server 2025 b26292, b26304

Issue:

Booting the DC fails at the first boot during DC hydration at "Getting Ready"

DISM Log reports an interruption as if the ISO / WIM was broken or the VM rebooted during setup phase.

Image

Hyper-V Console view:

'Windows Could not configure one or more system components. To Install Windows, restart computer and then restart the installation.'

Image

Repro steps:

Install WS 2022 or 2025 as host OS Enable Hyper-V Deploy mslab 24.06.02 Use WS 2025 vNext ISO during step 2 (2_createparentdisks.ps1)

Do not use WS 2025 vNext and neither WS2025 b26100 (see #588) as a guest VM OS at the moment, for 2_CreateParentDisks.ps1 (DC) until solved. Using WS 2025 for usual VMs, such as Management, WAC etc are not affected.

Workaround:

Using Windows Server 2022 ISO patched 2024-10 LCU works on any of the mentioned host OSes.

Logs:

WS2022 DC (works) Prereq.log CreateParentDisks.log

WS2025 vNext DC b26304 (fails) CreateParentDisks.log Prereq.log

Karl-WE commented 3 days ago

If anyone can repro this issue, please do not hesitate posting here. Mind that #588 is not exactly related to this issue, while it appears at the same step and appear similar.

The main difference is that b26100 will return a black screen, while b26296 and later should have this mentioned issue fixed, but now - for me - produces a different issue.

fyi: @michbern-ms

Karl-WE commented 3 days ago

corrected typo in OP WS build WS 26308 > 26304 corrected logs in OP - added clarification for logs and DC OS Version, added both WS 2022 and b26304

Tested new combination Host OS 26304 and DC 26311 - issues appears to be fixed

Logs (first run): WS2025 vNext DC b26311 (from UUPdump) Prereq.log CreateParentDisks.log

Will do more tests with Host OS 26311 and DC 26311 before closing this issue.

second run with a complete fresh start with mslab dev Host OS b26304 and DC 26311 was successful.

Logs (second run): Prereq.log CreateParentDisks.log

Karl-WE commented 3 days ago

Tested Host OS b26311 and DC b26311 on mslab dev.

Heureka! The issue got resolved in the build 26311.

CreateParentDisks.log Prereq.log