DX4000 - Can't install ComputerConnector on Win 10 w/ Bitlocker

I have 2 new computers. They are HP laptops with Windows 10 Pro & Bitlocker.

On both of them, when I try to install the ComputerConnector, the application crashes after it prompts for the password to the server. The full cycle is: UAC Prompt, Finds Server, Wizard Info, .NET Warning, Enter Password, CRASH.

BTW, it crashes whether I supply the correct password or not.

The ClientDeploy.log gives me the best hope of finding an answer… but I haven’t found anything yet.
Also, there is NO C:\Program Files\Windows Server folder.

Can anyone help?

Here is the part of ClientDeploy.log with the error:
[2784] 160816.165229.4241: General: Failed to open IDENTITY registry key.
[2784] 160816.165229.4241: IDENTITY: Couldn’t load CertNative.dll from C:\Program Files\Windows Server\Bin\CertNative.dll. Last Error = (126)
[2980] 160816.165229.4241: ClientSetup: !!!FATAL!!! Unhandled Exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> Microsoft.WindowsServerSolutions.ClientSetup.ClientSetupException: Unexpected Error occured: DeploymentStage=InstallingPreRequistes —> System.TypeInitializationException: The type initializer for ‘NativeMethods’ threw an exception. —> System.IO.FileNotFoundException: C:\Program Files\Windows Server\Bin\CertNative.dll —> System.ComponentModel.Win32Exception: The specified module could not be found
— End of inner exception stack trace —
at Microsoft.WindowsServerSolutions.Certificates.CertManaged.NativeMethods.LoadCertNativeDll()
at Microsoft.WindowsServerSolutions.Certificates.CertManaged.NativeMethods…cctor()
— End of inner exception stack trace —
at Microsoft.WindowsServerSolutions.Certificates.CertManaged.NativeMethods.IdnToAscii(UInt32 dwFlags, String UnicodeCharStr, Int32 cchUnicodeChar, StringBuilder ASCIICharStr, Int32 cchASCIIChar)
at Microsoft.WindowsServerSolutions.Certificates.CertManaged.PunyEncodedFQDN(String FQDN)
at Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetCertServiceClient(String serverName)
at Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetMachineStatus(String serverName, String userName, String password, String machineName, Boolean& isAdmin)
at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ValidateUserTask.Run(WizData data)
at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ConnectorWizardForm.RunTasks(Object sender, DoWorkEventArgs workEventArgs)
at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ConnectorWizardForm.<m_wizardPageHomeServerCred_PageValidating>b__0(Object worker, DoWorkEventArgs workEventArgs)
at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
— End of inner exception stack trace —
at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ConnectorWizardForm.<>c__DisplayClass2.<m_wizardPageHomeServerCred_PageValidating>b__1(Object worker, RunWorkerCompletedEventArgs completedEventArgs)
at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e)
— End of inner exception stack trace —

If 2 computers are acting up I think I would check the server first using Roberts tool. You do not have a 3rd party AV on the Win 10’s?

Oh, check the date on the DX4000, not the time and make sure the windows server services are started