installed a fresh VM and will try to reproduce it.
So far when continuing the setup after enable flighting. setup comes up with the "Ready to Install Windows 11"
Same result. Does WS 2025 require (v)TPM? From techcommunity answer I understood that's only on later HW but not for VMs.
Oh, please also include which edition of Server you are using.
I tried the most basic Server 2022 -> Server 2025 upgrade scenario on Hyper-V. I used a Gen 2 VM with 4GB of RAM. I started with a vanilla image of Datacenter with Desktop Experience, Windows Server 2022, with February patches, and then attached an ISO of WS 2025 26063 and ran Setup.exe. It worked fine.
So, let's figure out what's different in your setup.
I'm working through the process of doing this in MSLab. Based on the pictures you documented, I assume it is the 'DC' VM that I need to update - but I am getting a strange complaint about an additional step I need to take for the domain controller. Did you see this as well? Is there a reasonable way to address this? (I can see that the link documents a set of steps, but this seems rather far off the track of a simple upgrade.)
@MSBernstein thank you for going the extra mile with mslab. as there is even a session on this on WS summit supposed it is still supported.
When running Deploy.ps1 with the default labconfig it will create the base, virtual disks templates with WS2022 core and GUI, and a DC template VM
1. please rename the existing labconfig file
2. and create a new one with code below
3. run deploy.ps1
this will create the "lab" with the DC and 2 VMs used for Management (GUI) and WAC (Core)
plain and naked and AD join them.
As we do not need the azure stack hci hosts for this lab these are # out.
We can play the upgrade repro on these.
DC IPU is possible but in fact you need a cmdline command for forest prep executed from the ISO tools folder. This is by design.
At the time of writing I am updating WS 2022 to b26080. Online phase was always ok.
This is the management VM config (vTPM could be optional) does not cause it. Just adopting it from what I learned these days about new security features.
#basic config for Windows Server 2022, that creates VMs for S2D Hyperconverged scenario https://github.com/Microsoft/MSLab/tree/master/Scenarios/S2D%20Hyperconverged
$LabConfig=@{AllowedVLANs="1-10,711-719" ; DomainAdminName='LabAdmin'; AdminPassword='LS1setup!' ; DCEdition='4'; Internet=$true ; TelemetryLevel='Full' ; TelemetryNickname='' ; AdditionalNetworksConfig=@() ; SecureBoot=$true ; VMs=@() ; CustomDnsForwarders=@("1.1.1.1","1.0.0.1")}
#Azure Stack HCI 22H2
#1..2 | ForEach-Object {$LABConfig.VMs += @{ VMName="AzSHCI$_" ; Configuration='S2D' ; ParentVHD='AzSHCI22H2_G2.vhdx' ; HDDNumber=4 ; HDDSize=1TB ; MemoryStartupBytes=1GB; VMProcessorCount=4 ; vTPM=$true}}
#Azure Stack HCI 22H2 with nested virtualization
#1..2 | ForEach-Object {$LABConfig.VMs += @{ VMName="AzSHCI$_" ; Configuration='S2D' ; ParentVHD='AzSHCI22H2_G2.vhdx' ; HDDNumber=4 ; HDDSize=1TB ; MemoryStartupBytes=32GB ; VMProcessorCount=8 ; vTPM=$true ; NestedVirt=$true}}
#Windows Admin Center in GW mode
$LabConfig.VMs += @{ VMName = 'WACGW' ; ParentVHD = 'Win2022Core_G2.vhdx'; MGMTNICs=1}
#Management machine
$LabConfig.VMs += @{ VMName = 'Management' ; ParentVHD = 'Win2022_G2.vhdx'; MGMTNICs=1}
very unfortunately no change for Windows Server 2022 Datacenter GUI to 26080
C1900101 - 0x20017
Host OS is now 26080
Guest OS is still 2022 > 26080
Next steps:
trying IPU on WS 2022 Core (below)
trying a fresh VM, . just to make sure it is not an RSAT tool or other dependency on this box.
tested Windows Server 2022 Datacenter Core to 26080
Tried uprade the core upgrade but this fails even earlier after confirming to keep files and settings in the wizard, could be related to the known issues in release notes.
Error when IPU 2022 Datacenter to WS 2025 b26080 Core
SetupDiag: processing rule: FindAbruptDownlevelFailure.
.....
Error: SetupDiag reports abrupt down-level failure.
Last Operation:
Error: 0xC1900220 - 0x4000D
LogEntry: 2024-03-14 02:34:32, Error MOUPG CSetupResponseTemplate<class ICompatActionResponse>::InitializeRoutine(84): Result = 0xC1900220[gle=0x00000002]
new VM 23048.2159
@MSBernstein last update for this tonight, same behaviour
So opposite to you, (unfortunately) I can replicate the problem.
Hope you'll have success to repro it, too. Here it appears to be absolutely reproducible.
One to note, after setup completed to 100% in the online phase, now with 26080 recognize a small difference vs 26063.
The first boot after IPU takes several minutes showing (old) circling balls, where as I would be expecting to see a brief "preparing drivers" + Apply phase with "You are x% there yet - do not shut down..." But this is not showing up just very long boot phase with 26080 now.
With 26063 the reboot was quick (about 2 seconds) and it directly booted into the "wrong" bcdedit as it appears.
With 26080 it seems it is picking the setup bcdentry
in both cases each IPU attempt would generate a new bcdentry. So maybe there is the culprit.
It does not initiate a real visible rollback and the setup bcd remains.
Hyper-V Host settings all default, except on host HCVI / VBS is enabled via Defender Security Center (Core Isolation). And off the bare defaults also vTPM is activated on the Gen2 Secure Boot guest VM.
Accepted Solutions