@Greg_E for the upgrade, the vm has the citrix drivers installed. For a new install, it never got that far. Anyway, it appears to be that the host cpu is too old.
Posts
-
RE: Win11 24H2 install fails consistently
-
RE: Win11 24H2 install fails consistently
@dinhngtu yeah it is a Intel(R) Core(TM) i5-4250U and it definitely is not supported. My production pool is three newer nucs that are supported, but they are currently not running xcp 8.3.
The odd thing is that win11 works on this host up to 23H2 and then it doesn't.
-
RE: Win11 24H2 install fails consistently
@dinhngtu as this is my homelab, I only have old stuff, intel, but old.
Now I'm curious what hw platform specific nonsense they are doing that breaks things. Install works up to 23H2, then it doesn't.
-
RE: Win11 24H2 install fails consistently
Win11 24H2 business editions iso fails with C000021A instead, which is a winlogon crash. My guess is that something else is going on that is destabilizing winpe or whatever they are using these days to run the install.
-
RE: Win11 24H2 install fails consistently
@olivierlambert yes - it is bugcheck C0000428, which is a signing issue with the image, maybe? So I'm downloading a different version of 24H2, the business edition instead of the enterprise LTSR.
I'll update this thread when I have the results.
-
Win11 24H2 install fails consistently
Re: Win11 VM update 23H2 -> 24H2 fail
XCP-ng 8.3.0 - using provided Win11 template.
Updating from 23H2 to 24H2 using windows update fails because the platform doesn't meet the requirements.
Installing from a new Win11 template using a win11 24H2 enterprise ISO crashes shortly after the installation starts from the iso.
TL;DR - my test pool host is too old. Bummer.
-
RE: EOL: XCP-ng Center has come to an end (New Maintainer!)
@michael-manley sounds like a plan.
-
RE: 8.3 USB Passthrough - Win Server 2019 BSOD
@andsmith windbg is also a regular win32 app and is included in any recent windows SDK. Here: https://developer.microsoft.com/en-us/windows/downloads/windows-sdk/
You just need windbg so deselect all the other crap.
-
RE: EOL: XCP-ng Center has come to an end (New Maintainer!)
@AbyssMoon the tip of the development branch (commit cd4c62ee) builds in VS2022 and produces a functional XCP-ng Center. If you have the tools, you can just fork the repo (or clone it) and build locally.
The github workflow doesn't appear to be working, as far as I can tell, so perhaps that is why the 'latest' release is from January.