Release Date:June 29, 2023
Summary
This article provides help to mitigate an issue when after installing the June 13, 2023, updates for .NET Framework and .NET, users may experience issues with how .NET Framework runtime imports X.509 Certificates.
Symptom
Scenarios using .NET Framework 3.5 will crash during startup with an access violation (code 0xc0000005) in mscorwks.dll whenever certain instrumenting profilers are active.
Resolution
This issue was addressed in out-of-band updates released June 29, 2023 and July 5th, 2023, for Windows and Windows Server versions affected by this issue. To get the standalone package for these out-of-band updates, search for the KB number in the Microsoft Update Catalog. You can manually import these updates into Windows Server Update Services (WSUS) and Microsoft Endpoint Configuration Manager. For WSUS instructions, see WSUS and the Catalog Site. For Configuration Manger instructions, see Import updates from the Microsoft Update Catalog.
If you used any workaround or mitigations for this issue, they are no longer needed, and we recommend you remove them. To remove workaround review the workaround or alternative workaround which was applied for instructions.
|
Product Version |
Update |
|
|---|---|---|
|
Windows 11, version 22H2 |
||
|
.NET Framework 3.5 |
||
|
Windows 11, version 21H2 |
||
|
.NET Framework 3.5 |
||
|
Windows Server 2022 |
||
|
.NET Framework 3.5 |
||
|
Azure Stack HCI, version 22H2 |
||
|
.NET Framework 3.5 |
||
|
Azure Stack HCI, version 21H2 |
||
|
.NET Framework 3.5 |
||
|
Windows 10 Version 22H2 |
||
|
.NET Framework 3.5 |
||
|
Windows 10 Version 21H2 |
||
|
.NET Framework 3.5 |
||
|
Windows 10 1809 (October 2018 Update) and Windows Server 2019 |
||
|
.NET Framework 3.5 |
||
|
Windows 10 1607 (Anniversary Update) and Windows Server 2016 |
||
|
.NET Framework 3.5 |
||
|
Windows Embedded 8.1 and Windows Server 2012 R2 |
||
|
.NET Framework 3.5 |
||
|
Windows Embedded 8 and Windows Server 2012 |
||
|
.NET Framework 3.5 |
||
|
Windows Embedded 7 Standard and Windows Server 2008 R2 SP1 |
||
|
.NET Framework 3.5.1 |
||
|
Windows Server 2008 SP2 |
||
|
.NET Framework 2.0, 3.0 |
||
Affected updates
The following .NET Framework and .NET versions are affected:
-
.NET Framework 2.0, 3.0, 3.5, 3.5.1, when the June 13, 2022, security update is installed.
Frequently Asked Questions (FAQs)
When was this change introduced?
This change in behavior was introduced in the June 13, 2022, security updates for .NET and .NET Framework.
Is it necessary for me to install this new update?
Installing this new update is necessary only if your application is experiencing the issue described in the "Symptom" heading at the top of this article. If you are not experiencing this issue, there is no need for you to install this update.
Does this new update replace the June 13, 2023, .NET Framework update?
No. If you are using .NET Framework, you should first install the June 13, 2023 rollup or security-only updates before installing the new June 22, 2023 update.
Information about protection and security
-
Protect yourself online: Windows Security support
-
Learn how we guard against cyber threats: Microsoft Security
