I've been using windows backup with success for many a year on a windows server 2019 machine however on the 16th March it failed and has failed ever since in running my scheduled backup either manually or at the scheduled timeslot.
The Event log shows the following:
Faulting application name: wbengine.exe, version: 10.0.17763.1282, time stamp: 0x6722838e
Faulting module name: ntdll.dll, version: 10.0.17763.1192, time stamp: 0x5854f5da
Exception code: 0xc0000374 Fault offset: 0x00000000000fb0b9
Faulting process id: 0x2704 Faulting application start time: 0x01d71cff561aab5a
Faulting application path: C:\WINDOWS\system32\wbengine.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 8ae26ee5-d04e-4037-a3ae-139112b3cf94
Faulting package full name:
Faulting package-relative application ID:
I have tried so many things to fix this issue, such as removing the windows backup feature and reinstalling it, removing backup catalogs, trying a different volume to back up too, have reinstalled the OS, preserving apps and documents and I just can't fix the issue.
The backup schedule job does a bare metal and hyperv backup for me. If I change the backup to just do a hyperv it works, if I change it to pick anything other than a bare metal it works. It appears therefore it is the bare metal backup that is causing the crash and I can't think why. The OS disk is a Samsung SSD and as far as I can tell it is working fine, Samsung magician software states all is good with it, been running for a few years in my server.
The only thing that changed on my server on the 15th March was the installation of Blue Iris CCTV software, but I can't see how that would have caused this specific backup crashing problem.
I am reluctant to uninstall it at present to see if it is the cause, as it took a while to configure, but I am running out of options.
I need a bare metal backup of my C: drive and at present I don't have one, as I deleted all previous backups in hope a complete reset would solve the issue, but it didn't.
I should also mention I don't think the issue is windows update related as nothing was installed on 15th or early 16th, other than some CPU microcode update. I did roll this back and still hit the same issue. Can someone at Microsoft please help me!