{"id":3322,"date":"2017-07-24T19:07:59","date_gmt":"2017-07-24T17:07:59","guid":{"rendered":"http:\/\/borncity.com\/win\/?p=3322"},"modified":"2020-09-15T23:35:19","modified_gmt":"2020-09-15T21:35:19","slug":"july-2017-updates-kb4025336-kb4025331-breaks-wsus","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2017\/07\/24\/july-2017-updates-kb4025336-kb4025331-breaks-wsus\/","title":{"rendered":"July 2017 Updates KB4025336\/KB4025331 breaks WSUS"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline\" src=\"http:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2013\/03\/winb.jpg\" width=\"58\" align=\"left\" height=\"58\">[<a href=\"http:\/\/www.borncity.com\/blog\/2017\/07\/22\/microsoft-juli-2017-updates-kb4025336kb4025331-als-wsus-killer\/\" target=\"_blank\" rel=\"noopener noreferrer\">German<\/a>]It seems that Updates KB4025336 for Windows Server 2012 R2 and KB4025331 for Windows Server 2012 are breaking WSUS and SCCM. Here are a few details. <\/p>\n<p><!--more--><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" alt=\"\" src=\"https:\/\/ssl-vg03.met.vgwort.de\/na\/ecda59ae7891421697bc5f7b98570de5\" width=\"1\" height=\"1\">I've been contacted by German blog reader Marco R. by e-mail \u2013 but I noticed some issues already within Microsoft forums. <\/p>\n<h2>Updates KB4025336 for Windows Server 2012 R2<\/h2>\n<p>Updates <a href=\"https:\/\/support.microsoft.com\/de-de\/help\/4025336\/windows-8-update-kb4025336\" target=\"_blank\" rel=\"noopener noreferrer\">KB4025336<\/a> is a monthly rollup f\u00fcor Windows 8.1 and Windows Server 2012 R2, released on July 11, 2017. Beside the iSCSI connection issue, I 've mentioned within my blog post <a href=\"https:\/\/borncity.com\/win\/2017\/07\/17\/windows-server-an-update-causes-iscsi-connection-issues\/\">Windows Server: an Update causes iSCSI connection issues<\/a> (fixed with <a href=\"https:\/\/borncity.com\/win\/2017\/07\/19\/windows-8-1-preview-rollup-update-kb4025335\/\">Windows 8.1 Preview Rollup Update KB4025335<\/a>), the update also breaks client's connection with WSUS.  <\/p>\n<p>I've addressed this issue within my blog post <a href=\"https:\/\/borncity.com\/win\/2017\/07\/12\/botched-updates-kb4025252-and-kb4025336-july-2017-woodyleonhard\/\">Botched Updates KB4025252 and KB4025336 (July 2017)<\/a>. German blog reader JohnRipper mentioned within <a href=\"http:\/\/www.borncity.com\/blog\/2017\/07\/11\/sicherheitsupdates-juli-2017-kurzbersicht\/#comment-46248\" target=\"_blank\" rel=\"noopener noreferrer\">a comment<\/a>, that update <a href=\"https:\/\/support.microsoft.com\/kb\/4025336\">KB4025336<\/a> (Monthly Rollup for Windows 8.1\/Windows Server 2012 R2) blocks the client's connection to WSUS. I found also a 2nd <a href=\"https:\/\/www.heise.de\/forum\/heise-Security\/News-Kommentare\/Patchday-bei-Microsoft-Erneut-SMB-Schwachstelle-geschlossen\/Probleme-mit-KB4025252-KB4025336\/posting-30691559\/show\/\" target=\"_blank\" rel=\"noopener noreferrer\">post<\/a> within German heise.de forum, dealing with the same issue. All clients reports suddenly error 0x80244008 during update search. This error code stands for (<a href=\"http:\/\/www.borncity.com\/blog\/2016\/11\/26\/windows-10-update-fehlercodes-0x8024-entschlsselt\/\" target=\"_blank\" rel=\"noopener noreferrer\">see<\/a>):  <\/p>\n<blockquote>\n<p>WU_E_PT_SOAPCLIENT_PARSEFAULT \u2013 0x80244008 \u2013 (16392) \u2013 <i>Same as SOAPCLIENT_PARSEFAULT_ERROR \u2013 SOAP client failed to parse a SOAP fault.<\/i><\/p>\n<\/blockquote>\n<p>It seems, that this update breaks something within SOAP client. The only solution known yet is uninstalling the botched update. The topic is also discussed within <a href=\"https:\/\/social.technet.microsoft.com\/Forums\/windowsserver\/en-US\/fbf4912e-5d1f-4168-832d-31102c2b0d16\/clients-failing-to-connect-to-wsus-80244008?forum=winserverwsus\">technet forum<\/a>.  <\/p>\n<h2>Update KB4025331 for Windows Server 2012<\/h2>\n<p>Update <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4025331\/windows-server-2012-update-kb4025331\" target=\"_blank\" rel=\"noopener noreferrer\">KB4025331<\/a> is a monthly rollup update for Windows Server 2012, issued at July 11, 2017. This patch shall fix Internet Explorer 10 crashes and other issues. Blog reader Marco R. informed me via e-mail about a serious issue with this update for Windows Server 2012 and WSUS. Marco wrote (I freely translated his German text):  <\/p>\n<blockquote>\n<p>Here is an information, that caused a lot of time to investigate. Beside KB4025336 for Windows 2012 R2 also Update KB4025331 for Windows Server 2012 \u2026 breaks WSUS.<\/p>\n<\/blockquote>\n<p>He did send me a screen shot with entries from <em>WindowsUpdate.log<\/em>, that he found on all Windows 7 x64 clients of a customer.  <\/p>\n<p><a href=\"http:\/\/i.imgur.com\/1ehqVuY.jpg\" target=\"_blank\" rel=\"noopener noreferrer\"><img loading=\"lazy\" decoding=\"async\" title=\"KB4025331 WSUS-Fehler\" alt=\"KB4025331 WSUS-Fehler\" src=\"http:\/\/i.imgur.com\/1ehqVuY.jpg\" width=\"671\" height=\"297\"><\/a><br \/>(Click to enlarge)  <\/p>\n<p>The log file reports several error 0x8024400D which stands for WU_E_PT_SOAP_CLIENT (Same as SOAP_E_CLIENT \u2013 SOAP client found the message was malformed; fix before resending). It indicates, that something went terrible wrong with SOAP client connection within Windows Update. I guess, the hints given <a href=\"https:\/\/web.archive.org\/web\/20181230022627\/https:\/\/www.wsus.de\/de\/0x8024400d\" target=\"_blank\" rel=\"noopener noreferrer\">here<\/a> and <a href=\"https:\/\/blogs.technet.microsoft.com\/sus\/2008\/10\/29\/wsus-clients-fail-synchronization-with-0x80244015-and-0x8024400d-errors\/\" target=\"_blank\" rel=\"noopener noreferrer\">here<\/a> won't help. Marco R wrote:  <\/p>\n<blockquote>\n<p>After installing no more Office and Windows updates could be installed from clients via SCCM. After uninstalling update <a href=\"https:\/\/support.microsoft.com\/en-us\/help\/4025331\/windows-server-2012-update-kb4025331\" target=\"_blank\" rel=\"noopener noreferrer\">KB4025331<\/a> from Windows 2012 WSUS Server, the error has been gone.<\/p>\n<\/blockquote>\n<p>Within <a href=\"https:\/\/community.spiceworks.com\/topic\/2019744-wsus-july-2017-updates\" target=\"_blank\" rel=\"noopener noreferrer\">this Spiceworks community thread<\/a> somebody addressed a similar issue, but mentioned other updates. But within <a href=\"https:\/\/social.technet.microsoft.com\/Forums\/windowsserver\/en-US\/fbf4912e-5d1f-4168-832d-31102c2b0d16\/clients-failing-to-connect-to-wsus-80244008?forum=winserverwsus\" target=\"_blank\" rel=\"noopener noreferrer\">this Technet thread<\/a> update KB4022720 (<a href=\"https:\/\/www.borncity.com\/blog\/2017\/06\/28\/windows-78-1-preview-rollups\/\" target=\"_blank\" rel=\"noopener noreferrer\">see<\/a>) has been identifies as a root cause for WSUS error 0x80244008 (WU_E_PT_SOAPCLIENT_PARSEFAULT, same code as for SOAPCLIENT_PARSEFAULT_ERROR \u2013 SOAP client failed to parse a SOAP fault). Within this this <a href=\"https:\/\/social.technet.microsoft.com\/Forums\/windowsserver\/en-US\/fbf4912e-5d1f-4168-832d-31102c2b0d16\/clients-failing-to-connect-to-wsus-80244008?forum=winserverwsus\" target=\"_blank\" rel=\"noopener noreferrer\">MS forum thread<\/a> user LiquidVipe reported update <em>KB4025331<\/em> breaks WSUS aon Windows Server 2012.  <\/p>\n<blockquote>\n<p>My Wsus runs in Windows Server 2012 R1. Same problem here but different KB: 4025331.  <\/p>\n<p>Uninstalling solved the problem.<\/p>\n<\/blockquote>\n<p>The thread deals with the issue, that clients could not connect to WSUS to receive updates. I published these cases here, perhaps other admins can confirm this issue. If a solution is known, please feel free to drop a comment.  <\/p>\n<p><strong>Similar articles:<br \/><\/strong><a href=\"https:\/\/borncity.com\/win\/2017\/07\/17\/windows-server-an-update-causes-iscsi-connection-issues\/\">Windows Server: an Update causes iSCSI connection issues<\/a><br \/><a href=\"https:\/\/borncity.com\/win\/2017\/07\/19\/windows-8-1-preview-rollup-update-kb4025335\/\">Windows 8.1 Preview Rollup Update KB4025335<\/a><br \/><a href=\"https:\/\/borncity.com\/win\/2017\/07\/12\/botched-updates-kb4025252-and-kb4025336-july-2017-woodyleonhard\/\">Botched Updates KB4025252 and KB4025336 (July 2017)<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>[German]It seems that Updates KB4025336 for Windows Server 2012 R2 and KB4025331 for Windows Server 2012 are breaking WSUS and SCCM. Here are a few details.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,22,2],"tags":[166,945,936,195,159,569],"class_list":["post-3322","post","type-post","status-publish","format-standard","hentry","category-issue","category-update","category-windows","tag-issues","tag-kb4025331","tag-kb4025336","tag-update","tag-windows-server","tag-wsus"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/3322","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=3322"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/3322\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=3322"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=3322"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=3322"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}