.NET and .NET Framework January 2026 Servicing Updates: What Changed

Microsoft released the January 2026 servicing updates for .NET and .NET Framework on January 9, 2026. These are non-security updates—bug fixes, performance improvements, and stability enhancements.

Here's what changed and whether you need to update.

What's Included

.NET 10 (Latest)

• Runtime: 10.0.1
• SDK: 10.0.101
• ASP.NET Core: 10.0.1

.NET 9 (LTS)

• Runtime: 9.0.3
• SDK: 9.0.403
• ASP.NET Core: 9.0.3

.NET 8 (LTS)

• Runtime: 8.0.13
• SDK: 8.0.413
• ASP.NET Core: 8.0.13

.NET 6 (LTS, End of Support November 2026)

• Runtime: 6.0.39
• SDK: 6.0.439
• ASP.NET Core: 6.0.39

.NET Framework 4.8.1

• Security and Quality Rollup
• Windows 10, Windows 11, Windows Server 2019, Server 2022

Key Bug Fixes

1. JIT Compiler Optimization Bug (All Versions)

Issue: Aggressive inlining caused incorrect behavior in edge cases:

// This code would produce wrong results
public int Calculate(int x)
{
    if (x > 100)
        return x * 2;
    return x + 10;
}

// With x = 101, would sometimes return 111 instead of 202

Fix: Improved inlining heuristics to prevent over-optimization.

Impact: Rare, but could cause logic bugs in production.

2. Garbage Collector Pause Time Reduction (.NET 10)

Before: GC pauses averaged 12ms for large heaps (2GB+).

After: GC pauses reduced to 8ms (33% improvement).

How: Improved concurrent marking algorithm.

Impact:

• Lower latency for high-traffic web apps
• Smoother game performance
• Better real-time system responsiveness

3. HttpClient Connection Pool Leak (.NET 8, 9, 10)

Issue: Under specific conditions, HttpClient would leak connections:

using var client = new HttpClient();
for (int i = 0; i < 1000; i++)
{
    await client.GetAsync("https://api.example.com/data");
}
// Connections weren't properly returned to pool

Symptoms:

• "Cannot connect to remote server" after thousands of requests
• Increasing memory usage
• Socket exhaustion

Fix: Improved connection pool recycling logic.

Impact: Critical for high-throughput APIs.

4. ASP.NET Core Blazor WebAssembly Startup Hang (.NET 9, 10)

Issue: Blazor WASM apps would occasionally hang during startup on slower devices.

Fix: Optimized module initialization sequence.

Impact:

• Faster Blazor app load times (15% improvement)
• Fewer startup failures on low-end devices

5. Entity Framework Core Query Translation Bug (.NET 8, 9, 10)

Issue: Complex LINQ queries with nested Select and GroupBy translated to incorrect SQL:

var result = dbContext.Orders
    .GroupBy(o => o.CustomerId)
    .Select(g => new
    {
        CustomerId = g.Key,
        Orders = g.Select(o => o.OrderId).ToList()
    })
    .ToList();

// Generated SQL had missing JOIN, returned wrong data

Fix: Improved query compilation for nested projections.

Impact: Data integrity bugs if you used this pattern.

Performance Improvements

.NET 10 Runtime

String Operations:

• string.Contains(): 12% faster
• string.StartsWith(): 18% faster
• string.Replace(): 9% faster

Collections:

• Dictionary<TKey, TValue> lookups: 7% faster
• List<T>.Sort(): 11% faster
• HashSet<T>.Contains(): 8% faster

Async/Await:

• Task allocation overhead reduced by 5%
• ValueTask fast path improved

ASP.NET Core 10

Routing:

• Endpoint resolution: 14% faster
• Route parameter binding: 10% faster

Middleware:

• Middleware pipeline execution: 8% faster

Result:

• 50ms average request time → 44ms (12% improvement)

Blazor WebAssembly

Startup Time:

Before: 2.8s
After: 2.4s
Improvement: 14%

Rendering:

• Component rendering: 9% faster
• Event handler binding: 6% faster

Breaking Changes

None.

This is a servicing update—no API changes, no breaking behavior.

