Message boards : Questions and problems : Windows 10 Taskbar and Boinc
Message board moderation
Author | Message |
---|---|
Send message Joined: 11 Sep 15 Posts: 5 ![]() |
I have a weird issue on multiple computers (multiple versions of Boinc) and wanted to get your opinions. I run SETI@Home exclusively. When Boinc is running, right clicking on an icon on the taskbar doesn't work. Doing so with icons in the notification area works, just not on the taskbar. If I snooze Boinc, all of the icons I right clicked start displaying the right click menu immediately. Not a huge deal because now I know if I want to get to the right click menu I have to pause Boinc first, but it is kind of a pain. Any thoughts? |
Send message Joined: 6 Jul 10 Posts: 585 ![]() |
Can't reproduce [After 1.5 months of battling with this pitiful Linux ripping OS], it's now working as it's expected to work on a 1.6GHZ 4 core BOINC crunching, at 100%, 10 year old ancient... MS even adopted the 3 bars Google/Android menu indicator, hahaha. N.B. The search-indexing function in W10 is very very pivotal. Everything gets indexed into some DB. If that's not complete, behavior becomes slow and erratic in W10, to the point of crashing such as 'Start Menu and Cortana aren’t working’ Critical Error'. Much seems to have been fixed with the September updates though. Coelum Non Animum Mutant, Qui Trans Mare Currunt |
Send message Joined: 9 Nov 10 Posts: 63 ![]() |
To my knowledge, this is a Windows 10 bug, where Microsoft is not properly handling shell interactions with correct process/thread priority, while the cpu is fully saturated. It is especially noticeable when clicking the "Show notifications" system tray icon, doesn't open the Notifications window. And then, if it's in that stuck state, right-clicking a taskbar icon won't work. My testing with the Windows 10 Insider builds, indicates that this may already be fixed for Windows Insiders. This "Threshold 2" TH2 build of Windows 10, is expected to be publicly released to normal users sometime in October/November, and I suspect you will pick up the fix then. As a workaround, you can change the BOINC setting "Use at most x% CPUs" to a value that is not 100%, either permanently, or temporarily while you interact with the Windows 10 shell. I would also encourage you to use the Windows Feedback tool, in Windows 10, to upvote/submit any suggestions/problems that you find with Windows 10. They are listening, and the tool sends them valuable feedback/telemetry. Kind regards, Jacob Klein |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.