{"id":10341,"date":"2019-07-03T18:15:22","date_gmt":"2019-07-03T16:15:22","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=10341"},"modified":"2019-07-03T18:16:14","modified_gmt":"2019-07-03T16:16:14","slug":"word-2013-update-kb4475525-july-2-2019-causing-crc-error-in-wsus-and-certificate-error-with-adr-at-sccm","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2019\/07\/03\/word-2013-update-kb4475525-july-2-2019-causing-crc-error-in-wsus-and-certificate-error-with-adr-at-sccm\/","title":{"rendered":"Word 2013 Update KB4475525 (July 2, 2019) causing CRC error in WSUS and certificate error with ADR at SCCM"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" title=\"Update\" style=\"border-left-width: 0px; border-right-width: 0px; border-bottom-width: 0px; float: left; margin: 0px 10px 0px 0px; display: inline; border-top-width: 0px\" border=\"0\" alt=\"Windows Update\" src=\"https:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2015\/02\/Update.jpg\" width=\"54\" align=\"left\" height=\"54\">[German]A brief note to administrators in corporate environments. There are issues with update KB4475525 for Word 2013 (July 2, 2019). This cannot be imported in environments with WSUS or SCCM, but causes a CRC 32 or certificate error. <\/p>\n<p><!--more--><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" alt=\"\" src=\"https:\/\/vg01.met.vgwort.de\/na\/e99f6fd302c44b8195176fc23d08d95f\" width=\"1\" height=\"1\">I introduced Update <a href=\"https:\/\/support.microsoft.com\/help\/4475525\">KB4475525<\/a>  for Microsoft Word 2013 in the article <a href=\"https:\/\/borncity.com\/win\/2019\/07\/03\/microsoft-office-patchday-july-2-2019\/\">Microsoft Office Patchday (July 2, 2019)<\/a>. This update fixes an issue that causes Outlook to crash in 2013 when an incoming e-mail message contains a table. <\/p>\n<h2>There are CRC 32 errors at WSUS<\/h2>\n<p>Shortly after the publication the German edition of my article mentioned above I got feedback from German blog readers reporting issues:<\/p>\n<blockquote>\n<p><a href=\"https:\/\/www.borncity.com\/blog\/2019\/07\/03\/microsoft-office-patchday-2-juli-2019\/#comment-74195\" target=\"_blank\" rel=\"noopener noreferrer\">1:<\/a> Our WSUS reports a CRC error during download for KB4475525 32Bit.<\/p>\n<p><a href=\"https:\/\/www.borncity.com\/blog\/2019\/07\/03\/microsoft-office-patchday-2-juli-2019\/#comment-74201\" target=\"_blank\" rel=\"noopener noreferrer\">2:<\/a> The download at KB4475525 also aborts with a CRC error. The rest seems to be ok.<\/p>\n<\/blockquote>\n<p>Within <a href=\"https:\/\/www.borncity.com\/blog\/2019\/07\/03\/microsoft-office-patchday-2-juli-2019\/#comment-74195\" target=\"_blank\" rel=\"noopener noreferrer\">this comment<\/a> Reader Tobias writes:&nbsp; <\/p>\n<blockquote>\n<p>Same error when downloading the KB via WSUS  <\/p>\n<p>Error downloading the content file.<br \/>Cause: CRC verification failure.<br \/>Source file: \/d\/msdownload\/update\/software\/crup\/2019\/06\/word-x-none_fac010d01176d1a785a3b59c6cabaecb4dee4550.cab<br \/>Target file: Path:\\WSUS\\WsusContent\\50\\FAC010D01176D1A785A3B59C6CABAECB4DEE4550.cab<\/p>\n<\/blockquote>\n<p>So it doesn't seem to be a local download error. Instead, the file that Microsoft provides for synchronization with WSUS is broken. <\/p>\n<blockquote>\n<p>Reader Bernhard <a href=\"https:\/\/www.borncity.com\/blog\/2019\/07\/03\/microsoft-office-patchday-2-juli-2019\/#comment-74215\" target=\"_blank\" rel=\"noopener noreferrer\">points out<\/a> here that the update is provided as both 32 and 64 bit, although he only uses the 32 bit Office clients. <\/p>\n<\/blockquote>\n<h2>SCCM also affected<\/h2>\n<p>While writing the blog post last night, there were hardly any hits. I just came across <a href=\"https:\/\/www.reddit.com\/r\/SCCM\/comments\/c8e1yb\/adr_failure_kb_signing_issues\/\" target=\"_blank\" rel=\"noopener noreferrer\">this reddit.com thread<\/a> where someone gets a \"13875 signature error for the certificate\" in the ADR (Automatic Deployment Rules).&nbsp; <\/p>\n<blockquote>\n<p><strong>ADR failure &#8211; KB signing issues<\/strong><\/p>\n<p>anyone else experiencing issues with <a href=\"https:\/\/support.microsoft.com\/en-gb\/help\/4475525\/july-2-2019-update-for-word-2013-kb4475525\" target=\"_blank\" rel=\"noopener noreferrer\">kb4475525<\/a> where it will generate a 13875 signing certificate failure? while my ADR picked it up with a failure code, manually downloading the 32bit version via SCCM console will also fail.  <\/p>\n<p>i've been doing a fair bit of work with our SCCM system &#8211; inplace OS upgrade including flattening WSUS, and also working on the SUP side including adding the dell, hp &amp; lenovo 3rd party updates and lastnight\/today has been resync day.  <\/p>\n<p>I haven't looked into anything else yet but i beleive both the MS and 3rd party sources are working fine and it's isolated to just this KB update. I guess at this point i'm just looking for confirmation that it is the update and not something wrong with our deployment.<\/p>\n<\/blockquote>\n<p>This error is also confirmed by other users.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>[German]A brief note to administrators in corporate environments. There are issues with update KB4475525 for Word 2013 (July 2, 2019). This cannot be imported in environments with WSUS or SCCM, but causes a CRC 32 or certificate error.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,11,22],"tags":[47,2018,195,757],"class_list":["post-10341","post","type-post","status-publish","format-standard","hentry","category-issue","category-office","category-update","tag-issue","tag-kb4475525","tag-update","tag-word"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/10341","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=10341"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/10341\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=10341"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=10341"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=10341"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}