Remote Registry Fails to start causes error Windows 10

[JohnGalt1717]

If you use Direct Deploy and the user starts up a normal install without /dd on Windows 10 that's in Active Directory management you'll get an error about RemoteRegistry could not be started asking to retry endlessly on line 162 of the direct deploy script.

Given the else that it's in which appears to be standard installation I have no idea why this is being called in the first place but in any event it should handle this correctly because Windows 10 has RemoteRegistry disabled by default so no start will ever allow it to run.

[FrancescoT]

Dear JohnGalt1717,

Remote Registry is disabled by default with all Windows versions (eg. Win XP SP3 has by default Remote Registry disabled).
Consequently, of course Remote Registry must be enabled before to issue any remote call.

Regards

[JohnGalt1717]

The issue of course is that it should detect if it's needed by the command line arguments and only attempt to use it and should try and start it if and only if the command line is set. Otherwise you can't build an installer that will work for both regular users and network deploy.