Need admin logon to run - BGEE GOG version
BillyYank
Member Posts: 2,768
Last year when I first bought BGEE from GOG, I had this problem. Trying to run the game from GOG Galaxy produced a crash. Running from Baldur.exe brought up a security dialog, and the game would run once I typed in the Admin credentials. I found the solution in a registry key:
When I installed the 2.1 update, the registry key reverted to the incorrect setting and I had to change it again to run the game normally.
I'm just putting this out here in case anyone else has the same problem. I have all three vendors' versions and this only happened on GOG's BGEE. BG2EE and IWDEE from GOG both run normally.
I had already checked the permissions to the install directory, and when I double checked just now, I saw that none of the files had been updated since install anyway, so it couldn't have been that.
I wondered if perhaps the save file location had been hard coded to the Admin profile location during installation, so I started looking for an .ini or config file. When I couldn't find one, I thought of the registry. I searched the registry for "baldur" and found a suspicious setting.
In HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers are entries for all my GOG games. BGIIEE and IWDEE are set to HIGHDPIAWARE while BGEE was set to ~WIN7RTM RUNASADMIN. I changed BG to match the other two and made the same change in HKU\(SID)\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers.
Started up BG and it just works! I did a quick test and I can start a new game, save and load games. I suppose there's a possibility that this might cause a problem down the line, but I'm cautiously optimistic.
I wondered if perhaps the save file location had been hard coded to the Admin profile location during installation, so I started looking for an .ini or config file. When I couldn't find one, I thought of the registry. I searched the registry for "baldur" and found a suspicious setting.
In HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers are entries for all my GOG games. BGIIEE and IWDEE are set to HIGHDPIAWARE while BGEE was set to ~WIN7RTM RUNASADMIN. I changed BG to match the other two and made the same change in HKU\(SID)\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers.
Started up BG and it just works! I did a quick test and I can start a new game, save and load games. I suppose there's a possibility that this might cause a problem down the line, but I'm cautiously optimistic.
When I installed the 2.1 update, the registry key reverted to the incorrect setting and I had to change it again to run the game normally.
I'm just putting this out here in case anyone else has the same problem. I have all three vendors' versions and this only happened on GOG's BGEE. BG2EE and IWDEE from GOG both run normally.
0