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

[Members_ZqCVg6l]

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.

[Samsung_Moderator]

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.

[Members_ZqCVg6l]

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.

[Members_ZqCVg6l]

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.

[Members_ZqCVg6l]

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.

[Members_ZqCVg6l]

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.

[Members_ZqCVg6l]

Update

Over the last 24–48 hours I’ve captured a new failure mode that appears to confirm a platform‑level issue with Modern Standby, networking, and system stability on my Galaxy Book4.

1. Silent reboot during inactivity‑triggered sleep (lid open)

Today the laptop entered sleep due to inactivity (lid remained open). When I returned about an hour later, the system appeared to “wake,” but all applications were closed — Outlook, File Explorer, Notepad, browser windows, everything.
Windows sleep does not close applications, and there were no update messages, no crash dialogs, and no “unexpected shutdown” notifications.

Immediately afterward, the system behaved exactly like it had completed a full reboot, and Robocopy ran cleanly — something that only happens after a full subsystem reset.
This is the second time I’ve observed this silent‑reboot behavior.

2. Continued daily subsystem failures

Before the silent reboot, the following failures occurred (consistent with the last two weeks):

• Classic Outlook disconnected (today at 08:47)
• New Outlook disconnected (yesterday at 16:27)
• Edge and Copilot unable to connect
• OneDrive degraded (can see files but cannot open many of them)
• Notepad hanging on open/close
• Diagnostics showing repeated failures:

• WinHTTP FAIL
• TLS/Schannel TCP FAIL
• CERT/TLS FAIL
• WAM FAIL
• WebView2 FAIL

These failures occur daily and follow the same pattern.

3. Robocopy behavior confirms subsystem instability

Robocopy initially failed with network‑location errors, then later treated all Desktop files as “new,” which only happens when the SMB redirector or network stack is not initialized yet.
After the silent reboot, Robocopy ran normally with no errors.

4. Why I believe this is a platform‑level issue

The combination of:

• Silent reboot during Modern Standby
• Daily WinHTTP/TLS/WAM/WebView2 failures
• OneDrive cloud provider failures
• SMB redirector failures
• Notepad and Explorer hangs
• Outlook disconnecting at different times
• Reboots sometimes requiring forced app closures
• Subsystems only stabilizing after a full reboot

…strongly suggests a firmware or driver‑level defect, not an application or configuration issue.

Request

Could you please escalate this case to engineering?
The silent reboot during inactivity‑triggered sleep (with lid open) is especially concerning and appears to be a key indicator of a deeper platform‑level problem.

I can provide additional logs, timestamps, screenshots, and diagnostic files if needed.

[Members_ZqCVg6l]

I’m continuing to see daily system failures on my Galaxy Book4, and today’s diagnostics add several new symptoms that appear to confirm an ongoing platform‑level issue affecting Modern Standby, networking, authentication, and system stability.

1. Continued full modern‑stack failure (today’s diagnostics)

This morning’s diagnostic run again showed:

• WinHTTP FAIL (timeout)
• TLS/Schannel TCP FAIL
• CERT/TLS FAIL (timeout)
• WAM FAIL
• WebView2 FAIL (timeout)

These failures match the pattern I’ve been seeing every day for the last two weeks.

2. Outlook behavior

Before reboot:

• Both Classic and New Outlook had current email, matching my mobile Outlook.
• However, links inside emails would not open, indicating the system could not launch a browser session or URL protocol handler.
• This is consistent with the WinHTTP/WebView2 failures above.   

3. OneDrive and file I/O failures

Before reboot:

• OneDrive Gallery could see files but could not open them.
• Notepad hung when opening/closing files.
• Diagnostics took 10 minutes to run, which only happens when the system is in a degraded state.

4. Robocopy cloud‑provider errors

Robocopy failed with:

Code

ERROR 362 — The cloud file provider is not running.

This indicates the OneDrive cloud provider was not responding at all. This is a recurring failure and matches the OneDrive symptoms above.

5. Post‑reboot behavior

• Reboot was normal (1 minute 25 seconds).
• After reboot, Copilot’s Ctrl+Shift+Enter shortcut stopped working, which suggests the subsystem did not fully recover even after reboot.
• Edge and Copilot were not working before reboot.

6. NEW: Persistent failures across multiple reboots and a full shutdown

After seeing the issues above, I:

1. Rebooted again → Robocopy still failed with ERROR 362, and the Copilot shortcut was still broken.
2. Performed a full shutdown and cold start → the same failures persisted.
3. Copilot hung immediately after reboot, even after the full shutdown.

