Skip to the content
The Update Bureau
.NET Framework 3.5 / 4.8 .NET Framework 3.5 / 4.8 Update
Patch Tuesday

KB5037933

KB5037933: Cumulative update for .NET Framework, versions 3.5 and 4.8, on Windows 10 1809 and Windows Server 2019, May 2024. Three SQL CLR hash constructors trigger errors; later fixed

In short

Runtime exceptions can occur in SQL CLR code that creates SHA256Managed, SHA384Managed, or SHA512Managed objects; KB5043804 resolves the issue. The update also addresses .NET reliability problems.

Does it affect you? Applies to: Devices running Windows 10, version 1809, or Windows Server 2019, with .NET Framework 3.5 or 4.8 installed.

File version
2.0.50727.9063 · 4.8.4729.0
Restart
Required
Review notes Additional details from the official release notes (2) Read notes
  • This page Runtime exceptions can occur in certain SQL CLR-hosted scenarios involving these hash types.
  • Known issues This issue affects certain SQL CLR-hosted scenarios involving the listed hash types.

The official sources are linked at the end of the page.

What changes

Fixes 5 changes

CLR

For: Apps querying the same managed type concurrently

  • Crashes can occur when several threads query the same managed type at once. The update addresses this issue.1
    Addresses concurrent queries to the ITypeInfo implementation of the same managed type.

.NET Libraries

2 items
  • Some 32-bit devices can have much slower response times. The update addresses this issue.2
  • The update addresses an issue with validated FIPS algorithm implementations.3
    The update addresses use of MIST validated implementations of FIPS algorithms.

.NET Fundamentals

  • The update addresses a problem with wildcard formats in IIS 10.4

WPF

Verified in package

For: Apps using WPF

  • Some apps can crash when they read window text. The update addresses this issue.5
    Addresses crashes when apps call GetWindowText and GetWindowTextLength.

Known issues

  1. Resolved Affects: Everyone Resolved by KB5043804

    Microsoft received reports about .NET Framework May cumulative update causing customers to observe runtime exceptions in certain SQL CLR hosted scenarios.

    Some SQL CLR scenarios can get runtime exceptions when code creates SHA256Managed, SHA384Managed, or SHA512Managed objects. KB5043804 resolves the issue.6

    How to apply the workaround Workaround

    Mark the assembly that uses those constructors as UNSAFE, or use SQL's built-in HASHBYTES function instead.6

Technical details

Data sheet · Security · Downloads · Components Click to collapse or expand

Data sheet

Released
2024-05-14
Classification
Updates
Type
Cumulative update
Restart
Required
Replaces
KB5034624
Replaced by
KB5039886
VersionFile versionChannel
3.5 2.0.50727.9063 General availability
4.8 4.8.4729.0 General availability

Security

No vulnerabilities are listed for this update.

Downloads (Microsoft Update Catalog)

x64 Windows 10 Enterprise LTSC 2019 / Windows Server 2019
82.0 MB
windows10.0-kb5037933-x64-ndp48.msu Main update · KB5037933 SHA-1: 1813776b…bf156c
x86 Windows 10 Enterprise LTSC 2019
48.0 MB
windows10.0-kb5037933-x86-ndp48.msu Main update · KB5037933 SHA-1: 5f0eda94…964a55

Updated components

73 files changed since the previous update for the same versions.

Top changed componentsFiles
WPF22
.NET runtime (CLR)12
WCF12

Verified in package: changed files confirm WPF.

Sources

Updated
Cited passages from Microsoft's official notes (6)
  1. 1. Addresses an issue where crashes can occur if several threads all concurrently query the ITypeInfo implementation of the same managed type support.microsoft.com
  2. 2. Addresses an issue where 32-bit platform show a significant response time regression. support.microsoft.com
  3. 3. Addresses an issue to use MIST validated implementations of FIPS algorithms. support.microsoft.com
  4. 4. Addresses an issue with wildcard format changes introduced in IIS 10. support.microsoft.com
  5. 5. Addresses an issue where apps crash when calling GetWindowText and GetWindowTextLength methods. support.microsoft.com
  6. 6. This exception is due to a recent change in the implementation of the SHA256Managed, SHA384Managed, and SHA512Managed types in .NET Framework. support.microsoft.com
Checked automatically: 8 of 8 checks passed, 6 quoted passages · compared with Microsoft's page on Oct 20, 2026
  • Quotes found in the official pages: passed
  • Numbers found in the sources: passed
  • Vulnerabilities from the dossier only: passed
  • Links to allowed domains only: passed
  • Every official change covered: passed
  • Readable plain text: passed
  • Changes confirmed by the file list: passed
  • Sources agree: passed

A second AI read the text against the sources: correctness 4/5, clarity 4/5, completeness 5/5. How we work

Published by The Update Bureau. Written with AI from Microsoft's own documents, checked by rules and a second AI. How we work · Report a mistake