Update, 9 September 2026: confirmed server issues
- KB5122769 — SQL Server 2025 CU8 + GDR — 17.0.4085.5
- KB5122770 — SQL Server 2025 GDR — 17.0.1135.8
- KB5122768 — SQL Server 2022 CU26 + GDR — 16.0.4275.2
- KB5122771 — SQL Server 2022 GDR — 16.0.1200.5
- KB5122772 — SQL Server 2019 CU32 + GDR — 15.0.4490.9
- KB5122773 — SQL Server 2019 GDR — 15.0.2190.7
- KB5122774 — SQL Server 2017 CU31 + GDR — 14.0.3550.4
- KB5122775 — SQL Server 2017 GDR — 14.0.2130.4
The SQL Server updates dated 8 September below list error 7416 for linked-server queries using MSDASQL with a provider string (@provstr). Only certain configurations are affected. Record the build, provider and sanitised error, never credentials. We could not retrieve the detailed workaround page, so we provide no unverified repair command. Success means the affected query works again with the same permissions.
Only KB5122768 and KB5122769 additionally list c0000005 when querying sys.dm_exec_requests during RESTORE, startup recovery or an availability-group replica coming online. Microsoft is investigating a fix; this does not establish that the issue first began in September. Conditional workaround: suspend the affected DMV query during recovery, not all monitoring. Back up the monitoring configuration first; resume after recovery and check the query and error log. Do not indiscriminately uninstall updates or change trace flags.
Exchange SE RTM: KB5121608, build 15.2.2562.49, lists two known issues. KB5126672: published .ics calendars return HTTP 500 to calendar clients although a browser receives HTTP 200; the issue originated with the August update. KB5127092: classic hybrid configured with -UseGraphApiOnly, where a remote mailbox user checks Exchange Online availability through a delegated on-premises mailbox; EWS logs 403/EXNL-GraphWebRequestProcessingException. Verify this exact scenario instead of attributing every Outlook problem to it.
Microsoft links conditional Exchange workarounds, not a confirmed permanent fix. Before IIS or routing changes, back up the current configuration and have the Exchange administrator verify prerequisites. Retest actual calendar-client synchronisation or the same delegated availability lookup. Restore the saved configuration if side effects occur. We have not tested these server changes ourselves.
Earlier findings — preserved unchanged
Checked 9 September 2026. This review of the 8 September updates separates vendor documentation from user reports. We have not performed an installation test; timing alone does not prove causation. Before changes, back up data, identify Windows version and architecture, and record the KB, error code and time.
What is supported by evidence?
Several first-hand installation reports concern KB5123099. One File History report names KB5124008, KB5122878 and KB5126052 among updates installed together; no individual culprit is established. We found no substantiated new fault reports for KB5122880, KB5122876, KB5126050 or KB5126043. This does not guarantee trouble-free operation; the individual KB5126050 page could not be retrieved. The WSUS limitations listed for KB5122871 and KB5122882 predate this Patch Tuesday.
KB5122880 · KB5122876 · KB5126043
KB5123099: installation fails with 0x8007000d
Windows Server 2016 users report invalid data and MSU files that cannot be read completely. Microsoft does not currently identify a general package defect. The following low-impact attempt addresses damaged downloads, not every cause of this error.
- During a maintenance window, check/install servicing stack update KB5122874 first. WSUS requires approval of both the SSU and KB5123099; Microsoft identifies the SSU as important for successful installation.
- Download the correct x64 file again from Microsoft Update Catalog into a new folder. Preserve the old copy. If downloads repeatedly differ, ask IT to investigate the delivery path without disabling security controls.
- Compare file size and an available publisher hash. Get-FileHash outputs hexadecimal: compare the same algorithm and representation. A Base64 SHA1 string differs visually from the same digest in hex; that alone proves nothing. Without a trusted reference, a locally calculated hash cannot authenticate a file.
- Retry only with an intact package and prerequisites met. Complete any requested restart, then verify Update History and build 14393.9512, or a higher build after a later cumulative update. If the error persists, examine CBS/DISM logs around the failure time.
Get-FileHash -LiteralPath "C:\Updates\package.msu" -Algorithm SHA256Replace the example path with the actual downloaded MSU file. Compare SHA256 only with the matching SHA256 reference.
KB5123099 · Microsoft Update Catalog · User report · Check a file hash
KB5124008: WinGet missing in an elevated terminal
GitHub issue 6497 originally describes preview KB5120998; it does not establish a new KB5124008 regression. If WinGet is missing only in an elevated terminal, open a normal terminal without Run as administrator and test winget --info. If it works, update the intended application and accept the normal elevation prompt. If absent there too, check App Installer and Microsoft’s WinGet troubleshooting. Do not disable UAC or administrator protection, or copy another profile’s paths into PATH.
KB5124008 / KB5122878 / KB5126052: File History
The single report also lists KB5126146 and KB890830; reposts are not independent confirmation. No KB-specific fix is confirmed. As a diagnostic step, reconnect the external backup drive or reselect the network destination in File History. Open Control Panel → System and Security → File History and choose Run now. Change a test file inside a folder actually covered by backup, back it up, then restore an earlier version to a different location. A recent timestamp alone is insufficient. Keep a separate copy of important files until restore works; do not delete or format existing backups.
KB5122871 / KB5122882: missing WSUS error details
Microsoft restricted detailed synchronization error reporting in older updates for security reasons. Missing details do not prove synchronization itself has failed. Check the last synchronization result/time; for actual failures inspect SoftwareDistribution.log under %ProgramFiles%\Update Services\LogFiles. Follow Microsoft’s diagnostic guidance for the specific error; this is not a promise to restore the hidden display. Do not roll back security updates just to see details. The September baseline restart for Server 2022 Azure Edition is intentional.
If the problem persists
Microsoft says KB5124008 fixes earlier Teams/new Outlook launch failures on ARM and desktop background/cursor issues. Do not mistake those for new side effects. If faults persist, give support the build, KB, architecture, error code and redacted log excerpts. Avoid blanket registry deletion, update-cache resets or removal of all September updates. The linked sources provide the latest status.