[weinerbarn]

I'm officially stumped. I have tried pretty much everything I can think of, including other versions. This is a VM which I have edited the vmx so it shows the correct code. I have turned off secure boot, installed, rebooted, applied dll and reg fix, licensed with valid key, made "x4711" file, applied Full fix, edited the service xml files, deleted the eclipse plugin, etc. When I launch the program, it asks me which driver and then I either select DoIP or CarDaq-Plus and both result in a "No access authorization code! ..." 

I have tried both connected and not connected to the internet.

Does XPT require an interface to be connected or can you launch it and mess around in the GUI w/o and active interface plugged in?

[gcs190]

Try not to remove the eclipse plugin (it's not necessary) and remember that version of XPT runs on x64, you need appinit for x32 and x64.

Check carefully the @pesona thread about the installation for newbies....

[Joe2]

I have tried installation and long key in the past on VM. Key was accepted but Xentry does not started correctly. 

I have no solution for that I have stopped to test it

I started to use native installation...

PS.
It needs any passthru drivers installed. There should be list opened during start.

[weinerbarn]

Thank you. I will go back and read the other 118 pages on the pesona thread . Appreciate the hints.

[gcs190]

Thank you. I will go back and read the other 118 pages on the pesona thread . Appreciate the hints.

Focus on the first post and make sure you do everything right, deleting the plugin is an outdated and problematic "fix" that is not necessary and that makes me think you are not taking into account the running on x64, otherwise the fellow above is right and some virtual systems give problems.

[weinerbarn]

Going to reinstall but let me just ask a couple clarifying questions since there's a lot of conflicting info around. I have a Windows 10 64bit (22H2) system. Do I only need to to perform the 64bit fix for the ConnectorAPI64.dll? I'll be honest it seems counterintuitive to put the 64 dll in the system32 dir and vice versa for the 32 in SysWOW64 ... so I want to verify.

This is all I need to do? No need to use the older XentryAPI.dll?

Copy ConnectorAPI64.dll to C:\Windows\System32
Execute ConnectorAPI64.reg

Then just follow the rest of the steps?

[weinerbarn]

Here's the fix. Ended up just running the the install.bat under the ConnectorAPI folder. The main fix is below.
Needed to add a few more lines to my vmx file in VMWare to help with VMware detection.

monitor_control.virtual_rdtsc = "FALSE"
monitor_control.restrict_backdoor = "TRUE"
isolation.tools.getPtrLocation.disable = "TRUE"
isolation.tools.setPtrLocation.disable = "TRUE"
isolation.tools.setVersion.disable = "TRUE"
isolation.tools.getVersion.disable = "TRUE"
monitor_control.disable_directexec = "TRUE"
hypervisor.cpuid.v0 = "FALSE"