KB5083769 is not mentioned in the available information, and there is no documented issue in the context that matches Windows 11 April 2026 cumulative update behavior, BITS timeouts, or bitsadmin freezing after idle time.
However, there are some relevant points about BITS behavior and known issues in general that can help frame the situation and what to do next:
- BITS is a core Windows component used for background file transfers and is also used by other components such as Windows Update and Outlook OAB downloads. It is designed to handle interruptions and resume transfers automatically.
- Overview and intended behavior are described in Background Intelligent Transfer Service documentation.
- When BITS is malfunctioning or its state becomes corrupted, symptoms can include:
- Inability to download files using BITS-dependent components.
- Crashes or hangs in processes interacting with BITS.
- In older versions (e.g., Windows Vista), corruption of BITS state files could even stop the host process for Windows services and break Windows Update, requiring a repair tool or update to fix the corruption.
- There are known historical issues where BITS-related bugs were confirmed by Microsoft and fixed via updates, for example:
- A BITS client resetting TCP connections on Windows 7/Windows Server 2008 R2.
- Inability to download via BITS when using certificate-based authentication on Windows Server 2008/Windows Vista.
- For Outlook OAB downloads over HTTP(S), BITS policies and service state can directly affect download success. If BITS is throttled or stopped, downloads fail until configuration or service state is corrected.
Given that:
- The issue appears only after installing KB5083769.
- Both BITS-based and SOAP-based downloads time out.
-
bitsadmin /list /allusersfreezes during the failure state. - A reboot temporarily restores normal behavior, and uninstalling KB5083769 removes the problem.
This pattern is consistent with a regression or defect in BITS or a related networking/service component introduced by that update, similar in nature (though not identical) to past BITS-related issues that were later acknowledged and fixed.
Recommended next steps based on the patterns in the provided material:
- Collect and preserve diagnostics
- Capture event logs (Application, System) around the time of the timeouts and
bitsadminfreeze. - Note exact OS build, edition, and architecture, and confirm that the issue is reproducible only with KB5083769 installed.
- Document the idle time before failure, and whether any sleep/modern standby or network changes occur in that window.
- Capture event logs (Application, System) around the time of the timeouts and
- Validate BITS service state and policies when the issue occurs
- Confirm that the Background Intelligent Transfer Service is running when downloads fail (similar to the guidance for OAB downloads).
- Check for BITS-related policies under:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\BITSand verify whether throttling or other constraints are being applied that might interact badly with the update.
- Use supported repair paths if system corruption is suspected
- Past issues with BITS state corruption on older Windows versions required a repair tool or update; on current Windows versions, the supported approach for systemic update-related corruption is to perform an in-place repair/reinstall of the current Windows version using official guidance (reinstalling the current version of Windows while keeping files and apps). This has been used in other update-failure scenarios when SFC/DISM did not show problems.
- Engage official support channels
- Because this appears to be a new regression tied to a specific cumulative update and affects core servicing components (BITS/networking), it should be escalated through official Microsoft support or the appropriate feedback channel for Windows updates, providing the diagnostics and reproduction steps above. Historical BITS issues in the context were confirmed and tracked by Microsoft in this way.
Until an official fix or updated guidance is available, the only fully supported mitigations indicated by the patterns in the context are:
- Uninstalling the problematic cumulative update (as already tested) where acceptable from a security/compliance standpoint, or
- Reinstalling/repairing the current Windows version and then re-evaluating behavior with or without the update, under guidance from support.
References:
- Background Intelligent Transfer Service
- HTTP version of the Outlook Offline Address Book (OAB) does not download
- An update is available to fix a Background Intelligent Transfer Service (BITS) crash on a Windows Vista-based computer
- A BITS client resets the TCP connection every time that it finishes downloading a range of the file in Windows 7 or in Windows Server 2008 R2
- You cannot download files by using the BITS service in Windows Server 2008 or in Windows Vista using certificate authentication
- Plethora of issues relating to windows and possibly security. - Microsoft Q&A I'm not sure where to start.
- KB5079473 fail with 0x80073712 while inplace upgrade fail with 0x8007042B - Microsoft Q&A
- Latest Security Update KB5079473 (26200.8037) Fails to Install - Microsoft Q&A
- can you fix update 26220.8138 insider preview - Microsoft Q&A