When a system powers off unexpectedly (not a clean shut down) after UDP v6.5 update 2 backup job had run, there is a chance that the BCD file could be corrupted.
If this happens, the system will boot into an error.
The exact error says: "Your PC needs to be repaired. The Boot Configuration Data for your PC is missing or contains errors. File: \Boot\BCD Error code: 0xC000014C."
To prevent this from happening, apply UDP v6.5 Update 3.
Update 3 is available via the built-in Auto-Update of the UDP Console.
For systems isolated from the Internet, offline installers are available here: UDP 6.5 Update 3 download links.
Once the UDP Console is upgraded to v6.5 Update 3, please deploy out this update to all connected RPS and Agent nodes via the built in function:
Before v6.5 Update 3 was released, the fixes P00001097 and P00001123 were available, but these are now superseded by the Update 3 release and hence should no longer be used.
If the server did not have the fix, and encounters the boot / BCD problem, please recovery the server by following these steps:
- Boot into any WinPE environment. This could either be the UDP Bare Metal Recovery boot media, or any Windows installation media with the "Repair my PC" option.
- Mount the Boot partition using the “diskpart” command. For that, you will have to find the correct partition / volume. The “Info” value of the Boot partition is “System”.
- For UEFI system:
- For BIOS system:
Once the boot partition or volume is selected, the diskpart command to mount it is
... using T as an example, though the letter could be any drive letter not yet in use.
- Run "chkdsk /f " against the mounted volume; for example "chkdsk /f T:".
Note: compared to a chkdsk on a large data volume, this step will be very quick (less than 5 seconds). This is normal, because the System volume is tiny in comparison.
- Reboot the server to confirm that everything is back to normal. Remember that the BCD problem had been caused by an unexpected power off without a clean shut down, so some startup routines will do additional checking and will take longer than after a clean reboot.
- Apply the fix P00001097 after recovering the server and then run a new full or incremental backup job to prevent this particular BCD error from occurring in the future.
Arcserve UDP v6.5 Update 2 - when installed on Windows 10 or Windows 2012 / 2012 R2
Products Not Affected:
- UDP v6.5 update 3 is not affected, as it was released to distribute P00001097 and P00001123.
- UDP v6.5 update 1 or any earlier UDP versions are not affected.
- UDP v6.5 update 2 when installed on other Windows variants is not affected.
- VM's that are backed up via UDP's agentless host-based backup plans are not affected.
Product Installation Instructions:
Apply UDP v6.5 update 3.
Previous instructions for P00001097 and P00001123 :
1. Make sure there is no running job
2. Run P00001097.exe or P00001123.exe to apply the fix
3. Submit a backup job, either full backup or incremental backup.
- An updated version of the patch P00001097 is available to download since Feb 7th 2018 for a machine with the BIOS firmware. If this new version is installed, then the patch P00001123 is not required to be applied.
- If the earlier version of the patch was installed, please install the patch P00001123. The updated P00001097 can identified by checking the properties of of the file P00001097.exe.
- Select the downloaded P00001097.exe - Right click --> "Properties->Digital Signatures" of the P00001097.exe file is 7th February 2018. ( the time might vary depending on your system clock)
Related Fix List:
Best Fix Release UDP v6.5 Update 3: UDP 6.5 Update 3 download links.
Old Fix (P00001097 - only for UDP 6.5 Update 2) is available please click here to download and apply. 2018-03-05: P00001097 was superseded by Update 3.
Old Fix (P00001123 - only for UDP 6.5 Update 2) is available please click here to download and apply. 2018-03-05: P00001123 was superseded by Update 3.