Problem with tap100i0 Windows Server 2022 Standard HP Gen8 Microserver
- Thread starter townie
- Start date
All sorted. Fresh install of windows server did the trick.
Just didn't consider that considering dism and SFC completed successfully. I assumed windows was good.
Must've been a bad driver, bad config or just corrupt file somewhere.
Unless there was a fix released in a recent proxmox update.
Proxmox fully updated now and working great.
So I spoke too soon. Started happening again. After a long painful journey finally sorted. My findings below.
Windows Server Crash After March 2025 Update – Summary & Fix
Issue Summary
After applying the March 2025 cumulative update (KB5035857), Windows Server 2022 system began crashing or rebooting shortly after startup, particularly once I logged in.
Symptoms observed:
Spontaneous crashes or reboots within minutes of logon
Folder Redirection appeared to be working, but systems still crashed
Registry still referenced old, decommissioned server hostnames.
Offline Files (Client-Side Caching) was enabled
---
Root Cause
The KB5035857 update appears to trigger issues when Offline Files tries to access stale Folder Redirection paths. Even if those paths are no longer valid or in use, references in registry keys such as HKLM\...\fdeploy and SyncItemLog still cause background sync attempts, which result in crashes.
---
Problematic Update
KB5035857 – March 2025 Cumulative Update
https://support.microsoft.com/help/5035857
---
Similar Reports from Other Users
Reddit: https://www.reddit.com/r/sysadmin/comments/1bsm7cq/windows_server_2022_crash_after_update_kb5035857/
Reddit: https://www.reddit.com/r/sysadmin/comments/1bslnhg/folder_redirection_causing_server_crash/
Microsoft Q&A: https://learn.microsoft.com/en-us/a...s-server-crashes-after-march-update-kb5035857
Administrator.de (German): https://administrator.de/forum/windows-server-2022-stuerzt-ab-nach-kb5035857/
---
Fix / Workaround
Step 1: Uninstall the Update
wusa /uninstall /kb:5035857 /quiet /norestart
---
Step 2: Disable Offline Files via Group Policy
1. Open Group Policy Management
2. Navigate to:
Computer Configuration > Administrative Templates > Network > Offline Files
3. Set "Allow or Disallow use of the Offline Files feature" to Disabled
4. Also disable:
"Enable Transparent Caching"
"Administratively assigned offline files"
5. Apply with:
gpupdate /force
---
Final Recommendation
Until Microsoft provides an official patch, it’s best to:
Uninstall KB5035857
Disable Offline Files if you're using Folder Redirection
Remove registry references to retired servers
These steps stopped the crashes in our environment.
Windows Server Crash After March 2025 Update – Summary & Fix
Issue Summary
After applying the March 2025 cumulative update (KB5035857), Windows Server 2022 system began crashing or rebooting shortly after startup, particularly once I logged in.
Symptoms observed:
Spontaneous crashes or reboots within minutes of logon
Folder Redirection appeared to be working, but systems still crashed
Registry still referenced old, decommissioned server hostnames.
Offline Files (Client-Side Caching) was enabled
---
Root Cause
The KB5035857 update appears to trigger issues when Offline Files tries to access stale Folder Redirection paths. Even if those paths are no longer valid or in use, references in registry keys such as HKLM\...\fdeploy and SyncItemLog still cause background sync attempts, which result in crashes.
---
Problematic Update
KB5035857 – March 2025 Cumulative Update
https://support.microsoft.com/help/5035857
---
Similar Reports from Other Users
Reddit: https://www.reddit.com/r/sysadmin/comments/1bsm7cq/windows_server_2022_crash_after_update_kb5035857/
Reddit: https://www.reddit.com/r/sysadmin/comments/1bslnhg/folder_redirection_causing_server_crash/
Microsoft Q&A: https://learn.microsoft.com/en-us/a...s-server-crashes-after-march-update-kb5035857
Administrator.de (German): https://administrator.de/forum/windows-server-2022-stuerzt-ab-nach-kb5035857/
---
Fix / Workaround
Step 1: Uninstall the Update
wusa /uninstall /kb:5035857 /quiet /norestart
---
Step 2: Disable Offline Files via Group Policy
1. Open Group Policy Management
2. Navigate to:
Computer Configuration > Administrative Templates > Network > Offline Files
3. Set "Allow or Disallow use of the Offline Files feature" to Disabled
4. Also disable:
"Enable Transparent Caching"
"Administratively assigned offline files"
5. Apply with:
gpupdate /force
---
Final Recommendation
Until Microsoft provides an official patch, it’s best to:
Uninstall KB5035857
Disable Offline Files if you're using Folder Redirection
Remove registry references to retired servers
These steps stopped the crashes in our environment.
Last edited:
