Blog Post

Windows IT Pro Blog
3 MIN READ

Simplifying on-premises deployment of servicing stack updates

AriaUpdated's avatar
AriaUpdated
Icon for Microsoft rankMicrosoft
Sep 08, 2020
Update 2021.02.09: On February 9, 2021, we released the February 2021 SSU for Windows 10, versions 1909, 1809, 1607 and 1507*. The February 2021 SSU will be a prerequisite for receiving the new one c...
Updated Feb 24, 2021
Version 5.0
servicing and updates
JoergWu's avatar
JoergWu
Copper Contributor
Oct 03, 2020

Hi AriaUpdated,

In general these are really great news and I like it very much. :lol:

 

But now there is the drawback! Including all stuff in the install.wim (as of today 2004 with sept updates is 4,487 MB) is already beyond the space limit of FAT32 (4 GB max file size) partitions on USB drives (needed to do an installation with FAT32 while secureboot is on. NTFS partitions e.g. would even not be shown on a Surface device!) :cry:

Whenever you do an inplace upgrade (from running Windows OS) from an USB drive (NTFS) everything is fine. But when you need to do a fresh installation (no running OS, while secure boot is on (and setting it to off is not really a good option)). :facepalm:

Fortunately you would have already a solution for this! You just need to use it! (simply use your own split functionality!)

https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/split-a-windows-image--wim--file-to-span-across-multiple-dvds

So it would be very convenient when ever your ISO build process is modified to have 4GB Install wims (.SWM files) instead to deal with this manually.

I think its not a good option whenever we as customers have to modify the install media by ourselves everytime. Just think of home users! For us this is complex, cumbersome and time consuming process. For you its a simple onetime change in your ISO build process.

 

Looking forward to get the next ISO with the right install.wims (splitted accross smaller files). :stareyes: