When you emailed support@larian.com, did you include a link to this topic? It isn't a big deal, but could help them if there is any additional information or troubleshooting feedback added here that you may not have included with your email.
There is a patch to convert D2:ED + FoV to DKS, but I don't think it has been officially released yet (there was a call for beta testers a little over a month ago). Maybe DKS would not exhibit the same problem, if you can not otherwise fix it.
Is there an error message or anything trying to start the game the second time?
When you re-installed the game, did you need to re-enter the serial number for FoV? If so, there could be a problem with the copy protection, where it works when it needs to be activated, but there is some glitch with subsequent checks.
There could be a problem creating a configuration file, or something. Perhaps deleting it would allow the game to start again; there is at least a graphicsoptions.xml file that you can try renaming or deleting.
In XP the saves are in the folder below, while the configuration file(s) are either in the Divinity 2 folder or a different subfolder (not sure, I don't have the PC version).
C:\Documents and Settings\ %username% \Local Settings\Application Data\Divinity 2\Savegames
or in Vista / Win 7
C:\Users\ %username% \AppData\Local\Divinity 2\Savegames
You may need to set Windows Explorer to show hidden files and folders (
XP, Vista,
Win 7).
You could try re-installing the game again, then use a program to scan the install and user folders before and after running the game, to see which files were changed or added.
FileCheck (
download 194KB) is a small freeware program (no install required) to calculate the CRC-32 values (the cyclic redundancy check used in zip files) of a number of files, and also verify files against an existing CRC file.
DVDsig is a very small (10KB) freeware program (also no install required) to calculate or verify the MD5 values (similar to CRC-32, but more accurate) of files. The program is not as flexible as FileCheck, given its specific purpose design, but it would work fine for this, and is simpler to use.
