topic Galaxy Book4 – Progressive Networking Failure After Long Uptime (WinHTTP, WebView2, TLS, Outlook) in Computers

Galaxy Book4 – Progressive Networking Failure After Long Uptime (WinHTTP, WebView2, TLS, Outlook)

Members_ZqCVg6l — Tue, 31 Mar 2026 18:58:31 GMT

Hi, I need help with a reproducible system‑level networking issue on my Galaxy Book4. After the laptop has been running for a while (usually 12–24 hours), Windows networking begins to fail in a predictable sequence:
Stage 1 – WebView2 fails
• Edge and Copilot stop connecting
• Outlook still works
• Diagnostic log: “WebView2 FAIL (timeout)”

Stage 2 – WinHTTP fails
• Windows Update, OneDrive, Edge, Copilot all stop working
• Outlook still works
• Diagnostic log: “WinHTTP FAIL (timeout)”

Stage 2.5 – Authentication/TLS issue
• New Outlook stays connected
• Classic Outlook disconnects
• Encrypt column still present
• Browsers offline

Stage 3 – Full TLS/Schannel collapse
• Classic Outlook fails completely
• Encrypt column disappears
• All HTTPS traffic fails
• Diagnostic log:
• “TCP FAIL”
• “CERT/TLS FAIL (timeout)”
• “WinHTTP FAIL (timeout)”

Only a full reboot restores functionality.
I have multiple days of logs showing each stage, plus Outlook connection‑status screenshots. This appears to be a long‑uptime regression involving WinHTTP, WebView2, WAM, and Schannel/TLS.

Can this be escalated to the backend/engineering team? I can provide all logs and screenshots.
Thank you.

Re: Galaxy Book4 – Progressive Networking Failure After Long Uptime (WinHTTP, WebView2, TLS, Outlook)

Samsung_Moderator — Fri, 20 Mar 2026 18:49:03 GMT

A very detailed symptom breakdown, thanks for sharing this with us Members_ZqCVg6l. While we do not have a way to forward this to our engineers, but we can point you in the right direction. This doesn't feel like a physical WiFi or Ethernet hardware error, since these programs are failing only gradually. Instead, it sounds like the Windows apps are getting clogged up with system files or network drivers.

There should be a way to refresh Windows without losing data (We still recommend backing up all data, just in case). Try doing a Windows refresh and see if this helps resolve this concern. You can do that by following the steps below. If this doesn't help, or if the issue comes back; I would recommend reaching out to Microsoft for further assistance.

Steps to Refresh Windows (Keep Files)
1) Open Settings: Press Windows Key + I or click the Start button and select the gear icon.
2) Navigate to Recovery:
- Windows 11: Go to System > Recovery.
- Windows 10: Go to Update & Security > Recovery.
3) Reset PC: Under "Reset this PC", click Reset PC (or "Get Started").
4) Choose "Keep my files": Select this option to retain your data, personal files, and settings.
5) Reinstall Method: Choose between Cloud download (downloads fresh system files) or Local reinstall (uses existing files).
6) Finalize: Follow the prompts, review the changes, and click Reset. The PC will restart and begin the process.

Re: Galaxy Book4 – Progressive Networking Failure After Long Uptime (WinHTTP, WebView2, TLS, Outlook)

Members_ZqCVg6l — Fri, 20 Mar 2026 19:28:02 GMT

Thanks for the response. I’ve already performed the standard troubleshooting steps, including network resets, driver updates, and a full Windows reinstall earlier in the troubleshooting process. The issue persists and is reproducible across multiple days.

This is not a Wi‑Fi or router issue. The failures occur inside Windows networking subsystems (WinHTTP, WebView2, WAM, and Schannel/TLS). The diagnostic logs I posted show:

- WinHTTP timeouts
- WebView2 endpoint failures
- TCP handshake failures
- Certificate validation failures
- TLS/Schannel timeouts

