![](\"http:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2015\/01\/Stop.jpg\")
Microsoft has released on July 11, 2017 two botched updates KB4025252 and KB4025336 for Internet Explorer and Windows 8.1. Here's what's wrong with these updates. Addendum: It seems that an update revision fixed some install issues.<\/p>\nMicrosoft has released on July 11, 2017 two botched updates KB4025252 and KB4025336 for Internet Explorer and Windows 8.1. Here's what's wrong with these updates. Addendum: It seems that an update revision fixed some install issues.<\/p>\n
<\/p>\n
Microsoft issued Update KB4032782<\/a> to fix this error (see IE11 printing issues in Windows are fixed (June 2017)<\/a>). But users are reporting crashes of Internet Explorer 11 during visiting several web sites.<\/p>\n On July 11, 2017 Microsoft released another fix for Internet Explorer that shall fix the crashes during visiting complex web sites.<\/p>\n I've mentioned these updates within my blog post Microsoft July 2017 patch day<\/a>.<\/p>\n Microsoft has also released cumulative update KB4025252<\/a> for Internet Explorer. This update is helpful for admins installing security-only Rollup updates for Windows 7 SP1 or Windows 8.1 and the corresponding Server variants. But it seems that this patch is botched, many users are reporting issues (at least with WSUS).<\/p>\n German blog reader Marco R. informed me via e-mail, that update KB4025252<\/a> is offered also several times via SCCM. While SCCM says, the update install fails \u2026<\/p>\n \u2026 the Windows event manager says, the update is installed successful.<\/p>\n The only workaround: Hide or block this update in WSUS or SCCM and wait, until Microsoft delivers the next fix.<\/p>\n Some German blog readers mentioned<\/a>\u00a0Microsoft has released revision 210 of\u00a0update KB4025252 on July 12, 2017 for WSUS and SCCM. Further comments posted within my German blog are saying, that multiple installs an clients via WSUS has been fixed.<\/p>\n But Microsoft hasn't updated the KB article yet.<\/p><\/blockquote>\n I also contacted blog reader Marco R., wo has send me the SCCM screenshots above. He wrote back that the revised update is offered on SCCM, bit there are still install errrors (see screenshot below).<\/p>\n Macro tries to verify it again, but till yet it seems that it hasn't been fixed for SCCM.<\/p>\n German blog reader JohnRipper points within this comment<\/a> to another issue. Update KB4025336<\/a> (Monthly Rollup f\u00fcr Windows 8.1\/Windows Server 2012 R2) blocks the clients connection to WSUS. The clients reporting error 0x80244008 during update search. This error code stands for (see Windows: How to decode update 0x8024\u2026. errors<\/a>):<\/p>\n WU_E_PT_SOAPCLIENT_PARSEFAULT – 0x80244008 – (16392) – Same as SOAPCLIENT_PARSEFAULT_ERROR – SOAP client failed to parse a SOAP fault.<\/i><\/p><\/blockquote>\nUser how installed June security updates KB4021558 or KB4022719 or KB4022725 etc. run into printing issues in Internet Explorer 11. I mentioned it within my blog post June 2017 Patches causing Internet Explorer 11 printing issues<\/a>.<\/p>\n
A fix for Internet Explorer 11 crashes (July 2017)<\/h2>\n
\n
Update KB4025252 reinstalling multiple time<\/h2>\n
\n
![\"Update-Fehler](\"http:\/\/i.imgur.com\/se1OOOD.jpg\" "\\"Update-Fehler")
<\/a>
\n(Click to resize)<\/p>\n![\"Update-Fehler](\"http:\/\/i.imgur.com\/r3NrqHw.jpg\" "\\"Update-Fehler")
<\/a>
\n(Click to resize)<\/p>\nRevised update KB4025252 fixes WSUS issue<\/h2>\n
![](\"http:\/\/i.imgur.com\/v7ieLWm.jpg\")
<\/a>(Click to resize)<\/p>\nUpdate KB4025336 blocks WSUS connections in clients<\/h2>\n