Start10 Menu buttom does not work on one monitor in multimon mode

from Stardock Forums

I have a fully updated Start10 running on Win10  v1803, Build 17134.829

 

I have a Surface 2 Laptop which I use stand alone and with 2 different USB3 docking stations (work and home) that have 2 additional monitors.  At work when I'm docked I have 2 HD monitors attached and I use one of my USB3 HD monitors as the main display.  When I am in this configuration the Start10 menu button on the taskbar shows up on all 3 screens but on the Surface2 display it does not work.  I click on it repeatedly and no Start10 menu.  The other 2 displays from the dock have functional Start10 menu buttons includign the one display that is the main display.  When the computer is in this state the Surface2 Start10 key remains inactive even when I undock and I cannot use the laptop and have to reboot it.

When I reboot it stand alone it works fine.

At home I have a different USB3 dock and a different alignment of 2 HD displays.  In this configuration the same PC has no issue with the Start10 button on the Surface 2 but one possibly important difference is in this second docked configuration the Surface2 display is ALWAYS the Main display in the multimon unlike my work USB Dock multimon where the Surface2 display is NOT the main monitor.

Another interesting detail on the work moltimon that results in an inactive start10 key is that if I boot this config with the Surface 2 configured as the main display on my work docked setup it never seems to happen even if I change the main monitor away from the Surface2 after it has booted.  If I DO boot in the Work USB3 Dock scneario with the surface NOT the mainmonitor the Start10 button NEVER works on the Surface 2 display.

 

start10
10,203 views 15 replies
Reply #1 from Stardock Forums Top

Hello,

I have forwarded your problem to Stardock Support team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

 

Basj

Stardock Community Assistant.

Reply #2 from Stardock Forums Top

I have verified the repro steps last night.  Connected to the multimon home dock has no issues with the Surface2 Win Menu button, but the work multimon dock does (which is where I am now).

Sins of a Solar Empire II
Reply #3 from Stardock Forums Top

Hello,
I have forward your problem again to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Reply #4 from Stardock Forums Top

OK so I have received NO replies in 2 weeks from the support team.  I have about 10 licenses of this product on various PCs for my family.  This is a clear bug with a clear repro that I shared.  This bug requires a reboot of the laptop after undock to even use the laptop.  As someone who has done commercial SW for 20yrs this is a P0 bug, MAYBE a P1.  Either way no support feedback at all is unacceptable.  This bug reders my PC unusable.

 

A simple "we're working on this" is the minimum I'd expect.  Silence is not acceptable.

Reply #5 from Stardock Forums Top

Hello,
I have forwarded your questions/problems, again, to the Stardock Support team for their assistance. Please keep an eye on this thread for any updates. We appreciate you feedback and patience.

Thank You,
Basj
Stardock Community Assistant.

Reply #6 from Stardock Forums Top

billvert,

Sorry to hear you are having trouble.

Quoting billvert, reply 4

A simple "we're working on this" is the minimum I'd expect.  Silence is not acceptable.
End of billvert's quote

We would, of course, strive to help but we can not readily reproduce your rather unique, and elaborate, set up. There are also many software an hardware unknowns. 

Quoting billvert, reply 4

I have about 10 licenses of this product on various PCs for my family. 
End of billvert's quote

I suspect they do not all have this same set up nor do they see any similar problems with their more common setups, yes?

Another interesting detail on the work moltimon that results in an inactive start10 key is that if I boot this config with the Surface 2 configured as the main display on my work docked setup it never seems to happen even if I change the main monitor away from the Surface2 after it has booted.
End of quote

If a restart of Windows Explorer does not resolve the issue in your preferred config (should be attempted if it has not been), is this an acceptable workaround for the time being?  Also, a 'boot' may not be required; instead, a much quicker log off / on may be enough.

A clean boot, to see if there are any other software conflicts should also be attempted if all fails:

https://forums.stardock.com/486022/start10-support-faq#cleanboot

Sean Drohan
Stardock Support Manager

 

Reply #7 from Stardock Forums Top

I have to reboot Windows, not "Windows Explorer".  I can share images of how my screens are configured to make it easier to reproduce.  I also have a different laptop I only use at home.  I can try to set up the monitor layout on it to mimic the configuration I have on my work laptop and see if it is truly the monitor config causing Start10 issues or if it is some weird policy on the work laptop.  I am in London at the moment but I should be able to do this by this Sunday.

I mentioned the number of copies I have of Start10 not to address this bug but to indicate I'm a fan and a great customer.  I worked at Microsoft for 20yrs and I know how hard software bugs can be.

Reply #8 from Stardock Forums Top

Quoting billvert, reply 7

I have to reboot Windows, not "Windows Explorer".
End of billvert's quote

I understand what you said you were doing to make it work - I am curious if my suggestion would also work.

Quoting billvert, reply 7

I can share images of how my screens are configured to make it easier to reproduce.
End of billvert's quote

Its not the logistics - its actually being able to physically reproduce the environment (hardware, software, set up) physically to test.  My suggestion for the clean boot would help eliminate any software, setting, Win profile issues.

Quoting billvert, reply 7

I also have a different laptop I only use at home.  I can try to set up the monitor layout on it to mimic the configuration I have on my work laptop and see if it is truly the monitor config causing Start10 issues or if it is some weird policy on the work laptop.
End of billvert's quote

Such a test could prove helpful.

Sean Drohan
Stardock Support Manager

 

Reply #9 from Stardock Forums Top

So I'm not familiar with Windows Explorer.  Is this the shell for Windows?  How does one restart it?

I can send a screen scrape that captures the config of my docked monitors if that would help?

Reply #10 from Stardock Forums Top

Quoting billvert, reply 9

How does one restart it?
End of billvert's quote

Sean Drohan
Stardock Support Manager

Reply #11 from Stardock Forums Top

So I undocked the laptop, Start10 button on the laptop was not functional (as I originally reported) and I restarted Windows Explorer as you asked and...Start10 button started working.  I redocked and it continued working AND I undocked it again and the Start10 button still worked.  So once I restart Windows Explorer it appears to fix it for all subsequent dock/undocks.

Is this something you guys can fix?

Reply #12 from Stardock Forums Top

Quoting billvert, reply 11

So once I restart Windows Explorer it appears to fix it for all subsequent dock/undocks.

Is this something you guys can fix?
End of billvert's quote

Again, recreating your environment for any test would be difficult.  If restarting WinExp works for you, I have written a batch file you can run when you need to so that it is quicker:

https://cdn.stardock.us/support/uploads/WinExeRestart.zip

Sean Drohan
Stardock Support Manager

Reply #13 from Stardock Forums Top

The batch file was effective.  If you ever have a product update related to this issue, email me, I'm happy to test.

Thanks

Reply #14 from Stardock Forums Top

another data point on the batch file that might help track this down, after I used the batchfile on my first undock (and he Start10 hey was inactive as expected) the next time I docked and then undocked I did not need the batch file, it worked fine.  Apparently there is something different from when Windows Explorer initially starts and when the batch file restarts it because that second start of Windows Explorer does not have the broken undocking behavior that the initial boot with Windows Explorer has.

Thanks again!