We've detected a regression in ThinApp 4.6.2, unfortunately.
Multiple applications are giving an Access Violation error under Windows 7 (32-bit). The error is the following:
Exception EAccessViolation in module <application.exe> at <address>.
Access violation at address <address> in module '<application.exe>'. Read of address <address>.
Attached are 3 sample trace files showing what seems to be an error in ThinApp where it calls FindNextFileW with a malformed argument.
The char array is filled with the name of the .dat file, then partly overwritten by the name of the executable and send (incorrectly) using the size of the name of the .dat file.
Or so it seems.
This occurs in 4.6.2 and 4.7.0, but not in 4.6.1.