none
Microsoft Security Updates cause BizTalk Admin Console errors: An internal failure occurred for unknown reasons (WinMgmt) RRS feed

  • Question

  • After applying this months security patches we get the below errors in the BizTalk Admin Console when either refreshing the Group Overview or trying to view any of the Platform Settings on both BizTalk 2010 (CU9) and BizTalk 2013 R2 (CU6).

    We tried restarting Windows Management Instrumentation and also rebooting the server, no change.

    Apart from rolling back the security patches and seeing it that resolves it, and re-installing them one by one, is there any other way to diagnose what is causing the issue?

    And how to resolve it?  We did find this blog that resolved a similar error by running a repair from the installer.

    1) Failed to load Group [dbhost:BizTalkMgmtDb] data providers. (Microsoft.BizTalk.Administration.SnapIn)

    Additional Information:

    Failed to load Group [dbhost:BizTalkMgmtDb] data providers.
    (Microsoft.BizTalk.Administration.SnapIn)
    An internal failure occurred for unknown reasons. (WinMgmt)

    2) Failed to create a BizTalkdDBVersion COM component installed with a BizTalk server.

    Class not registered (WinMgmt)

    3) An internal failure occurred for unknown reasons. (WinMgmt)




    Thursday, July 12, 2018 1:35 AM

Answers

  • I, too, reported this issue to Microsoft. I was provided the workarounds here plus one I don't see. You can make a one-line change to BTSWMISchema.mof, recompile and restart WMI.

    I personally prefer this over wholesale removing a patch that may actually fix other things or escalating privilege on an account and everything running under it.

    1. Under the Microsoft BizTalk Server install folder, find the Bins32 folder. Inside it, you'll find BTSWMISchema.mof. I'd recommend creating a backup of it. In a text editor, change the line

    HostingModel = "NetworkServiceHost";

    to

    HostingModel = "LocalSystemHost";

    2. From a command line, issue "mofcomp BTSWMISchema.mof". "mofcomp.exe" is found under Windows\System32\wbem\. When I did it, I also specified the full path to the file, e.g., mofcomp "C:\Program Files (x86)\Microsoft BizTalk Server 2016\Bins32\BTSWMISchema.mof"

    3. Finally, restart the Windows Management Instrumentation (WinMgmt) service.

    Such deep tinkering might not be for you. For me, it was the best option.


    Sincerely, <br/> <br/> Randy S. Ridgely <br/> Former Microsoft Employee <br/> <br/> Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. <br/>

    Wednesday, July 25, 2018 1:07 PM
  • We got the same problem with BizTalk 2016 FP2 CU4.
    We uninstalled KB4338605,KB4338613,KB4338424,KB4338419 to solve this problem.

    First we tried to repair BizTalk 2016 and the repair for FP2, but this did not work.
    After uninstalling KB4338419  and a reboot the issue went away.

    • Edited by mannie1980 Thursday, July 12, 2018 9:58 AM
    • Proposed as answer by Gert Vloo Thursday, July 12, 2018 10:41 AM
    • Marked as answer by Colin Dijkgraaf Thursday, July 12, 2018 6:48 PM
    Thursday, July 12, 2018 9:54 AM
  • We uninstalled all the KBs and it resolved the issue.  We then uninstalled just one on another environment and identified it. Looks the culprits are 

    BizTalk 2013 R2

    KB4338600  Description of the Security Only update for .NET Framework 4.5.2 for Windows 8.1 and Server 2012 R2 

    and 

    BizTalk 2010

    KB4338602 Description of the Security Only update for .NET Framework 4.5.2 for Windows 7 SP1, Server 2008 R2 SP1 and Server 2008

    And then I would be wary off the below as well if you have BizTalk on Windows Server 2012

    KB4338601 Description of the Security Only update for .NET Framework 4.5.2 for Windows Server 2012

    The below KB didn't cause an issue on the BizTalk 2013 R2 environment (as BizTalk uses .Net 4.5.x)
    KB4338605 Description of the Security Only update for .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, and 4.7.1 for Windows 8.1 and Server 2012 R2  


    Update: I've listed all the KBs that I know about on my blog Microsoft Security Updates cause BizTalk Admin Console errors: An internal failure occurred for unknown reasons (WinMgmt)

    Microsoft has a blog post Advisory on July 2018 .NET Framework Updates and a KB about the issue "Access Denied" errors and applications with COM activation fail after installing July 2018 Security and Quality Rollup updates for .NET Framework

    Note: It also impacted SharePoint, IIS with classic ASP and .NET application that uses impersonation.

    Update:  Microsoft Have now released patches that address the problem. See .NET Framework July 2018 Update
    Thursday, July 12, 2018 5:31 AM
  • Also affected by this today after installing updates on our Azure BizTalk dev VMs:

    For us Security Update for MS Windows KB338814 is the culprit.

    Windows Server 2016, BizTalk 2016.

    Regards

    • Proposed as answer by mannie1980 Thursday, July 12, 2018 11:14 AM
    • Marked as answer by Colin Dijkgraaf Thursday, July 12, 2018 6:51 PM
    Thursday, July 12, 2018 11:03 AM
  • The CVE's in question:

    Depending on the operating system you're using will depend on the patch that is applicable.

    I also administer a platform remotely from Windows 10 and that's effected with KB4338825, which unhelpfully is a big bundle of updates.


    If this is helpful or answers your question - please mark accordingly.
    Because I get points for it which gives my life purpose (also, it helps other people find answers quickly)
    Read my articles on: BizTalk | .NET

    Thursday, July 12, 2018 1:36 PM
  • A KB article has been posted for this problem: https://support.microsoft.com/en-gb/help/4345913/


    • Edited by nc101 Friday, July 20, 2018 10:31 AM
    • Marked as answer by Colin Dijkgraaf Saturday, July 21, 2018 9:10 PM
    Friday, July 20, 2018 10:30 AM

