I finally had some time to do some digging and Gemini suggested that sometimes vssadmin list writers hanging may not be a permanent failure with the installation of the KB, but a result of BitLocker “suspending” I/O while it waits for a protector to be validated. And suggested cycling the protectors could clear the VSS queue.
Do this by running these commands in an Elevated Command Prompt:
Gemini said if the vssadmin list writers hang returns after a reboot it means the issue isn’t just a “stuck” protector, but a persistent policy conflict or It’s highly likely that the KB has introduced a driver-level conflict with your specific hardware/TPM firmware that a simple reset can’t bypass and one would have to resort to restarting the srevices each boot like kilrah says to do.
I went to test this theory today and re-enabled KB5083769 on the PC’s that were having the issue, installed the update and rebooted. Strange thing is none of them hang vssadmin list writers now, tried multiple reboots and backups and all backups are working nomrally. There haven’t been any new updates or even reboots since I disabled and uninstalled the KB → no idea what has changed to fix the issue.
From my side have introduced a timeout for this operation with the latest client version. So we should get better error messages instead of it just indexing forever. It does not fix the problem.
After uninstalling KB5083769 the backup worked fine. But as you know, windows will just automatically reinstall it to the client and after having done so the forever indexing returns. We somehow need to get urbackup to run with this update installed
Well as one may have predicted 3 of the 4 have stopped working and vssadmin list writers on those 3 is freezing. They have not been rebooted or anything.
I’ve upgraded the problem PC’s Client to V2.5.30, enabled logging, and done the procedure in my last post, rebooted, verified vssadmin list writers doesn’t hang.