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.

[Members_ZqCVg6l]

Hello, I need to request escalation to Samsung engineering and a replacement evaluation for my Galaxy Book4 due to a persistent, reproducible platform‑level failure that has continued for more than ten days.

I have documented the issue daily with diagnostics, timestamps, screenshots, and subsystem behavior. The failure pattern is consistent and reproducible:

1. Daily Failure Pattern (Before Reboot)

Every morning, and now even during normal daytime use, the system enters a collapsed state with the following diagnostic results:

• WinHTTP FAIL (timeout)

• TLS handshake FAIL

• CERT/TLS FAIL (timeout)

• WAM FAIL

• WebView2 FAIL (timeout)

This failure affects all cloud‑connected and identity‑dependent components:

• Edge disconnected

• Copilot disconnected

• OneDrive partially operational

• Gallery thumbnails missing or dark

• Notepad hangs

• Classic Outlook and New Outlook lose connection

• Cloud file provider fails (Robocopy ERROR 362)

This failure occurs after sleep/idle, and now also during active use (most recently after ~2.5 hours of normal operation).

2. Reboot Behavior (Partial Recovery Only)

After reboot, the system never fully recovers. Diagnostics consistently show:

• WinHTTP OK

• TLS OK

• CERT OK

• WAM FAIL

• WebView2 FAIL (timeout)

Additional symptoms after reboot:

• Fingerprint authentication is missing until I manually select “Other options”

• Cloud provider takes minutes to initialize

• Gallery and Notepad “warm up” slowly

• Reboot times have increased from ~1:40 to 6 minutes 58 seconds during the most recent collapse

This shows the subsystem is not recovering cleanly, even after a full reboot.

3. Progression of the Defect

Over the last ten days, the issue has progressed from:

• Overnight failures → to

• Daily failures → to

• Failures during normal daytime use → to

• Increasing reboot times → to

• Identity subsystem instability (fingerprint missing) → to

• Cloud provider failures on new files

This is no longer intermittent. It is a persistent, worsening, platform‑level defect.

4. Why This Requires Engineering Review

The failure spans multiple independent subsystems:

• WinHTTP

• TLS/Schannel

• Certificate validation

• WAM (identity provider)

• WebView2

• Cloud file provider

• Windows Hello

• Display subsystem (on some reboots)

This pattern is consistent with a Modern Standby firmware defect or a motherboard‑level power‑state controller failure, not a Windows or application issue.

No amount of software troubleshooting, resets, or reinstalls can correct a hardware‑level or firmware‑level initialization defect.

5. Request for Escalation and Replacement Evaluation

Given the duration, reproducibility, and progression of this defect, I am requesting:

1. Escalation to Samsung engineering for review of the diagnostics logs and subsystem failures.

2. A replacement evaluation, as the device is no longer able to maintain a stable operating state.

I am happy to provide:

• daily diagnostic logs

• timestamps

• screenshots

• Robocopy error logs

• Outlook connection status captures

• reboot timing data

Please attach this message to my existing case and escalate to engineering for review.

Thank you.

[Members_ZqCVg6l]

Hello, I’m following up on my escalation and replacement‑evaluation request.

The issue continues to occur every day with the same failure pattern:

• Full subsystem collapse after sleep/idle (WinHTTP, TLS, CERT, WAM, WebView2 all failing)
• Partial recovery after reboot (network OK, WAM/WebView2 still failing)
• Cloud file provider failures with Robocopy error 362
• New Outlook, Edge, and Copilot losing connection
• OneDrive and Notepad degraded
• Repeated forced‑close events during reboot
• Classic Outlook is the only component that remains functional

This behavior has been consistent and reproducible for more than two weeks and is continuing to worsen. I have provided diagnostics, timestamps, and logs showing the progression.

Please confirm that my case has been escalated to Samsung engineering and that a replacement evaluation is in progress.

Thank you.

[Samsung_Moderator · Accepted solution]

Hello Members_ZqCVg6l, 
 I am so sorry to read that you are having this issue with your Galaxy Book 4.Thanks for sharing the detailed symptom breakdown. We can point you in the direction  of our service department as you have performed the troubleshooting that would have been recommended and the problems persist . We will be happy to set up a service ticket for your device. During the repair process, some content on your device may incidentally be visible to the technician, or it may be necessary to check areas on the device within which your content is located in order to verify repair quality. Samsung does not share any content located on your device unless otherwise required by law. If you do not wish Samsung to have access to this information, we recommend that you delete that information or reset you device before sending it in for repair. We also recommend you performing a full back up of your system prior to sending it for service. Please reach out to any one of pour moderators via private message with your laptops full model and serial number in order to initiate the process.