Determine 1903 or 1909 with WIM?

%3CLINGO-SUB%20id%3D%22lingo-sub-1345813%22%20slang%3D%22en-US%22%3EDetermine%201903%20or%201909%20with%20WIM%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1345813%22%20slang%3D%22en-US%22%3EOne%20of%20the%20headaches%20we've%20run%20into%20(mainly%20with%20MEMCM%20OSD%20is%20being%20able%20to%20determine%20if%20a%20WIM%20is%201903%20or%201909%20as%20the%20osbuild%20on%20the%20image%20is%20the%20same.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1345989%22%20slang%3D%22en-US%22%3ERe%3A%20Determine%201903%20or%201909%20with%20WIM%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1345989%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F160879%22%20target%3D%22_blank%22%3E%40Damien%20Solodow%2C%20MCSE%2C%20MCSA%2C%20VCP-DCV%3C%2FA%3E%26nbsp%3Bfor%20raising%20this.%20Yes%20this%20is%20currently%20a%20limitation%20of%20how%20we%20shipped%201909.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EDo%20you%20directly%20import%20the%20images%20from%20Microsoft%20VLSC%20%5C%20WSUS%20or%20do%20you%20edit%20your%20images%20before%20you%20import%20them%20into%20MEMCM%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20WIM%20images%2C%20you%20can%20currently%20work%20around%20this%20by%20manually%20updating%20the%20image%20name%20to%20include%201903%20%5C%201909%20using%20dism%20and%20use%20that%20as%20a%20proxy%20for%20image%20version.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20have%20a%20fix%20in%20some%20of%20the%20insider%20fast%20builds%20(build%20numbers%20%26gt%3B19600)%20where%20you%20can%20mount%20a%201909%20WIM%20image%20and%20unmount%20-%20commit%20it%20and%20that%20should%20update%20the%20build%20number%20properly.%20This%20fix%20is%20also%20available%20via%20the%20insider%20ADK%20builds%20available%20for%20download%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fsoftware-download%2FwindowsinsiderpreviewADK%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%26nbsp%3B%20Please%20let%20us%20know%20if%20that%20helps%20resolve%20your%20issue.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20will%20look%20into%20how%20we%20can%20resolve%20this%20in%20the%20future%20releases%20%5C%20drops.%26nbsp%3B%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%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1346003%22%20slang%3D%22en-US%22%3ERe%3A%20Determine%201903%20or%201909%20with%20WIM%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1346003%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F51788%22%20target%3D%22_blank%22%3E%40Sudhagar%20Thirumoolan%3C%2FA%3E%26nbsp%3BThanks.%3C%2FP%3E%3CP%3EWe%20start%20with%20the%20VLSC%20WIM%20and%20run%20it%20through%20OSDBuilder.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'll%20give%20the%20mount%2Fcommit%20trick%20a%20try%3B%20I%20have%20a%20Fast%20Ring%20machine%20handy.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1347327%22%20slang%3D%22en-US%22%3ERe%3A%20Determine%201903%20or%201909%20with%20WIM%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1347327%22%20slang%3D%22en-US%22%3EThat%20seems%20to%20have%20done%20the%20trick.%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

One of the headaches we've run into (mainly with MEMCM OSD) is being able to determine if a WIM is 1903 or 1909 as the osbuild on the image is the same.

3 Replies

Thank you @DamienSolodow for raising this. Yes this is currently a limitation of how we shipped 1909.

 

Do you directly import the images from Microsoft VLSC \ WSUS or do you edit your images before you import them into MEMCM?

 

For WIM images, you can currently work around this by manually updating the image name to include 1903 \ 1909 using dism and use that as a proxy for image version. 

 

We have a fix in some of the insider fast builds (build numbers >19600) where you can mount a 1909 WIM image and unmount - commit it and that should update the build number properly. This fix is also available via the insider ADK builds available for download here.  Please let us know if that helps resolve your issue.

 

We will look into how we can resolve this in the future releases \ drops. 

 

Thanks

 

@Sudhagar Thirumoolan Thanks.

We start with the VLSC WIM and run it through OSDBuilder.

 

I'll give the mount/commit trick a try; I have a Fast Ring machine handy.

That seems to have done the trick. :)