SOLVED
Home

Known issue with importing updates from the Microsoft Update Catalog on WSUS 10.0 (Windows Server 20

%3CLINGO-SUB%20id%3D%22lingo-sub-163830%22%20slang%3D%22en-US%22%3EKnown%20issue%20with%20importing%20updates%20from%20the%20Microsoft%20Update%20Catalog%20on%20WSUS%2010.0%20(Windows%20Server%2020%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-163830%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20currently%20working%20on%20a%20known%20issue%20with%20importing%20updates%20on%20WSUS%2010.0%20(Windows%20Server%202016)%20from%20the%20%3CA%20href%3D%22http%3A%2F%2Fwww.catalog.update.microsoft.com%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EMicrosoft%20Update%20Catalog%3C%2FA%3E%2C%20which%20fails%20with%20the%20following%20error%3A%20%3CEM%3E%E2%80%9CThis%20update%20cannot%20be%20imported%20into%20Windows%20Server%20Update%20Service%2C%20because%20it%20is%20not%20compatible%20with%20your%20version%20of%20WSUS%E2%80%9D.%20%3C%2FEM%3E(see%20image)%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20are%20aware%20of%20the%20%3CA%20href%3D%22https%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fwindowsserver%2Fen-US%2F122b4681-3938-405e-83f8-a7cd59ad25c1%2Fwill-this-update-kb4057142-be-made-available-in-config-manager-wsus%3Fforum%3Dwinserverwsus%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Eissue%3C%2FA%3E%20and%20presently%20working%20on%20a%20fix.%20In%20the%20meantime%2C%20the%20following%20workarounds%20can%20be%20used%20to%20unblock%20your%20deployment%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EAfter%20clicking%20on%20the%20%E2%80%9CImport%20Updates%E2%80%A6%E2%80%9D%20option%20in%20the%20WSUS%20console%2C%20an%20Internet%20Explorer%20window%20will%20open%20on%20the%20following%20URL%3A%20%3CA%20href%3D%22http%3A%2F%2Fcatalog.update.microsoft.com%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fcatalog.update.microsoft.com%2F%3C%2FA%3E...%26nbsp%3B%20%26amp%3BProtocol%3D1.20%3C%2FLI%3E%0A%3CLI%3EBefore%20proceeding%20with%20importing%20the%20updates%2C%20change%20the%20%E2%80%9C1.20%E2%80%9D%20protocol%20value%20in%20the%20URL%20to%20the%20previous%20protocol%20value%20%E2%80%9C1.8%E2%80%9D.%20The%20URL%20should%20look%20like%20this%20when%20you%E2%80%99re%20done%3A%20%3CA%20href%3D%22http%3A%2F%2Fcatalog.update.microsoft.com%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fcatalog.update.microsoft.com%2F%3C%2FA%3E...%26nbsp%3B%20%26amp%3BProtocol%3D1.8%3C%2FLI%3E%0A%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-284500%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20importing%20updates%20from%20the%20Microsoft%20Update%20Catalog%20on%20WSUS%2010.0%20(Windows%20Serve%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-284500%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20issue%20has%20been%20fixed%20(sorry%20for%20German%2C%20but%20as%20you%20can%20see%20no%20more%20warning%20is%20displayed)%3A%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F59369i5CD3D974531B10B5%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22wsus-import.png%22%20title%3D%22wsus-import.png%22%20%2F%3E%3C%2FSPAN%3EThanks%2C%3C%2FP%3E%0A%3CP%3EAndrei%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-194324%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20importing%20updates%20from%20the%20Microsoft%20Update%20Catalog%20on%20WSUS%2010.0%20(Windows%20Serve%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-194324%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Bruce%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3Ethese%202%20issues%20shouldn't%20be%20related%2C%20please%20open%20a%20support%20case%20to%20investigate%20the%20download%20issue%20or%20open%20a%20thread%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fen-US%2Fhome%3Fforum%3Dwinserverwsus%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fen-US%2Fhome%3Fforum%3Dwinserverwsus%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%2C%3C%2FP%3E%0A%3CP%3EAndrei%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-194190%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20importing%20updates%20from%20the%20Microsoft%20Update%20Catalog%20on%20WSUS%2010.0%20(Windows%20Serve%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-194190%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20has%20been%20broken%20for%205%20months.%20Seriously%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-194102%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20importing%20updates%20from%20the%20Microsoft%20Update%20Catalog%20on%20WSUS%2010.0%20(Windows%20Serve%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-194102%22%20slang%3D%22en-US%22%3E%3CP%3EChanging%20the%20protocol%20gets%20rid%20of%20the%20wrong%20version%20error%20and%20allows%20me%20to%20attempt%20to%20download%20the%20update.%26nbsp%3B%20However%2C%20every%20update%20fails%20to%20download%20with%20an%20error.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20do%20I%20download%20an%20Update%20into%20a%20Windows%20Server%202016%20WSUS%20server.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-165619%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20issue%20with%20importing%20updates%20from%20the%20Microsoft%20Update%20Catalog%20on%20WSUS%2010.0%20(Windows%20Serve%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-165619%22%20slang%3D%22en-US%22%3E%3CP%3ELinked%20here%20as%20well%3A%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fwindowsserver%2Fen-US%2F122b4681-3938-405e-83f8-a7cd59ad25c1%2Fwill-this-update-kb4057142-be-made-available-in-config-manager-wsus%3Fforum%3Dwinserverwsus%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fwindowsserver%2Fen-US%2F122b4681-3938-405e-83f8-a7cd59ad25c1%2Fwill-this-update-kb4057142-be-made-available-in-config-manager-wsus%3Fforum%3Dwinserverwsus%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Jeff Wolford
Microsoft

We are currently working on a known issue with importing updates on WSUS 10.0 (Windows Server 2016) from the Microsoft Update Catalog, which fails with the following error: “This update cannot be imported into Windows Server Update Service, because it is not compatible with your version of WSUS”. (see image)

 

We are aware of the issue and presently working on a fix. In the meantime, the following workarounds can be used to unblock your deployment:

 

  • After clicking on the “Import Updates…” option in the WSUS console, an Internet Explorer window will open on the following URL: http://catalog.update.microsoft.com/...  &Protocol=1.20
  • Before proceeding with importing the updates, change the “1.20” protocol value in the URL to the previous protocol value “1.8”. The URL should look like this when you’re done: http://catalog.update.microsoft.com/...  &Protocol=1.8
5 Replies
Highlighted

Changing the protocol gets rid of the wrong version error and allows me to attempt to download the update.  However, every update fails to download with an error. 

 

How do I download an Update into a Windows Server 2016 WSUS server.

Highlighted

This has been broken for 5 months. Seriously?

Highlighted

Hi Bruce,

 

these 2 issues shouldn't be related, please open a support case to investigate the download issue or open a thread here: https://social.technet.microsoft.com/Forums/en-US/home?forum=winserverwsus

 

Thanks,

Andrei

Highlighted
Solution

This issue has been fixed (sorry for German, but as you can see no more warning is displayed):

wsus-import.pngThanks,

Andrei