FYI -- With V2.7, noticed that a pinned folder menu (for "quick launch" items) had changed in appearance, now showing as a black background/dark mode. The S11_ForceDarkMode registry setting (value 2) successfully reverted this pinned menu back to light background, as wanted. It would probably be better for the version upgrade to not have made this change, but happily it is configurable. Thank
larrycraw
Adding WebView2 did not seem to change situation. So I used Autoruns utility to disable the Stardock.Notification task, checking for impact of that configuration change.
Sean & Basj: The Stardock.Notifications.log file is shared at -- https://gofile.io/d/bViZD0 I'll look into WebView2 installation. It does not appear in the list of regularly installed apps or system components. Thanks.
Hello Stardock: Anyone encountered this Stardock error in the Windows Reliability Monitor? It seems to be related to the Stardock Notifications scheduled task. Occurs every few days, usually at the same clock time (indicates scheduled task start?). Win 11 Pro 25H2 Start 11 2.6. Apparently doesn't interfere with correct Stardock menu/taskbar operation, so not a critical i
Adam & Basj: Testing updates: (1) the symptom of icons jumping to top of desktop seems to have disappeared, after a newer non-WHQL version Intel video driver was installed, symptom can't be replicated now; (2) the issue with the non-persisting grouping of related windows seems to be related to the Windows (ie not Start11) Personalization setting for taskbar combining of buttons (behaves as expected when this is set to Always); (3) still not seeing the context menu option of
Hello Basj: Sorry, neither issue is resolved in the 2.55 version. - when after hovering, the row of icons/thumbnails appears, and one is close, the remaining icons no longer pop to the top of the desktop and then disappear, they simply disappear in place (above the taskbar). Instead, the row should close up and stay visible, to allow other selective window closures - when the pointer is above one out of a group of icons (app plus child doc windows), t
Another item for 2.53: when hovering over multiple related icons in the taskbar (app plus child windows), the right click context menu isn't showing a "Close all" option, as it did with previous Start10/11 versions. Can that useful context menu command be re-added?
Here is a gif to show the problem. An app plus its 4 document windows (= 5 icons w/ thumbnails) appears after hover in taskbar (correct behavior), the right hand item is closed, then incorrectly the remaining 4 icons don't remain in position above the bottom edge taskbar, they jump to desktop top, and then disappear in 2 seconds (maybe because of mouse movement?). I'll try to do v2.55 test ASAP. <img src="https://cdn.stardock.us/forums/48/73/4873698/29e8e809-ff
Good to have the v2.53 update, however it seems to have introduced an odd unwanted behavior. You have an app and half dozen of its child document windows showing in the taskbar. You hover over them, and larger icons w/ thumbnails for these appear above the taskbar. You want to use the Close control on several of the documents, and you click the Close X control on the first one. Instead of remaining visible, lined up in position immediately above the taskbar, an
Recently the Settings app on Win 10 1709 would crash when selecting System/About page. (Other Settings app pages work OK.) Upgraded to Start10 v1.60, the Settings app problem disappeared.
Windows 10 displays an initial lock screen at startup, before the login screen displays. This was unhelpful and unwanted by many desktop machine users. Until Win10 version 1607, a registry hack disabled this unwanted initial lock screen. Can Stardock add an option to Start10 to disable this unwanted initial lock screen? Thanks for Start8/10 -- very useful !
Followup clarification question about Banfield's post. It's understood that Start10 can't be installed under Windows 8.1. However, if a Start8 user wants to preserve their Start8 settings, is it possible to follow the sequence of first installing the MS Windows 10 upgrade, and then running the Start10 installer, which (1) picks up previous Start8 settings, (2) uninstalls the old Start8, and then (3) installs the new Start10 with the previous configuration settings pres