Why am I being reoffered updates on the latest VL media?
Update: The blog for this is now public: https://support.microsoft.com/kb/3037986
Update #2: The new supersedence is set for the November Update release so you should no longer be seeing previous roll-ups offering as they were in the past. I've struck through that text below.
Update #3: We recently made a publishing change that resolves Scenario #1 below.
If you're a customer who has built, or is building, new images based on the latest volume license media, published in November, there are a couple of issues you should be aware of when it comes to updating the media properly. Firstly, the following updates are not a part of the media (or were released in conjunction with the media) and will offer to these systems when they scan Windows Update.
| KB | Description |
| 2977765 | MS14-053: Description of the security update for the .NET Framework 4.5.1 and the .NET Framework 4.5.2 for Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2: September 9, 2014 |
| 2978041 | MS14-057: Description of the security update for the .NET Framework 4.5.1 and the .NET Framework 4.5.2 for Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2: October 14, 2014 |
| 2978126 | MS14-072: Description of the security update for the .NET Framework 4.5.1 and 4.5.2 on Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2: November 11, 2014 |
| 2979576 | MS14-057: Description of the security update for the .NET Framework 4.5.1 and the .NET Framework 4.5.2 for Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2: October 14, 2014 |
| 2894856 | Description of the security update for the .NET Framework 4.5.1 on Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2: December 10, 2013 |
| 3002885 | MS14-079: Vulnerabilities in kernel-mode driver could allow denial of service: November 11, 2014 |
| 2899189 | Update adds support for many camera-specific file formats in Windows 8.1 or Windows RT 8.1: December 2013 |
| 2976536 | November 2014 anti-malware platform update for Windows Defender in Windows 8.1 and Windows 8 |
| 2990967 | Some versions of the OneDrive desktop app for Windows do not update automatically |
| 2998174 | Active camera is switched unexpectedly when you review photos in Camera app in Windows 8.1 or Windows Server 2012 R2 |
Secondly, you may notice that prior rollups from May through October are offered to you. This is due to the fact that Nov. Update is currently marked as Optional for Windows Update. Because we would never want to offer an Optional update over an Important one, these will continue to offer. The Nov. Update will change to Important at some point in the near future and this will no longer be an issue.
Lastly, there are scenarios where April rollup (aka S14 to some) will reoffer. These scenarios are pretty specific and I have a KB article that will be out soon outlining these but I wanted to note them here. They are:
Scenario 1
Images were built using the November 2014 Volume License Media
Resolution: Integrate KB2959977 using the DISM method below (note: this cannot be installed via MSU)
Scenario 2
Images were built using the April 2014 Volume License Media where only KB3000850 has been installed
Resolution: Integrate KB2934018 using the DISM method below (note: these cannot be installed via MSU)
Scenario 3
Images built using either of the above methods where one of the following language packs is later installed: cs-cz,da-dk,de-de,el-gr,es-es,fi-fi,fr-fr,hu-hu,it-it,ja-jp,ko-kr,nb-no,nl-nl,pl-pl,pt-br,pt-pt,ru-ru,sv-se,tr-tr,zh-cn,zh-hk,zh-tw
Resolution:
· Install Language Packs required for the environment prior to installing KB2913955 -or-
· Install KB2934018 using the standalone installer
Scenario 4
Images built using the DISM /resetbase command
Resolution: Integrate KB2959977 using the DISM method below
Using DISM to integrate packages into an image
1. Download the standalone package for the update(s) to integrate
2. Create a new directory to expand the update packages
3. Extract the update package using the following command:
a. expand -f:* <path to .msu> <destination>
4. For example, the following command expands KB2959977 to the c:\cabs directory
b. expand -f:* Windows8.1-KB2959977-x64.msu c:\cabs
5. Integrate the expanded cabinet file into the image from the expanded package
c. DISM /Online /Add-Package /PackagePath:<path to extracted .cab file from Step 3>
6. For example, the command to integrate the KB2959977 cab file would be
d. DISM /Online /Add-Package /PackagePath:c:\cabs\Windows8.1-KB2959977-x64.cab
--Joseph