# AAR: Launcher fails to load after being closed in Secondary Screen

**URL:** <https://forums.eveonline.com/t/aar-launcher-fails-to-load-after-being-closed-in-secondary-screen/232378>\
**Category:** EVE Launcher\
**Created:** [April 14, 2020, 5:54am UTC](https://forums.eveonline.com/t/aar-launcher-fails-to-load-after-being-closed-in-secondary-screen/232378 "2020-04-14T05:54:48Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Biwako\_Acami](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/biwako_acami/32/404558_2.png) [@Biwako\_Acami](https://forums.eveonline.com/u/Biwako_Acami)\
**Post date:** [April 14, 2020, 5:54am UTC](https://forums.eveonline.com/t/aar-launcher-fails-to-load-after-being-closed-in-secondary-screen/232378/1 "2020-04-14T05:54:48Z")

</div>

I have a dual screen setup and have been having issues with the launcher, this one took me a while to understand. Just as info:

1. I play using the client installed from Steam.
2. I have Nvidia GTX 970
3. Using latest Nvidia Driver (445.75 at the time)
4. Running Windows 10 (1903)

**Re-producable problem:**

1. Move launcher to secondary screen
2. Close launcher in secondary screen
3. Launcher fails to load and ends up unresponsive showing a blank white box in lieu of the full launcher.
4. Need to close _evelauncher.exe_ and _QTWebEngineProcess.exe_ for Steam to detect game has stopped.

**My Solution:**

1. Make a backup of registry key by exporting _Computer\HKEY\_CURRENT\_USER\Software\CCP\EVE_ to a temp folder
2. Delete registry key value _LauncherWindowGeometry_ in _Computer\HKEY\_CURRENT\_USER\Software\CCP\EVE_
3. Launcher now starts properly on the primary screen

_ **Disclaimer: Do not modify registry keys if you don’t know what you’re doing! Ask someone with insight first if it would help in your case!** _

**My Notes:**

- Thanks to the _EVELogLite.exe_ application in the EVE Online folder I was able to determine that the launcher was hanging at ‘Moving launcher window to foreground’
- Since _QTWebEngineProcess.exe_ was responsive during the crash I assumed it was a QT related issue and started googling around QT issues. Some of the keywords that caught my eye were; redrawing, overdrawing.
- Other solutions from EVE Online posts mentioned deleting registry keys as a solution.
- Looking back at _EVELogLite.exe_ I saw that it was attempting ‘Setting geometry from registry value:’ before ‘Moving launcher window to foreground’
- Put 2 and 2 together I deleted the registry value _LauncherWindowGeometry_ and it started working again.

---

<div class="post-metadata">

**Author:** ![Marlene\_Dietrich](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/marlene_dietrich/32/199780_2.png) [@Marlene\_Dietrich](https://forums.eveonline.com/u/Marlene_Dietrich)\
**Post date:** [April 22, 2020, 11:26am UTC](https://forums.eveonline.com/t/aar-launcher-fails-to-load-after-being-closed-in-secondary-screen/232378/2 "2020-04-22T11:26:25Z")

</div>

Confirmed, after delete the key _LauncherWindowGeometry_ everything went back to normal

---

<div class="post-metadata">

**Author:** ![Kiab\_Pathfinder](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/kiab_pathfinder/32/201165_2.png) [@Kiab\_Pathfinder](https://forums.eveonline.com/u/Kiab_Pathfinder)\
**Post date:** [April 29, 2020, 1:47am UTC](https://forums.eveonline.com/t/aar-launcher-fails-to-load-after-being-closed-in-secondary-screen/232378/3 "2020-04-29T01:47:38Z")

</div>

Hi, just changed the language from French to English, couldn’t connect to serveur anymore.

Did what the original post said, and it worked fine just after. Ty.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/eveonline/original/3X/4/1/41ec4921cbaca7a6f9ea556e7cc20018461eae5e.png) [@system](https://forums.eveonline.com/u/system)\
**Post date:** [July 28, 2020, 1:47am UTC](https://forums.eveonline.com/t/aar-launcher-fails-to-load-after-being-closed-in-secondary-screen/232378/4 "2020-07-28T01:47:39Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
