Do you have Ctrl + Win set to open the StartIsBack menu, or the native Windows 10 menu?

Ok, thanks! Could you attach a copy of your troubleshooting info? Here are the steps:

• Open the Settings > Troubleshooting tab
• Click the "Copy to Clipboard" button
• Paste the text into a text file (please don't paste the text directly into your reply, the formatting gets garbled and makes it difficult to parse)
• Reply with the file attached

Thanks! Everything in there looks like it should use the newer "direct" method of opening the Start menu versus falling back to the old "move" method. For the next beta, we're adding more logging info to try and track down the exact reason that it's falling back to the "move" method. I'll let you know as soon as it's available so that we can grab a new debug log from you.

Thanks!

We've just released 8.0 Beta 6. Could you give it a try and let me know if you still run into this issue?

Thanks!

Ok, we've done some more investigating on this, and it's due to the fact that we can't use our special "direct" method to invoke the Start menu directly on the DF taskbar when it's triggered through StartIsBack. It will only work correctly if you don't have a third-party Start menu app installed, and click the Start button with the mouse. Any other scenarios, we have to fall back to the old "poll and move" method because we can't hook the Windows 10 Start menu like we used to be able to do with the Windows 7 Start menu

Sorry!