https://bugs.winehq.org/show_bug.cgi?id=57796
Bug ID: 57796 Summary: Testcomplete fails to authenticate license key Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: francisco278herrera@gmail.com Distribution: ---
Testcomplete fails to authenticate license key, this is not very obvious when running it on vanilla wine but if you run wine staging i believe it becomes more visible. i have attached the full console output from installation onwards using winetricks since i had difficulty saving console output for just the program. i ran the installer which then opens the program on it's own, the program itself starts to run with the first line that says
01f8:fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot
in the terminal.
in vanilla wine the program installs successfully then opens a browser window to obtain a license key which fails silently and the program closes, then the program refuses to open past the splash screen. when the program fails it closes with
0994:err:menubuilder:InvokeShellLinker failed to extract icon from L"C:\Program Files (x86)\SmartBear\TestComplete 15\Help\Getting Started With TestComplete 15.doc"
in the terminal
in wine staging i believe, the program behaves largely the same way but when authentication fails, the program says it failed to communicate with the backend or something similar. then when you close the program and open it again it gives an error about not being able to start or find the sentinel license? service or it gives an error about not having an active license? if i remember correctly the sentinel error appears the first time you try to open the program yourself, the license error appears the second time you try.
based on what i have seen in game anticheat, the CreateToolhelp32Snapshot is used to verify a system's integrity so it is possible the program is not running due to the sentinel? DRM not being able to determine, or failing the system's integrity, not entirely sure this can be fixed in wine since they could just look at running wine processes and determine that it's not a windows system maybe?