This indicates the subsystem is now failing at boot time, not just during normal operation. The cloud provider and WebView2 runtime are not initializing correctly even after a cold start.

7. Why this appears to be a platform‑level defect

Across the last two weeks, I’ve documented:

• Daily WinHTTP/TLS/WAM/WebView2 failures
• OneDrive cloud‑provider failures
• SMB redirector failures
• Notepad and Explorer hangs
• Outlook disconnecting at different times
• Silent reboot during inactivity‑triggered sleep (lid open)
• Subsystems only stabilizing after a full reboot
• And now: persistent failures across multiple reboots and a full shutdown

These failures affect multiple independent components simultaneously and point to a firmware or driver‑level issue, not an application or configuration problem.

Request

Could you please escalate this case to engineering? The combination of daily subsystem failures, cloud‑provider errors, and the recent silent reboot during sleep strongly suggests a deeper platform‑level problem that needs investigation.

I can provide additional logs, timestamps, screenshots, and diagnostic files if needed.

[Members_ZqCVg6l]

I ran another diagnostic test after performing a full shutdown and cold start, and the results show a new pattern that may help engineering identify the issue.

New diagnostic results (after cold start):

• WinHTTP: OK

• TLS handshake: OK

• Certificate validation: OK

• WAM: FAIL

• WebView2: FAIL (timeout)

This indicates that the lower layers of the networking/TLS stack are now initializing correctly after a full shutdown, but the upper layers (WAM and WebView2) are still failing to initialize even on a clean boot.

This matches the persistent symptoms I’m seeing after reboot and shutdown:

• Robocopy still fails with ERROR 362 (cloud file provider not running)

• Copilot still hangs immediately after boot

• Copilot’s Ctrl+Shift+Enter shortcut remains broken

• OneDrive still cannot open files even though they appear in the Gallery

These failures now persist across multiple reboots and a full shutdown, which suggests the subsystem is failing during the boot process itself.

Please add this new diagnostic information to the escalation request.

[Members_ZqCVg6l]

I have additional findings from the last 24 hours that further confirm a persistent platform‑level issue affecting Modern Standby, wake behavior, and subsystem initialization on my Galaxy Book4.

1. System collapse after several hours idle (lid open)

At approximately 9:30 PM on 4/15, I woke the laptop after several hours of inactivity. Immediately:

• Both Outlook clients showed current mail (IMAP still alive)

• Edge and Copilot had lost connection

• OneDrive/Gallery were partially functional (most photos opened, one produced a Gallery error)

• Notepad hung

• The system was clearly in a degraded state

2. Diagnostics confirmed a full subsystem failure

Diagnostics at 9:37 PM showed:

• WinHTTP FAIL (timeout)

• TLS handshake FAIL

• CERT/TLS FAIL (timeout)

• WAM FAIL

• WebView2 FAIL (timeout)

This is the same full collapse pattern I’ve been reporting.

3. Reboot behavior was abnormal

The reboot took 1 minute 48 seconds and did not require closing apps, but:

• Fingerprint login was missing initially

• After ~1 minute, the main display and two external displays lost signal

• Moving the mouse brought back only one display

• After another 30 seconds, all displays went blank again

• After waking the single display a second time, fingerprint login finally appeared

• After authenticating, all displays returned to normal

This behavior strongly suggests a failure in the wake/power‑state transition path.

4. Post‑reboot state

After logging in:

• Robocopy ran without errors (cloud provider temporarily recovered)

• Copilot’s Ctrl+Shift+Enter shortcut is still non‑functional

• System otherwise appeared stable

5. This morning’s diagnostics show the subsystem collapsed again

Diagnostics at 10:25 AM on 4/16 show the same full failure pattern:

• WinHTTP FAIL

• TLS FAIL

• CERT/TLS FAIL

• WAM FAIL

• WebView2 FAIL

This occurred even though the system had been rebooted just hours earlier.

6. Summary of the pattern

Across multiple days, I now have consistent, reproducible failures:

• System collapses after sleep or long idle

• Diagnostics show the same components failing every time

• Reboots only partially recover the system

• Fingerprint login intermittently fails to initialize

• Displays intermittently fail to re‑initialize after reboot

• Cloud provider fails → recovers → fails again

• WebView2 and WAM never fully recover

• Copilot shortcut remains broken

• Outlook IMAP is the only subsystem that consistently survives

Request

Please escalate this case to engineering. The repeated failures across sleep/wake, the full diagnostic collapses, the abnormal reboot behavior, and the persistent WAM/WebView2 failures strongly suggest a platform‑level issue involving Modern Standby or power‑state transition firmware.

I can provide additional logs, timestamps, screenshots, and diagnostic files as needed.