There is a release date for each version of Win10. So when you use the ISO, or its created installer, there is a good chance that it will be the right version (20H2), but the Build will probably not be current (as in containing the latest month’s updates). MS doesn’t put together new ISO material for download every day. In other words, today (on 3/16/21), the ISO might contain the November Preview Build (19042.631) instead of containing the current updates for March Build 19042.867. It will be the material from the last time MS created an ISO. However, the material (files, code, whatever you want to call it) that the MCT downloads from Microsoft to create the ISO, may not be the current build. The MCT is just a tool to download and create an ISO. In other words, today (on 3/16/21), the MCT will create an ISO of version 20H2=19042. Now you can either create a new task sequence that uses the newly created image or modify an existing one.The ISO created by the MCT you download will be the Version of Win10 that is current on the day you run the MCT. Given a unique name for the image, and done for the import. Check the Move the files option if needed. Select the entire image folder that contains the install.wim file we just managed to create.
Now let’s open Deployment Workbench (MDT Console), right-click Operating System and choose Import Operating System. This created the install.wim file in the same folder as install.esd. DISM /Export-Image /SourceImageFile:sources\install.esd /SourceIndex:6 /DestinationImageFile:sources\install.wim /compress:max /CheckIntegrity
Now run the following to create the install.wim file.
Since I am preparing for the Pro version, index 6 is what I needed. DISM /Get-WimInfo /WimFile:sources\install.esd Open an elevated Command Prompt window and run the DISM command to locate the right image to convert first. For me, I copied the whole drive into a Software folder on my computer.
Now let’s make a copy of the mounted drive to a folder.
0 kommentar(er)
