Let’s discuss the Difference Between the Content of Windows 10 ISO Media. Update on 17th Nov 2021: Microsoft announced that it removed the semi-annual channel update for Windows 10 on Nov 16, 2021. There will only be one feature update per year for Windows 10.
I wondered whether there is any difference in the content of Windows 10 ISO files released in two phases. Two different ISO files are released as part of Windows 10 SAC-T and SAC channels.
More details about the Semi-Annual Channel are here. This post will show the differences between Windows 10 SAC-T and SAC ISO Media.
With Windows 10, patching is simpler. One cumulative monthly update containing security and non-security fixes supersedes the previous month’s update.
Table of Contents
Two Related Posts on Windows 10 Servicing Topic – Difference Between Content of Windows 10 ISO Media
Another fact pointed out by Microsoft is that most of the production Windows 7 and eight machines don’t have the same patch level. The cause of patch fragmentation is a mix of individual updates, as explained in the following diagram.
Two Related Posts on Windows 10 Servicing Topic |
---|
Windows 10 1709 Semi-Annual CBB Ready for Broad Deployment and details about the release date of Windows 10 1709 CBB version media Release management strategy of Windows 10 Servicing – Real-World Experience. |
- How to Download Windows 10 ISO for Free
- Download Windows 10 ISO VHDs for Free
- How to Download the Latest Version of Windows 10 ISO
- VMware Workstation Pro is Free now for Personal Use
- Copilot Vs Copilot Pro Vs Copilot for Microsoft 365 Comparison
The content of this Post
What is the big deal with patch fragmentation in systems? According to Microsoft, “Fragmentation where different PCs could have a different set of updates installed leads to multiple potential problems.”
Windows 10 Patching – Avoid Fragmentation
Do the ISOs released in part of SAC-T and SAC have the same content?
What is the Difference Between Windows 10 SAC-T and SAC ISO Media content?
Conclusion
Windows 10 Patching – Avoid Fragmentation
I recommend avoiding FRAGMENTATION of patches on Windows 10 machines from starting itself. So, I wanted all the Windows 10 computers in my network to have the same patch level.
Hence, I had a valid question about different Windows 10 ISOs released in SAC-T and SAC channels. I would like more details about Windows patch fragmentation.
Do the ISOs released in part of SAC-T and SAC have the same content?
No, the content of both ISOs is different. Windows 10 Semi-Annual Channel (Targeted) (e.g., released on 17th OCT 2017) ISO and Windows 10 Semi-Annual Channel ISO (e.g., will be published on 22nd Jan 2018) have different content. Windows 10 SAC-T and SAC ISO media are different.
If I deploy 30% of Windows 10 devices with SAC-T channel ISO and 70% of Windows 10 devices with SAC channel ISO, does this have a chance of fragmenting patches on Windows 10 systems? Because of the cumulative nature of Windows 10 patches, I hope it won’t create fragmented systems.
Update (18th Jan 2018) – I discussed patch fragmentation on Twitter with Cristopher Alaya . And as per him, the fragmentation would still be there. “There are updates deployed by Microsoft Update that are not included in the Cumulative Update, like the Servicing Stack update here:
https://support.microsoft.com/en-us/help/4058702/servicing-stack-update-for-windows-10-version-1709 … It’s not in the CU.”
So, ideally, you are safe to start the development of the Windows 10 core image for SCCM immediately after SAC-T ISO availability. My previous post, “Release MGMT strategy for Windows 10 Semi-Annual Channel and SAC-T releases,” has more details.
However, to avoid patch fragmentation in systems, you need to inject patches released between SAC-T and SAC releases into your latest Windows 10 image. Another way to prevent patch fragmentation is to keep all your Windows 10 systems up to date with the latest patch(s).
What is the difference Between Windows 10 SAC-T and SAC ISO Media content?
We found that Windows 10 SAC-T and SAC ISO Media differ in the above section. This article will provide more details about this difference. I was trying to find an answer to the above question, but I didn’t find a clear-cut answer in TechNet documentation.
Microsoft deliberately uses the word “Refreshed media” to refer to the Windows 10 SAC ISO. As an SCCM admin, I don’t believe REFRESH and UPDATE are the same in this scenario, either.
I assumed, and Michael confirmed through Twitter, that “We do refresh the media for convenience, adding in a later cumulative update.” He gave a perfect example to help me understand the difference between the Windows 10 SAC-T and SAC ISO Media content.
“So it’s the same BASE BUILD (e.g., 16299) but a later PATCH LEVEL (e.g., 16299.15 vs. 16299.125)”.
Conclusion
Windows 10 BASE Version is the same for both Semi-Annual Channel (Targeted) and Semi-Annual Channel.
For example
Windows 10 1709 SAC-T Base version is 10.0.16299
Windows 10 1709 SAC Base version is 10.0.16299
Windows 10 1703 SAC-T Base version is 10.0.15063
Windows 10 1703 SAC Base version is 10.0.15063
The difference between Windows 10 SAC-T and SAC ISO Media is PATCH LEVEL. Windows 10 cumulative Patches are the only difference between the Windows 10 ISOs released as part of the CB and CBB cycle.
You can check this out in the following examples.
Windows 10 1709 SAC-T PATCH LEVEL is 16299.15
Windows 10 1709 SAC PATCH LEVEL is 16299.192 (I’m not sure if Windows 10 1709 SAC ISO patch level until 22nd Jan 2018)
So, once the CB or SAC-T version of Windows 10 is released, you can start building or creating Windows 10 images within SCCM. There is no need to wait for the CBB version of Windows to be published.
Update on 17th Nov 2021 – Microsoft announced that Microsoft removed the semi-annual channel update for Windows 10 on Nov 16, 2021. There will only be one feature update per year for Windows 10.
We are on WhatsApp now. To get the latest step-by-step guides, news, and updates, Join our Channel. Click here. HTMD WhatsApp.
Author
Anoop C Nair is Microsoft MVP from 2015 onwards for consecutive 10 years! He is a Workplace Solution Architect with more than 22+ years of experience in Workplace technologies. He is a Blogger, Speaker, and Local User Group Community leader. His main focus is on Device Management technologies like SCCM and Intune. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security, Career etc…