BUG: missing registry key
I've recently had to rebuild our primary DPM server and chose to go to 1801 > 1807 to future proof a bit! Once the production was up and running I thought it was worth backing that up to another DPM server, so I created one in Hyper-V & got to the installation phase when I had the dreaded "I couldn't find the Hyper-V tools installed" error. However, this one was different - it was looking for a registry key at HKLM\Software\Microsoft\Microsoft Data Protection Manager\Setup\HyperVPowerShell. Just out of curiosity I manually created this path in the registry & the installer sailed through. Just thought you might want to know, as this failure to identify Hyper-V & tools is a bit of a sticking point - the production instance wouldn't install until I let the DPM installer add the features, it didn't recognise them if I used PowerShell to add them manually.