I realize my wording is a tad confusing. What I meant to say is the only thing I have attempted to install after a clean wipe is Veeam Endpoint. I also neglected to share the fact that I have already tried rebooting.

I've come across this exact same problem when installing it on a Windows 7 32-bit system. Checked Microsoft forums and cleared the "RunOnce" registry values which did not help. System has already been restarted several times. No pending updates of any kind from any software vendor.

For the record, I just encountered this with the latest version of Veeam Endpoint Backup on 2 different Windows 2008 R2 servers.

The setup installer seems to be checking 2 registry keys/values. If either are present, it throws this error (waiting for a restart), even if you have already restarted.

For some reason, on some servers, either key/value is supposed to be deleted on reboot, but sometimes they don't. I don't know why.

The registry keys are:

HKLM\System\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations <- this last entry is a DWORD inside the Session Manager key
HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired <- this last entry is a key, with 1 or more DWORDs inside of it.

If you have rebooted and are still getting this error, it should be safe to delete the above registry values (delete just the DWORD for the 1st, and the whole key in the case of the 2nd, not just the DWORDs inside of it) - (standard disclaimer: as with any registry edit, do this at your own risk, I am not responsible for any damage, etc). I did this on 2 servers and was then able to run the installer as normal.

Hi Dima, i got exactly the same issue. I found many request for a solution to this issue, but none of the forum post mention how to solve it. All of them send you to talk with support team, so really its not so helpfull.

Can you please share with me the workaround to allow me to install the Veeam B&R???
Thanks in advance. Robert

Since the root cause might be different across cases and our ability to troubleshoot through the forums is limited, we always recommend to discuss each technical issue independently with our technical support engineers - they will be happy to help! Once you have a case ID, please let us know it - we'll keep an eye on it.