Forum Discussion
VTank
Oct 02, 2021Copper Contributor
In place update to build 22463 fails.
Hi I have build 20344.1 and tried to do an in place upgrade to the release eval build, but there is no option to keep files and settings (it is greyed out). I then tried to download build 22463 and ...
Mary Hoffman
Oct 06, 2021Former Employee
Where did you obtain the 20348 build?
MartinLu1080
Oct 06, 2021Copper Contributor
It is a MSDN Download in our Test Environment: 22348.230
- Mary HoffmanOct 16, 2021Former EmployeeWe are still very early in the development cycle of VNext which is why we have not yet resumed our usual weekly cadence, but yes, we do intend to resume weekly builds at some point. We support preview build-to-build upgrades, so when the next preview is released, let us know if you have any issues with upgrading from 22463.
- Radu IlieOct 16, 2021Brass ContributorAs for myself, I never tried to upgrade from the final (RTM) version of Windows Server 2022 to the first build of Windows Server vNext (11). I wanted a fresh start of a new testing period. For me, it would be interesting to see that in-place upgrade from one build to the next of Windows Server vNext (11) to the other., especially if new builds will came often. Until now, we have only one build. If there will be as often as weekly builds, this will be important to know.
- VTankOct 06, 2021Copper ContributorYep I understand that, although haven't done the upgrade yet. However, to get the download of the release that is not an evaluation build means trying to locate the details or person responsible for the accounts and getting a download. It would be far easier to be able to update my current build (20344) to the release build (eval is easier to get than the subscription) in place so it keeps the settings. Then we can either stay at that build to check the impact or go to vNext. But seems like a lot of hurdles in doing this for me, unless the eval build supports in place upgrade. Sorry if I have misunderstood something.
- Mary HoffmanOct 06, 2021Former EmployeeBuild-to-Build upgrade is already supported within the same version, e.g., Windows Server 2022 or Windows Server VNext. The issue seems to be related to upgrading from the RTM build of Windows Server 2022 to the first released build of VNext.
- VTankOct 06, 2021Copper ContributorThanks Mary for investigating. It would be nice if the evaluation build lets you do an in place upgrade as for testing we don't always want to rebuild and also don't always want to use every single build, may want to skip some. Would it be possible to ask the engineers if this could be allowed. Thanks
- Mary HoffmanOct 06, 2021Former EmployeeThanks, investigating with our internal upgrade subject matter expert.