File Backups Stopped Working after Windows 11 KB5083769 Undate

UrBackup Server Version 2.5.33 running on Debian Linux
Windows 11 Client Version 2.5.25

Windows forced two updates to the Windows 11 client system. The updates were KB5083769 (Cumulative update for Windows 11, version 25H2 and 24H2) and KB5082417 (Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 25H2).

File backups for the system have not worked since the updates. The backup starts and the server connects for the filelist. From the UrBackup Live Log:

04/17/26 14:12 INFO Starting scheduled incremental file backup…
04/17/26 14:12 DEBUG laptop-x Connecting for filelist…
04/17/26 14:12 DEBUG laptop-x: Waiting for filelist
04/17/26 14:12 DEBUG laptop-x: Connecting for filelist (async)…

There are no further entries until the backup eventually fails with a “CONNECT error during filelist construction (2)” error.

Things I’ve tried so far:

  • Reinstalled the UrBackup Client
  • Verified that the network is still configured “Private”
  • Verified that the third-party firewall rules for UrBackup are still configured and enabled.

My guess is that KB5083769 is the cause of this issue. I’m considering upgrading the client to Version 2.5.29. Other than that, my next option would be to back out KB5083769. I’m hesitant to do this since it’s a pretty hefty security update and includes some support for updating the expiring Bitlocker certificates.

Anyone else experiencing this issue?
Any thoughts on the usefulness of upgrading to client Version 2.5.29?
Other suggestions?

Thanks in advance for any response.

Just an update. The client was upgraded to 2.5.28. The problem still exists.

Logfiles sent to bugreports@urbackup.org

Same problem with 2.5.29, client gets stuck on indexing since the updates were applied.

debug.log (6.2 KB)

From the debug logs @mjm0722 sent, it hangs during snapshotting. @kilrah the non-debug log don’t point at any error.

Maybe use sysinternals Process Explorer to see where the thread hangs.

Maybe try creating a shadowcopy via powershell and check that this works:

Invoke-CimMethod -ClassName Win32_ShadowCopy -MethodName Create -Arguments @{ Volume = "C:\" }

If the powershell hangs, it is a Windows issue/shadow copy provider and there is nothing to be done from the UrBackup side to avoid the problem.

Guess debug.log isn’t actually a debug log then… ran enable_debug_logging.bat and here’s a subsequent run attempt.

debug.log (26.2 KB)

Powershell command works.

Looks like a different issue to me.

Well it matches “backups stopped working after that last round of Windows updates”.

Other test:

Stopped backend service

Deleted all shadow copies

Started backend service again

Initiated incremental file backup from server

This is the client log since start, no shadow copy has been created after 10ish minutes

debug.log (49.1 KB)

Windows is updating itself all the time.

Perhaps you could also send me a memory dump of the (perhaps) hanging process. Created like this https://www.barco.com/de/support/knowledge-base/2669-creating-a-dump-file-using-task-manager-for-troubleshooting-app-crashes-and-hangs

Please find the dump here:

I’m having the same issue with only the Windows 11 PCs that are using BitLocker since the 15th when that update was applied. KB5083769 does contain updates for Secure Boot for BitLocker… I have a diffrent Win 11 PC not using BitLocker and UrBackup works normally (Client V2.5.29) - has KB5083769 as well.

Clients were V2.5.26 and just wouldn’t start backups since the update. Upgraded to V2.5.29, and now are hanging at indexing. I’ve turned on debug logging and have a log of a backup starting and then sitting on indexing for 8 hours and memory dumps for both the backend service and client itself. Because these are not my PC’s I’ll email the log info to bugreports@urbackup.org

Please let me know if there is anything you would like tested.

Got one memory dump. That one hangs gathering writer metadata. What is the output of

vssadmin list writers

?

The command gets stuck and never returns on the affected machine. Re @ajcs ‘s comment this machine does have bitlocker enabled.

I let another machine with no bitlocker get updated, and can confirm the client works normally there, and vssadmin list writers returns a list instantly.

First of all, sorry to not be participating yesterday. I’m travelling this week and no longer have access to the system experiencing the problem.

You all probably already know but I’ll put it here anyway…Microsoft has admitted that the patch impacts systems with bitlocker enabled.
" The company’s latest Windows 11 cumulative updates, KB5083769 for Windows 11 24H2 and 25H2 and KB5082052 for Windows 11 26H1, can trigger an unexpected BitLocker recovery prompt after the first reboot on devices with a narrow set of enterprise-oriented settings. Microsoft says the issue is limited, the prompt is typically a one-time event, and a permanent fix is already in development. But because the affected systems are often managed endpoints, the operational impact can be disproportionate to the number of devices involved. (support.microsoft.com)"

Like others have stated in this thread, the machine I’m having issues with has bitlocker enabled. Wish I had the option of disabling it to see what happens.

Very different issue though.

I’ve put a comment on Feedback Hub and someone replied they have the same problem with other backup software. Dunno if that’ll matter but maybe upvote/add comments… Join Windows Insider – Get early access to Windows 11 features & updates

I hit the bug too after April 2026 Windows 11 update.
WARNING: SQLite: Safety level may not be changed inside a transaction in “PRAGMA synchronous = 1” errorcode: 1
ERROR: Error preparing Query [PRAGMA synchronous = 1]: Safety level may not be changed inside a transaction
WARNING: Parent of file with FRN xxx (Name “yyy”) with FRN zzz not found. Searching via MFT as fallback.
WARNING: Parent directory not found in MFT. Was probably deleted.
synchronous=FULL” errorcode: 1

after uninstall UrBackup then reinstall as New Computer Name , errors are :
WARNING: Info not found at ‘c:’ - reindexing
ERROR: Error while enumerating user “AUTORITE NT\Système” groups: 2453
WARNING: Parent of file with FRN xxx (Name “yyy”) with FRN zzz not found. Searching via MFT as fallback.
WARNING: Parent directory not found in MFT. Was probably deleted.

EDIT: UrBackup works after uninstalling April 2026 Windows update.

debug.log (6.2 KB)

Seems something happens with vss since April update.

Wow blocking specific updates in Windows11 is a horrible process (first time I’ve needed to do it) → to block an update it needs to be in the list of available updates (can’t have updates paused and the update can’t be installed already), but as soon as it is in the list WU starts downloading and installing the update. I like the old Win7 way… Uncheck done.

Well, enough complaining. I have all KB5083769 removed and blocked on all 4 of the PC’s, backups started, indexing took less than a minutes. Things back to normal for now.

I did test vssadmin list writers before and after. Before would return this and do nothing till I used CTRL+c to end it - no backups of any kind were being done when run.

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Waiting for responses.
These may be delayed if a shadow copy is being prepared.

After removing the KB it returned the list instantly.

I been looking everywhere for any info of this issue and can’t find anything that is relevant. I’m going to keep searching and will post anything I find.

Found a workaround, restart these 3 services in Powershell:

Restart-Service -Name "EventSystem" -force
Restart-Service -Name "VSS"
Restart-Service -Name "UrBackupClientBackend"

You can save that as a .ps1 script and then make a scheduled task to run at startup (I added 1 min delay) with

with parameters

-ExecutionPolicy Bypass <your_script_path>

I can also confirm that KB5083769 update is the culprit. After that update clients get stuck indexing. Uninstalled that update and everything works fine.