These failures occur progressively after uptime, and today the failure occurred within two hours of a reboot. The reboot itself took seven minutes, indicating a system service or driver hang.
This appears to be a system‑level defect affecting the Galaxy Book4 platform. Could you please escalate this to the backend/engineering team for review? I can provide additional logs if needed.
Thank you.

Re: Galaxy Book4 – Progressive Networking Failure After Long Uptime (WinHTTP, WebView2, TLS, Outlook)

Members_ZqCVg6l — Fri, 20 Mar 2026 19:40:51 GMT

Additional note:
I also have an HP desktop running the same Windows 11 25H2 build (26200.7462). It has been running continuously without any of the WinHTTP, WebView2, WAM, or TLS/Schannel failures I’m seeing on the Galaxy Book4. This strongly suggests the issue is specific to the Galaxy Book4 platform (drivers, firmware, or Modern Standby behavior), not Windows itself.

Thank you for your help.

Re: Galaxy Book4 – Progressive Networking Failure After Long Uptime (WinHTTP, WebView2, TLS, Outlook)

Members_ZqCVg6l — Sun, 22 Mar 2026 16:29:42 GMT

I added an additional note before, but I don't see it here, so I'm adding it again.

I also have an HP desktop running the same Windows 11 25H2 build (26200.7462). It has been running continuously without any of the WinHTTP, WebView2, WAM, or TLS/Schannel failures I’m seeing on the Galaxy Book4. This strongly suggests the issue is specific to the Galaxy Book4 platform (drivers, firmware, or Modern Standby behavior), not Windows itself.

Re: Galaxy Book4 – Progressive Networking Failure After Long Uptime (WinHTTP, WebView2, TLS, Outlook)

Members_ZqCVg6l — Mon, 30 Mar 2026 15:36:33 GMT

Update – Additional 5‑day pattern of reproducible failures

I’ve continued monitoring the issue over the last several days, and I now have a consistent, reproducible pattern of failures occurring shortly after reboot. Here is a summary of the most recent data:

1. Daily subsystem failures immediately after reboot
For five consecutive mornings (3/26–3/29), the diagnostic script shows:
• WinHTTP FAIL (timeout)
• TLS/Schannel handshake does not initialize
• Classic Outlook IMAP sessions enter “Connecting” or partial “Established/Connecting” states
• Reconnect button appears even when one IMAP session still shows “Established”
This indicates the networking subsystem is coming up in a degraded state immediately after boot.

2. Classic Outlook partial failures
On 3/29, Classic Outlook appeared healthy at 10:40, but the Reconnect button was available. This suggests a partial IMAP session failure even though one connection still showed “Established.”
By 10:43, Classic Outlook was fully disconnected, and the diagnostic log again showed WinHTTP FAIL.

3. New Outlook fails earlier than Classic Outlook
New Outlook lost connection between 09:44 and 10:24.
I confirmed this by checking Outlook on my mobile device — an email received at 10:24 appeared on mobile but not on the laptop.
This shows that the WAM/WinHTTP/WebView2 side of the networking stack is failing before the IMAP/TLS side.

4. Outlook had to be forcibly closed during reboot
During today’s reboot, Windows displayed a message that Outlook had to be closed before restarting. This suggests a hung thread or stalled subsystem call.

5. Reboots are sometimes slow, sometimes normal
• One reboot earlier in the week took 7 minutes
• Other reboots have been normal
• The subsystem failure occurs regardless of reboot speed

6. This issue does not occur on my HP desktop running the same Windows 11 build
My HP desktop (same OS version, same network, same environment) does not exhibit any of these failures. This strongly suggests the issue is specific to the Galaxy Book4 platform (drivers, firmware, or Modern Standby behavior), not Windows itself.

Request
Given the consistent 5‑day pattern, the reproducible subsystem failures, and the fact that this does not occur on my other Windows 11 device, could this please be escalated to the backend/engineering team for review? I can provide all diagnostic logs, timestamps, and Outlook connection status screenshots.

Thank you.