DPM 2025 UR1 fails to install

Wow, thank you! This is one of the most helpful answers I've seen on this site, it's an actual intelligent response, instead of an AI bot suggesting to run sfc /scannow!

I managed to get DPM UR1 to install by re-installing the c++ redist package from the original DPM 2025 installer files (inside the redist folder). I am unsure how to obtain the original version you refer to as it didn't appear to be on MSDN. After installing the update the C++ redist package seemed to be updated to 14.38.33135.

Be aware that after installing this update, every single job started failing with "Agent incompatible" errors, and nearly of the agent updates failed with the error that VC++ redist 2012 (not 2015 and very far out of support) needed to be installed on the machines being backed up. I'm still trying to troubleshoot this as it didn't fix it for several of the protected servers.

I would therefore have to agree with @simdoc that there seem to be some serious quality control issues with this update.

As many problems as we are having with a variety of Microsoft products today, I don't think catching that issue before release was much of a concern to them. They have broken so many things that worked fine in the past over the last year or so. Something as simple as RDP in Windows 11 24H2 and 25H2 is no longer usable if you make many RDP connections. I don't know why they broke something that was working fine for many years up to that point.

I also had the "Agent incompatible" errors for all systems after UR1, but was able to get around them by reinstalling the updated agent on all protected systems and then refreshing the agent status in the DPM console. I sometimes had to do the refresh multiple times for it to go away.

For some reason, I still have "Agent incompatible" error on a system with inactive protection. I have not been able to get rid of that one because the system is no longer available, but I still want to keep the protected content around a little longer.