Should You Update?

Update Immediately If:

1. You use HttpClient heavily The connection pool leak affects high-throughput APIs. If you're making thousands of HTTP calls per minute, this fix is critical.

2. You're experiencing GC pauses The .NET 10 GC improvements reduce pause times by 33%. If you're building low-latency systems (games, real-time APIs), update.

3. You use the affected EF Core query pattern The nested Select/GroupBy bug causes wrong data. If you use this pattern, update and test thoroughly.

4. You run Blazor WebAssembly The startup hang is rare but frustrating. The fix makes apps load faster and more reliably.

Safe to Wait If:

1. You're on .NET 6 LTS .NET 6 support ends November 2026. If you're migrating to .NET 8 or 10 soon, wait.

2. Your app is low-traffic Performance improvements are marginal for low-traffic apps.

3. You don't use the affected features If the bugs don't affect you, there's no urgency.

How to Update

.NET Runtime

Windows:

# Download from https://dotnet.microsoft.com/download
# Or via winget
winget install Microsoft.DotNet.Runtime.10

macOS/Linux:

# Update via package manager
brew install dotnet@10  # macOS
sudo apt install dotnet-runtime-10.0  # Ubuntu

ASP.NET Core

# Update SDK (includes runtime)
dotnet sdk check
dotnet sdk install 10.0.101

.NET Framework (Windows Update)

# Check for updates
Install-WindowsUpdate -AcceptAll -AutoReboot

# Or manually download:
# KB5048790 (Windows 11)
# KB5048791 (Windows 10)

Verifying the Update

# Check installed versions
dotnet --list-runtimes
dotnet --list-sdks

# Expected output (after update):
# Microsoft.AspNetCore.App 10.0.1 [/usr/local/share/dotnet/shared/...]
# Microsoft.NETCore.App 10.0.1 [/usr/local/share/dotnet/shared/...]

For applications:

cd /path/to/your/app
dotnet --info

Check that the runtime version matches the latest.

Compatibility

.NET 6 → 8 → 9 → 10 Migration Path

These updates don't change migration paths. If you're planning to upgrade from .NET 6 to .NET 10:

Step 1: Update to .NET 6.0.39 (this release) Step 2: Test thoroughly Step 3: Migrate to .NET 8 LTS (8.0.13) Step 4: Optionally upgrade to .NET 10

.NET Framework 4.8.1

Fully compatible with:

• .NET 6, 8, 9, 10 (side-by-side)
• Windows 10, Windows 11
• Windows Server 2019, Server 2022

Known Issues (Post-Update)

1. SDK Telemetry Opt-Out Not Persisting

Symptom: After updating, telemetry re-enables even if you previously opted out.

Fix:

# Re-disable telemetry
export DOTNET_CLI_TELEMETRY_OPTOUT=1
# Add to ~/.bashrc or ~/.zshrc to persist

2. Visual Studio 2024 Compatibility

Issue: Visual Studio 2024 (not 2026) doesn't recognize .NET 10.0.1 immediately.

Fix: Update Visual Studio to latest patch:

Help → Check for Updates

Or install .NET 10 SDK separately.

3. Blazor Hot Reload Instability

Issue: After updating, Blazor hot reload occasionally fails.

Workaround:

# Restart dev server after making changes
dotnet watch run

This is being tracked and will be fixed in February 2026 servicing update.

Timeline

Released: January 9, 2026 Next Servicing Update: February 2026 (expected February 11) Next Major Release: .NET 11 (November 2026)

Conclusion

January 2026 servicing updates bring meaningful improvements:

• HttpClient connection pool fix (critical for high-throughput apps)
• GC pause time reduction (33% improvement)
• EF Core query translation fix (data integrity)
• Performance improvements (5-18% faster in various areas)

Recommendation:

• High-traffic production systems: Update immediately
• Low-traffic apps: Update within 1 month
• .NET 6 apps near end-of-support: Plan migration to .NET 8 or 10

These are non-breaking updates. Test in staging, then roll out to production.

---

Resources:

• .NET 10 Release Notes
• .NET 8 Release Notes
• .NET Framework Updates
• Download .NET