Home

Windows Sevrer offline update user experience should be improved

%3CLINGO-SUB%20id%3D%22lingo-sub-358776%22%20slang%3D%22en-US%22%3EWindows%20Sevrer%20offline%20update%20user%20experience%20should%20be%20improved%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-358776%22%20slang%3D%22en-US%22%3E%3CP%3EGreetings%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20to%20say%20I%20am%20getting%20annoyed%20when%20installing%20cumulative%20updates%20for%20Windows%20Server%202016%20on%20an%20air-gaped%20server.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20installed%20this%20server%20by%20using%20en_windows_server_2016_x64_dvd_9718492.iso%2C%20which%20means%20the%20initial%20version%20is%2010.0.14393.447.%20I%20was%20happy%20at%20the%20very%20beginning%20because%20we%20have%20cumulative%20update.%20As%20the%20name%20indicates%2C%20I%20should%20have%20the%20ability%20to%20patch%20my%20server%20to%20a%20specific%20version.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20servicing%20stack%20update%20%3CSTRONG%3ETOTALLY%3C%2FSTRONG%3E%20break%20this%20nice%20dream.%20And%20these%20servicing%20stack%20updates%20are%20not%20listed%20in%20update%20history.%20(%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4000825%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4000825%3C%2FA%3E).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESince%20yesterday%2C%20I%20have%20to%20use%20wsusscn.cab%20to%20check%20the%20updates%20that%20should%20be%20installed.%20wsusscn.cab%20gives%20following%20output.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20554px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F84797i099C0B51F19471FB%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22wsusscn.png%22%20title%3D%22wsusscn.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20to%20patch%20the%20server%20to%20the%20specified%20version%20to%20mitigate%20the%20version%20compatibility%20issue%20of%20Windows%20Container.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fhub.docker.com%2F_%2Fmicrosoft-windows-servercore%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fhub.docker.com%2F_%2Fmicrosoft-windows-servercore%3C%2FA%3E%3C%2FP%3E%3CTABLE%3E%3CTBODY%3E%3CTR%3E%3CTD%3Elatest%3C%2FTD%3E%3CTD%3Eamd64%3C%2FTD%3E%3CTD%3ENo%20Dockerfile%3C%2FTD%3E%3CTD%3EWindows%20Server%20LTSC%202016%3C%2FTD%3E%3CTD%3E11%2F21%2F2018%2017%3A35%3A29%3C%2FTD%3E%3CTD%3E01%2F08%2F2019%2020%3A57%3A57%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3Eltsc2016%3C%2FTD%3E%3CTD%3Eamd64%3C%2FTD%3E%3CTD%3ENo%20Dockerfile%3C%2FTD%3E%3CTD%3EWindows%20Server%20LTSC%202016%3C%2FTD%3E%3CTD%3E10%2F05%2F2018%2023%3A34%3A11%3C%2FTD%3E%3CTD%3E02%2F12%2F2019%2020%3A59%3A43%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E10.0.14393.2665%3C%2FTD%3E%3CTD%3Eamd64%3C%2FTD%3E%3CTD%3ENo%20Dockerfile%3C%2FTD%3E%3CTD%3EWindows%20Server%20LTSC%202016%3C%2FTD%3E%3CTD%3E12%2F11%2F2018%2022%3A44%3A28%3C%2FTD%3E%3CTD%3E12%2F11%2F2018%2022%3A44%3A28%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E10.0.14393.2608%3C%2FTD%3E%3CTD%3Eamd64%3C%2FTD%3E%3CTD%3ENo%20Dockerfile%3C%2FTD%3E%3CTD%3EWindows%20Server%20LTSC%202016%3C%2FTD%3E%3CTD%3E11%2F21%2F2018%2017%3A39%3A07%3C%2FTD%3E%3CTD%3E11%2F21%2F2018%2017%3A39%3A07%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20issue%20was%20solved%20by%20following%20the%20hint%20here.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fen-US%2Fbb841f90-efd4-458d-aa73-9f9e1d041db7%2Fserver-2016-cumulative-update-not-applicable-to-your-computer%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fen-US%2Fbb841f90-efd4-458d-aa73-9f9e1d041db7%2Fserver-2016-cumulative-update-not-applicable-to-your-computer%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20not%20new%20to%20Windows%20Server%2C%20once%20I%20have%20certified%20as%20MCSE%20since%20Windows%20Server%202003.%20But%20I%20don't%20have%20a%20plan%20to%20renew%20it%20anymore.%20For%20this%20specific%20case%2C%20I%20don't%20100%25%20believe%20this%20slogan%2C%20%22empower%20every%20person%20and%20every%20organization%20on%20the%20planet%20to%20achieve%20more.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-358776%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Huajun Gu
New Contributor

Greetings,

 

I have to say I am getting annoyed when installing cumulative updates for Windows Server 2016 on an air-gaped server.

 

I have installed this server by using en_windows_server_2016_x64_dvd_9718492.iso, which means the initial version is 10.0.14393.447. I was happy at the very beginning because we have cumulative update. As the name indicates, I should have the ability to patch my server to a specific version.

 

But servicing stack update TOTALLY break this nice dream. And these servicing stack updates are not listed in update history. (https://support.microsoft.com/en-us/help/4000825).

 

Since yesterday, I have to use wsusscn.cab to check the updates that should be installed. wsusscn.cab gives following output.

 

wsusscn.png

 

I have to patch the server to the specified version to mitigate the version compatibility issue of Windows Container.

 

https://hub.docker.com/_/microsoft-windows-servercore

latestamd64No DockerfileWindows Server LTSC 201611/21/2018 17:35:2901/08/2019 20:57:57
ltsc2016amd64No DockerfileWindows Server LTSC 201610/05/2018 23:34:1102/12/2019 20:59:43
10.0.14393.2665amd64No DockerfileWindows Server LTSC 201612/11/2018 22:44:2812/11/2018 22:44:28
10.0.14393.2608amd64No DockerfileWindows Server LTSC 201611/21/2018 17:39:0711/21/2018 17:39:07

 

The issue was solved by following the hint here.

https://social.technet.microsoft.com/Forums/en-US/bb841f90-efd4-458d-aa73-9f9e1d041db7/server-2016-c...

 

I am not new to Windows Server, once I have certified as MCSE since Windows Server 2003. But I don't have a plan to renew it anymore. For this specific case, I don't 100% believe this slogan, "empower every person and every organization on the planet to achieve more."

 

Related Conversations
Extentions Synchronization
ChirmyRam in Discussions on
3 Replies
Tabs and Dark Mode
cjc2112 in Discussions on
35 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
9 Replies