All replies

  • We uninstalled all the KBs and it resolved the issue.  We then uninstalled just one on another environment and identified it. Looks the culprits are 

    BizTalk 2013 R2

    KB4338600  Description of the Security Only update for .NET Framework 4.5.2 for Windows 8.1 and Server 2012 R2 

    and 

    BizTalk 2010

    KB4338602 Description of the Security Only update for .NET Framework 4.5.2 for Windows 7 SP1, Server 2008 R2 SP1 and Server 2008

    And then I would be wary off the below as well if you have BizTalk on Windows Server 2012

    KB4338601 Description of the Security Only update for .NET Framework 4.5.2 for Windows Server 2012

    The below KB didn't cause an issue on the BizTalk 2013 R2 environment (as BizTalk uses .Net 4.5.x)
    KB4338605 Description of the Security Only update for .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, and 4.7.1 for Windows 8.1 and Server 2012 R2  


    Update: I've listed all the KBs that I know about on my blog Microsoft Security Updates cause BizTalk Admin Console errors: An internal failure occurred for unknown reasons (WinMgmt)

    Microsoft has a blog post Advisory on July 2018 .NET Framework Updates and a KB about the issue "Access Denied" errors and applications with COM activation fail after installing July 2018 Security and Quality Rollup updates for .NET Framework

    Note: It also impacted SharePoint, IIS with classic ASP and .NET application that uses impersonation.

    Update:  Microsoft Have now released patches that address the problem. See .NET Framework July 2018 Update
    Thursday, July 12, 2018 5:31 AM
  • How did you uninstall just KB4338600?

    Bill Chesnut | Microsoft Integration MVP | Mexia | Melbourne Australia http://www.biztalkbill.com | http://www.mexia.com.au

    Thursday, July 12, 2018 9:21 AM
  • We got the same problem with BizTalk 2016 FP2 CU4.
    We uninstalled KB4338605,KB4338613,KB4338424,KB4338419 to solve this problem.

    First we tried to repair BizTalk 2016 and the repair for FP2, but this did not work.
    After uninstalling KB4338419  and a reboot the issue went away.

    • Edited by mannie1980 Thursday, July 12, 2018 9:58 AM
    • Proposed as answer by Gert Vloo Thursday, July 12, 2018 10:41 AM
    • Marked as answer by Colin Dijkgraaf Thursday, July 12, 2018 6:48 PM
    Thursday, July 12, 2018 9:54 AM
  • What OS for the BizTalk 2016?

    Bill Chesnut | Azure MVP | SixPivot| Melbourne Australia https://www.biztalkbill.com | http://www.sixpivot.com..au

    Thursday, July 12, 2018 10:06 AM
  • Windows Server 2012 R2
    Thursday, July 12, 2018 10:36 AM


  • Bill Chesnut | Azure MVP | SixPivot| Melbourne Australia https://www.biztalkbill.com | http://www.sixpivot.com..au

    Thursday, July 12, 2018 10:38 AM
  • Also affected by this today after installing updates on our Azure BizTalk dev VMs:

    For us Security Update for MS Windows KB338814 is the culprit.

    Windows Server 2016, BizTalk 2016.

    Regards

    • Proposed as answer by mannie1980 Thursday, July 12, 2018 11:14 AM
    • Marked as answer by Colin Dijkgraaf Thursday, July 12, 2018 6:51 PM
    Thursday, July 12, 2018 11:03 AM
  • KB4338419, KB4338605 & KB4338424 did it for me on BizTalk 2013 R2.

    If this is helpful or answers your question - please mark accordingly.
    Because I get points for it which gives my life purpose (also, it helps other people find answers quickly)
    Read my articles on: BizTalk | .NET
    • Proposed as answer by mannie1980 Thursday, July 12, 2018 11:14 AM
    • Edited by Alastair Grant Thursday, July 12, 2018 12:19 PM
    Thursday, July 12, 2018 11:09 AM
  • Any of the update that references the 3 Security update I posted above break BizTalk depends on the OS.  This includes KB4338600, KB4338605, KB4338613, KB4338614, KB4338424, KB4338419

    Bill Chesnut | Azure MVP | SixPivot| Melbourne Australia https://www.biztalkbill.com | http://www.sixpivot.com..au

    Thursday, July 12, 2018 11:13 AM
  • I reported it to MS support and they will escalate this issue.
    Thursday, July 12, 2018 11:49 AM
  • The CVE's in question:

    Depending on the operating system you're using will depend on the patch that is applicable.

    I also administer a platform remotely from Windows 10 and that's effected with KB4338825, which unhelpfully is a big bundle of updates.


    If this is helpful or answers your question - please mark accordingly.
    Because I get points for it which gives my life purpose (also, it helps other people find answers quickly)
    Read my articles on: BizTalk | .NET

    Thursday, July 12, 2018 1:36 PM
  • We have Windows Server 2012 with BizTalk 2013 (not R2) and we removed KB4338605 and KB4338419 which allowed us to access the BizTalk Admin Console
    • Edited by Chris Y 888 Thursday, July 12, 2018 2:24 PM
    Thursday, July 12, 2018 1:58 PM
  • I reported it to MS support and they will escalate this issue.
    thank you for reporting this.
    Thursday, July 12, 2018 4:46 PM
  • Adding one more KB to the list; removed this and BizTalk is back

    KB4338819

    Environment: Windows 10

    Thursday, July 12, 2018 5:55 PM
  • How did you uninstall just KB4338600?

    Bill Chesnut | Microsoft Integration MVP | Mexia | Melbourne Australia http://www.biztalkbill.com | http://www.mexia.com.au

    Removed via the Control Panel: Add Remove Programs 
    Thursday, July 12, 2018 8:30 PM
  • How did you uninstall just KB4338600?


    Bill Chesnut | Microsoft Integration MVP | Mexia | Melbourne Australia http://www.biztalkbill.com | http://www.mexia.com.au

    Removed via the Control Panel: Add Remove Programs 
    Just a minor addition : Add Remove Programs (or Programs and Features) --> View "Installed Updates"
    Thursday, July 12, 2018 10:30 PM
  • I think you mean the Security Update  KB4338814
    Friday, July 13, 2018 8:54 AM
  • Hi,

    I am assuming all have different views / solution depends on their infrastructure, i recommend to read the important not before getting this updates from Microsoft.

    https://support.microsoft.com/en-us/help/4338419/description-of-the-security-and-quality-rollup-updates-for-net-framewo


    Hope this Helps!!!! Regards, Note: Please Mark As Answered if you satisfy with Reply.

    Friday, July 13, 2018 10:21 AM
  • We have several machines with Windows Server 2012R2 and 2919355 installed and after installing KB4338419 BizTalk Admin console still fails. And no language packs were installed after the KB4338419. So I would assume that this Important notes are not really related to the problem root cause.

    And yes, uninstalling this KB removes the issue.

    Friday, July 13, 2018 10:42 AM
  • It is indeed related to the environment where you installed the BizTalk Admin Console.

    I've the Win2016+BTS2016 FP3 CU5, then I removed the security package KB4338814. Another one is with Win2012R2+BTS2016, then I removed KB4338419,4338613,4338605. Then this work.

    Friday, July 13, 2018 1:30 PM
  • Hi Guys,

    I was facing same issue on Win7/BizTalk2013

    I had opened a ticket with Microsoft, had a call with Microsoft technical engineer and following work around resolved the issue for me:

    Go to Groups --> Administrators --> Add local Network Service to the group and restart the Server

    They are still working on a better solution for this.


    If this answers your question please mark as answer. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

    • Proposed as answer by WimanX Monday, July 16, 2018 11:21 AM
    Friday, July 13, 2018 6:33 PM
  • A nasty hack
    I would prefer to uninstall patches until the issue has been resolved properly

    /Peter

    Friday, July 13, 2018 6:39 PM
  • Hi Peter,

    Uninstalling patches did not work for me. BizTalk Group started loading but I was still getting error while trying to access the Host Instances.


    If this answers your question please mark as answer. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

    Friday, July 13, 2018 6:50 PM
  • Frustrating, thanks for the heads up

    /Peter

    Friday, July 13, 2018 9:14 PM
  • Also affected by this today after installing updates on our Azure BizTalk dev VMs:

    For us Security Update for MS Windows KB338814 is the culprit.

    Windows Server 2016, BizTalk 2016.

    Regards


    For me, on Win 2016 with BT 2016, CU5 fixed the issue. Was at CU4.
    Sunday, July 15, 2018 4:16 PM
  • For our environment Windows 2012 R2 & BizTalk 2013 R2.

    After lot of trial and errors. uninstalling KB4338605 & KB4338419 patches, and that resolved the issue.

    Monday, July 16, 2018 6:35 PM
  • While not ideal (providing NETWORK SERVICE Admin access to the server), this did work on my isolated VM environment

    • Windows Server 2008 R2 (all Updates applied; even current questionable ones - 6.1.7601)
    • BizTalk 2010 (added CU9)
    • Visual Studio 2010 (All Updates applied; including TFS 2017 adapter)

    While not ideal, for development and test environments this does work. Due to changing security I would recommend AGAINST doing this in production UNLESS the patches are deemed critical through policy and can't wait. In that case, through policy, you can limit what the Network Service account can do until the final fix is in place.

    Based on OS version some of the updates have different KB numbers so based on your platform you will have to do trial and error to verify which patch restores functionality (though ones people have success with typically will only be a few numbers higher or lower for different OS versions).

    Tuesday, July 17, 2018 6:45 AM
  • I have the same issue with KB4338814 on Windows Server 2016 with BizTalk 2013 R2. Granting the "Network Service" account as administrator brought back the BizTalk administration console. Solution is not ideal, but may be accepted as a temporary workaround.
    Tuesday, July 17, 2018 7:59 PM
  • KB4338420 produced this error in our environment - BT2010 / Win 2008 R2. We have temporarily uninstalled update, waiting for repair.

    Tuesday, July 17, 2018 8:40 PM
  • This worked for me, I didn't even need to reboot. I only did it in our dev environment though, wouldn't do it in prod, but this got administrator going and for some reason, its actually fast now!
    Tuesday, July 17, 2018 9:41 PM
  • Yesterday I received several updates on my virtal Win10 Pro with BizTalk 2016 FP2 CU4. Same error message from BizTalk admin console this morning. I uninstalled KB4345421 (a new one). Problem solved.
    • Edited by Fraggel_ejb Wednesday, July 18, 2018 7:05 AM
    Wednesday, July 18, 2018 7:05 AM
  • I uninstalled KB4338420 and had success.
    (BizTalk 2010, Windows Server 2008 R2)
    Wednesday, July 18, 2018 7:22 AM
  • Had this happen last night on my Windows Server 2016 VM. Un-installed Security update: KB4338814


    Wednesday, July 18, 2018 6:02 PM
  • We had the exact same issue on both our BizTalk Server 2013 and BizTalk Server 2013 R2 environments, and I was able to isolate it to the (3) KBs below, after uninstalling them one-by-by, followed with a reboot in-between.  Of course since I know which KBs are offending, I can know just uninstall those (3) and do a reboot.

    • KB4338419 - Update for Microsoft Windows (Elevation of Privilege)
    • KB4338613 - Security Update for Microsoft Windows (Remote Code Execution)
    • KB4338605 - Security Update for Microsoft Windows (Remote Code Execution)

    Looks like Microsoft may have a fix in mid-July:

    https://blog.sandro-pereira.com/2018/07/16/microsoft-security-updates-cause-internal-failure-occurred-for-unknown-reasons-winmgmt/


    Wednesday, July 18, 2018 8:37 PM
  • Had this same issue in BizTalk Server Configuration during a new setup/deploy of BizTalk 2013 R2.  Very thankful you guys have been onto this issue at the same time.

    Again removed patches and reboot:

    KB4338419 - Update for Microsoft Windows (Elevation of Privilege)

    • KB4338613 - Security Update for Microsoft Windows (Remote Code Execution)
    • KB4338605 - Security Update for Microsoft Windows (Remote Code Execution)

    Also did it on the SQL server as well as BizTalk's server, may not have been necessary?

    Thanks!

      
    Thursday, July 19, 2018 2:00 AM
  • Hi

    Noticed this last week after our BizTalk 360 wasn't able to monitor BizTalk host instances on production server. Although production server was not patched. Then i dicovered what you describe in test environment regarding BizTalk administartor console not working propperly. unfortunatly i took me two days before i found your post :).

    On our Windows Server 2012R2 and BizTalk 2013R2 CU9 the faulting kb was kb4338605. i did not have to uninstall KB4338613 for it to comeback and didn't have KB4338619. The same for BizTalk 360.

    Thursday, July 19, 2018 6:23 AM
  • I had the same issue on BizTalk 2016 with Windows Server 2016:

    I have uninstalled KB4345418 and the errors are gone.

    Thursday, July 19, 2018 9:07 AM
  • We had the same issue. BizTalk Server 2016 running on Windows Server 2012 R2. We had to uninstall KB4338605, KB4338613, KB4338424, and KB4338419 to fix the issue. Will there be a fix for this soon?
    Thursday, July 19, 2018 6:58 PM
  • Does anyone have any input on when there will be a hotfix that will be posted for this? Or will it just be a rollup in the next patching cycle? Any ideas?

    Thursday, July 19, 2018 8:31 PM
  • A KB article has been posted for this problem: https://support.microsoft.com/en-gb/help/4345913/


    • Edited by nc101 Friday, July 20, 2018 10:31 AM
    • Marked as answer by Colin Dijkgraaf Saturday, July 21, 2018 9:10 PM
    Friday, July 20, 2018 10:30 AM
  • same thing we have to do. 

    Thanks With Regards, Bharat Bhatia MCTS Biztalk 2010 Please Mark This As Answer If This Helps You. http://xs2bharat.wordpress.com/

    Friday, July 20, 2018 8:50 PM
  • Does anyone have any input on when there will be a hotfix that will be posted for this? Or will it just be a rollup in the next patching cycle? Any ideas?

    Microsoft have stated on their blog "We have stopped distributing the .NET Framework July 2018 updates on Windows Update and are actively working on fixing and re-shipping this month’s updates. "


    Monday, July 23, 2018 1:32 AM
  • For me KB4338420 as well as KB4338606 are causing the issue. Apart from uninstalling, did you get any solution yet? Repair as in what kind of repair. Please help!
    Monday, July 23, 2018 5:29 AM
  • We had to uninstall KB4345418.BizTalk Server 2016 running on Windows Server 2016.

    Monday, July 23, 2018 12:40 PM
  • Issue was resolved for BizTalk Server 2013 R2 after removing Security Update for Microsoft Windows (KB4338605) on Windows Server 2012 R2
    Monday, July 23, 2018 9:22 PM
  • For me KB4338420 as well as KB4338606 are causing the issue. Apart from uninstalling, did you get any solution yet? Repair as in what kind of repair. Please help!

    So far the only workaround apart from uninstalling the offending KB is the following from their Advisory on July 2018 .NET Framework Updates

    Warning: The following workarounds may make a computer or a network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend these workarounds but are providing this information so that you can implement the workarounds at your own discretion. Use these workarounds at your own risk.

    Use the following guidance as a workaround:

    • Add “NETWORK SERVICE” to the local Administrators group.


    Monday, July 23, 2018 10:42 PM
  • Thanks for all the information shared! In my case issue solved with BizTalk 2013 and Windows 2008R2 uninstalling KB4338606 & KB4338420
    Tuesday, July 24, 2018 11:18 AM
  • I, too, reported this issue to Microsoft. I was provided the workarounds here plus one I don't see. You can make a one-line change to BTSWMISchema.mof, recompile and restart WMI.

    I personally prefer this over wholesale removing a patch that may actually fix other things or escalating privilege on an account and everything running under it.

    1. Under the Microsoft BizTalk Server install folder, find the Bins32 folder. Inside it, you'll find BTSWMISchema.mof. I'd recommend creating a backup of it. In a text editor, change the line

    HostingModel = "NetworkServiceHost";

    to

    HostingModel = "LocalSystemHost";

    2. From a command line, issue "mofcomp BTSWMISchema.mof". "mofcomp.exe" is found under Windows\System32\wbem\. When I did it, I also specified the full path to the file, e.g., mofcomp "C:\Program Files (x86)\Microsoft BizTalk Server 2016\Bins32\BTSWMISchema.mof"

    3. Finally, restart the Windows Management Instrumentation (WinMgmt) service.

    Such deep tinkering might not be for you. For me, it was the best option.


    Sincerely, <br/> <br/> Randy S. Ridgely <br/> Former Microsoft Employee <br/> <br/> Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. <br/>

    Wednesday, July 25, 2018 1:07 PM
  • Thanks Randy, your solution works perfectly.
    Tuesday, July 31, 2018 7:42 PM
  • Does it work with a biztalk farm ?
    Wednesday, August 1, 2018 7:44 AM
  • Thanks Randy, your solution worked.
    Thursday, August 2, 2018 12:30 AM
  • Uninstalling KB4338606, followed by reboot helped us to resolve the issue.

    System configuration:

    OS: Win 2008R2

    BizTalk 2010 CU5

    Thursday, August 2, 2018 11:14 AM
  • We installed the released fixes for Windows Server 2012 R2 (kb4346408 and kb4346745) but the errors still persist.

    Has anyone had the same problems and found a solution?

    Thursday, August 9, 2018 8:59 AM
  • The July 2018 Security update (KB4338814, which includes the .Net "fixes") also impacts BizTalk Group configuration.

    You'll find this in the BizTalk ConfigLog:

    [2018-08-09 14:30:01:0509  Info BtsCfg] Entering function: CWMI::CreateGroup
    [2018-08-09 14:30:01:0798  Error BtsCfg] d:\bt\52584\private\source\setup\btscfg\btswmi.cpp(436): FAILED hr = c0c02402
    
    [2018-08-09 14:30:01:0798  Error BtsCfg] An internal failure occurred for unknown reasons.

    Applying the fix to the update https://support.microsoft.com/en-us/help/4346877/windows-10-update-kb4346877 corrects the issue with KB4338814.


    • Edited by Peter Nield Friday, August 10, 2018 1:07 AM
    Friday, August 10, 2018 1:06 AM
  • That´s good news but what about Windows Server 2012 R2? This update kb4346877 with fix is only for Windows 10 and Windows Server 2016. Is there chance that Microsoft do this update fix for Windows 2012 R2?
    • Edited by Milan K Tuesday, August 14, 2018 7:56 AM
    Tuesday, August 14, 2018 7:55 AM
  • That´s good news but what about Windows Server 2012 R2? This update kb4346877 with fix is only for Windows 10 and Windows Server 2016. Is there chance that Microsoft do this update fix for Windows 2012 R2?

    Take a look here for the relevant patches for your operating system:

    There doesn't appear to be a patch for the very latest versions of Windows 10, so the only solution to that is to uninstall the troublesome update and delay updates until they have resolved it.


    If this is helpful or answers your question - please mark accordingly.
    Because I get points for it which gives my life purpose (also, it helps other people find answers quickly)
    Read my articles on: BizTalk | .NET

    Tuesday, August 14, 2018 11:19 AM
  • Note that the patches listed at https://blogs.msdn.microsoft.com/dotnet/2018/07/30/net-framework-july-2018-update/ may only work if you are on the latest CU (or Feature Pack) in BizTalk.

    You can also install the August Security and Quality Rollup that will contain the fixes.

    Tuesday, August 14, 2018 10:49 PM
  • Thanks Randy. It worked 

    Agree with you,i don't want to mess with the security updates

    Wednesday, August 29, 2018 12:02 AM
  • This issue come back today after patching, and we applied the fix as per Randy Ridgely to get back to a working state.
    Wednesday, October 10, 2018 11:04 PM