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

KB5037929

KB5037929: Cumulative update for .NET Framework, versions 3.5 and 4.8.1, on Windows Server 2022, May 2024. WPF window-text crashes and .NET runtime errors addressed

In short

Apps that read window text can crash, and some SQL CLR apps can hit runtime errors with specific hash types. This update also addresses issues in IIS 10 and .NET libraries.

Does it affect you? Applies to: Windows Server 2022 devices with .NET Framework 3.5 or 4.8.1 installed.

File version
2.0.50727.9176 · 4.8.9246.0
Restart
Required
Review notes Additional details from the official release notes (1) Read note
  • This page This update does not resolve the SQL CLR runtime-exception issue; Microsoft resolved it with KB5043806.

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

What changes

Fixes 6 changes

CLR

2 items
  • Crashes from simultaneous queries of the same managed type are addressed.1
    Addresses crashes when several threads query the same managed type's ITypeInfo implementation at the same time.
  • Two APIs that find methods by document position can return incorrect results in some cases; this issue is addressed.2
    Addresses incorrect results from ISymUnmanagedReader::GetMethodsFromDocumentPosition and ISymUnmanagedReader2::GetMethodsInDocument under certain circumstances.

.NET Libraries

2 items
  • An issue in the FBX file parser is addressed.3
    Addresses an issue that can be triggered in the FBX file parser.
  • FIPS algorithm checks can use MIST-validated implementations.3
    Addresses an issue to use MIST-validated implementations of FIPS algorithms.

.NET Fundamentals

  • An issue with wildcard format changes in IIS 10 is addressed.4

WPF

Verified in package

For: Apps using WPF

  • Apps can crash when they read window text; this issue is addressed.5
    Addresses crashes when apps call GetWindowText or GetWindowTextLength.

Known issues

  1. Resolved Affects: Organizations and IT administrators Resolved by KB5043806

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

    Some SQL CLR apps might get runtime exceptions when using SHA256Managed, SHA384Managed, or SHA512Managed. The issue is resolved by KB5043806; SHA1Managed, HMACSHA1, HMACSHA256, HMACSHA284, and HMACSHA512 are not affected.6

    How to apply the workaround Workaround

    Mark the assembly that uses one of the affected hash types as UNSAFE, or use SQL Server's HASHBYTES function instead of the .NET Framework SHA-2 APIs.6

    Step-by-step workaround instructions
    2 steps
    Show steps Hide steps
    Step-by-step procedure
    1. For an assembly that uses SHA256Managed, SHA384Managed, or SHA512Managed, mark it as [UNSAFE].
    2. Alternatively, use SQL Server's HASHBYTES function instead of the .NET Framework SHA-2 APIs.

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
KB5034611
Replaced by
KB5039907
VersionFile versionChannel
3.5 2.0.50727.9176 General availability
4.8.1 4.8.9246.0 General availability

Security

No vulnerabilities are listed for this update.

Downloads (Microsoft Update Catalog)

x64 Windows Server 2022
66.9 MB
windows10.0-kb5037929-x64-ndp481.msu Main update · KB5037929 SHA-1: 64db35fe…24df00

Updated components

90 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 with ISymUnmanagedReader::GetMethodsFromDocumentPosition and ISymUnmanagedReader2::GetMethodsInDocument API's might result in incorrect results under certain circumstances. support.microsoft.com
  3. 3. Addresses an issue which can be triggered in the fbx file parser. - 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. Microsoft has resolved this issue with update KB5043806. 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