In-place upgrade versus optional features

%3CLINGO-SUB%20id%3D%22lingo-sub-2907069%22%20slang%3D%22en-US%22%3EIn-place%20upgrade%20versus%20optional%20features%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2907069%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20second%20build%20of%20Windows%20Server%20vNext%20(based%20on%20Windows%2011)%20came%20with%20an%20iso%20with%20installable%20optional%20features%2C%20via%20Dism.%20I%20plan%20to%20use%20in-place%20upgrade%20from%20build%20to%20build%2C%20not%20perform%20fresh%20installs%20on%20my%20test%20machine%20every%20time.%20I%20wonder%20if%20in-place%20upgrade%20shall%20be%2C%20practicly%2C%20blocked%2C%20if%20any%20of%20the%20optional%20features%20is%20installed%2C%20due%20to%20incompatibility%20between%20the%20installed%20optional%20features%2C%20on%20file%2Ffeature%20version%20number.%20Perhaps%20upgrade%20is%20possible%2C%20but%20optional%20features%20shall%20be%20uninstalled%20then%2C%20or%20kept%2C%20but%20needed%20to%20be%20reinstalled%20via%20Dism%20from%20new%20sources%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2907069%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EFeatures%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EGeneral%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ein-place%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Emanagement%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eoptional%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EUpgrade%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2911585%22%20slang%3D%22en-US%22%3ERe%3A%20In-place%20upgrade%20versus%20optional%20features%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2911585%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F67381%22%20target%3D%22_blank%22%3E%40Radu%20Ilie%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20create%20a%20custom%20image%20of%20the%20new%20build%2C%20with%20the%20new%20Feature%20on%20Demand%2C%20and%20use%20that%20as%20the%20OS%20to%20upgrade%20to%2C%20it%20should%20work.%26nbsp%3B%20Take%20a%20look%20at%20the%20steps%20here%20to%20do%20this%20with%20the%20App%20Compatibility%20Feature%20on%20Demand%20for%20Server%20Core.%26nbsp%3B%20See%20section%2C%20%22Adding%20to%20an%20offline%20WIM%20Server%20Core%20image%22.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fget-started%2Fserver-core-app-compatibility-feature-on-demand%23adding-to-an-offline-wim-server-core-image%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EServer%20Core%20App%20Compatibility%20Feature%20on%20Demand%20(FOD)%20in%20Windows%20Server%20%7C%20Microsoft%20Docs%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E-Brent%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

The second build of Windows Server vNext (based on Windows 11) came with an iso with installable optional features, via Dism. I plan to use in-place upgrade from build to build, not perform fresh installs on my test machine every time. I wonder if in-place upgrade shall be, practicly, blocked, if any of the optional features is installed, due to incompatibility between the installed optional features, on file/feature version number. Perhaps upgrade is possible, but optional features shall be uninstalled then, or kept, but needed to be reinstalled via Dism from new sources?

1 Reply

Hi @Radu Ilie 

 

If create a custom image of the new build, with the new Feature on Demand, and use that as the OS to upgrade to, it should work.  Take a look at the steps here to do this with the App Compatibility Feature on Demand for Server Core.  See section, "Adding to an offline WIM Server Core image".

 

Server Core App Compatibility Feature on Demand (FOD) in Windows Server | Microsoft Docs

 

Thanks!

 

-Brent