When I click Start Button on second monitor the menu pops up on primary, and other issues

WARNING: You currently have Javascript disabled!
This website will not function correctly without Javascript enabled.

Kirk Rexin

3 discussion posts

When I click Start Button on second monitor the menu pops up on primary. I'm using an Ultrabook with this Targus USB3 port replicator attached to two monitors. It uses DisplayLink to manage connectivity. When I first installed the application everything worked well. I think the problems started either when I restarted the PC or undocked and docked the PC.

Additionally, the systray on the second monitor does not work anymore. These two screen shots show my primary and secondary monitor systray icons.

• Attachment [protected]: Primary monitor systray.png [5,855 bytes]

• Attachment [protected]: Secondary monitor systray.png [10,268 bytes]

May 22, 2013 (modified May 22, 2013) • #1

It sounds like the global hooks might not be loading when DisplayFusion starts up. Could you do the following to help troubleshoot?

Enable debug logging on the Troubleshooting tab (set it to Logging: Important Only) and click Apply
Restart DisplayFusion
Confirm that the issues are still there
Attach the %appdata%\DisplayFusion\DisplayFusion.log file to this topic (can be found by clicking the 'Open Log' button on the Troubleshooting tab)
Disable debug logging after sending me the log

Thanks!

May 24, 2013 • #2

Kirk Rexin

3 discussion posts

The problem persisted. Here you go.

• Attachment [protected]: DisplayFusion.zip [37,873 bytes]

May 24, 2013 • #3

Thanks! It looks like for some reason, the DisplayFusion process is running as 32-bit, even though your system is 64-bit. Could you check the Properties > Compatibility tab for both the DisplayFusion shortcut, as well as the DisplayFusion.exe itself in C:\Program Files (x86)\DisplayFusion to see if there are any settings enabled there?

May 27, 2013 • #4

We've actually had another customer run into this issue, and we were able to get it sorted out. Are you comfortable with working in the Windows registry? If so, can you check the following registry value to see if it's set to 0 or 1?

HKEY_LOCAL_MACHINE\Software\Microsoft\.NETFramework\Enable_64Bit

If it's set to 0, just change it 1, restart your machine, and these issues should be all fixed up