Hello @DanBW
Sorry for the delayed update, but we were working on this issue, and trying to assemble all solutions and tips provided in the forum (thanks for mentioning the other posts).
So far we identified the following in our affected PC (which is a Acer Aspire A3 notebook with a i507200 CPU, 4Gb of RAM, Windows 10 Single Language 64bit 2004 build 1083, Feat. Experience pack 120.2212.3530.0, Intel HD Graphics 620 with driver ver 26.20.100.7261 1366x768 @ 60Hz , Xibo Player 2.257.2)
To start, we´ve setup a Player configuration to comply with the recommended resolution of the notebook display: 1366x768 pixels. We have even tried -1, -1, 1370, 770, with the same (undesired) results
Then we´ve updated the Intel Graphics HD 620 adapter using the manufacturer latest release. Again, no luck.
Test 1: Increase the startup delay to 60 seconds in Windows registry as suggested in the post (HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Serialize)
Result: inconsistent. The Xibo Player window will sometimes display in the wrong position - in the first initialization in the morning, or if I restart the notebook (either manually or sending a command from Xibo CMS)
Test 2: Disable the startup of the Xibo Client.exe in Windows Startup - and created a Scheduled Task: delay of 60 seconds, after any user logon.
Result: achieved a better result (approx. 9 out of 10), but the Xibo Window icon will be active in the Windows´ Task Bar until I actively click the mouse.
Test 3: Still running the scheduled task, I´ve setup an AutoIt macro to left click a random spot in the screen so the task bar will lose focus and hide itself.
Result: almost perfect, but sometimes the taskbar would be displayed (or the Xibo window was displayed in the wrong position). So I followed another tip from the forum: I moved the taskbar to the side, and set it not to be locked. This simple hack apparently made this issue with the taskbar disappear.
Test 4: Install Xibo Player version 300.5 from scratch
Result: none of the solutions worked. The window was displayed in the wrong position more than 70% of the notebook hot and cold starts. So I uninstalled, removed all the Xibo folders and entries in the registry, and reinstalled version 2.257.2
Test 5: re-enable the Xibo Player in the Window Startup and disable the scheduled task.
Result: so far, we have a good score - the windows position seems to be holding up well in the last 10 reboots, but we are not confident that this will sustain, according to our test 1 above.
In all tests, if the Xibo Player process is killed (or closed), and then the Watchdog relaunches it, the window will always be displayed fullscreen, as intended.
So far, the combination of these tweaks seems to be the best (but not definitive) solution so far:
- have a Player configuration in Xibo CMS to explicitly declare the resolution of the screen/windows
- use the registry modification to delay the startup to 60 seconds
- use a scheduled task to delay 1 minute the launch of Xibo Player.exe, after any user logged on
- move the taskbar to another position than bottom, and unlock it (but still having it to auto hide), so it will not be displayed with the Xibo Player icon active
Is there a way that we could confirm where, how and when the Xibo Player process will retrieve the information from the display driver / settings / registry while starting? Or could it be a Intel driver issue, more specifically related to the 620 model?
Thank you so far, @DanBW for your attention - but this is a big issue to our client, who is considering moving to another platform because of this issue - the end user is a big company, and is not ok with having the Xibo Player window closed when the offset occurs.
Best regards,
Norberto
