Closed andreadistefano closed 8 years ago
Have this issue as well, Windows 10 Enterprise 14342
I am using an open source library to handle virtual desktop. Unfortunately, the author has not been active on the GitHub repository for months. So I cannot fix the root issue.
The best I can do is add a setting to enable / disable virtual desktop support.
Do these insider builds eventually make it to consumers via windows updates? So in the new few months this issue will happen to users with a normal build of Windows 10, correct?
Yep, these builds are previews of the Anniversary Update, which should hit general availability in July 2016. Also, I think a setting would be great.
I opened an issue on the repository.
On the new build 14352 everything works fine.
Really? That's good.
On Friday, May 27, 2016, Andrea Di Stefano notifications@github.com wrote:
On the new build 14352 everything works fine.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ArcadeRenegade/SidebarDiagnostics/issues/93#issuecomment-222087639, or mute the thread https://github.com/notifications/unsubscribe/ANO20jnoS-bBUefAfD-SIa6s_cwHtq_sks5qFqg8gaJpZM4IaSHT .
Sadly, by build 14367 the issue reappears. Although if it's becoming intermittent, it might reflect bug issues at microsoft and not with the virtual desktop library. (I don't know since i mostly forget virtual desktops are there.) I guess unless the library developer shows, we'll have to wait and see what happens once the anniversary update drops.
Dang. Yeah I think this may have to wait for the final build to be released. If the error still occurs then I will try to fix the library myself. It's hard to fix without installing the insider build and debugging it myself.
I'll try to release an update to disable / enable the virtual desktop portion of Sidebar Diagnostics. It may take some time though because my SDD crashed and I lost my code signing certificate. I'll have to generate a new one and set up my development environment again.
Windows is releasing insider builds fairly frequently right now as they are in a bug bashing mode, apparently. Latest insider build (14371 for me right now) throws no errors, so I think we better wait until the next stable build is released, as it seems virtual desktop support is hit and miss between builds.
Incidentally, is the expected behavior for the sidebar to stay in only one virtual desktop, or show across all of them? Right now it shows in only my "main" desktop, which is what I like and expect, but I don't know if that's what's intended.
It should be moving to new active virtual desktop whenever you change them.
Ah. It's staying put. It's better than automatically crashing every time, and I personally like it that way, but if it's not the behavior you intended, it's still a bug.
It's working as intended in build 14376, released yesterday. To be honest I almost forgot about this issue, sorry about that. I'll try to update as new builds come out (they really stepped up their build flighting game these past weeks). EDIT: Still working in 14379.
I don't know if it helps but... Btw, win10 build 14379 and not working... :(
Not working in build 14383.
Probably broken record, Same issue
OS Version: Windows 10 Pro x64 Build 14372.rs1 Application Version: Sidebar 3.3.8 Reproduce: Just have Sidebar running when you open and siwtch to a virtual desktop.
Hopefully a solution can be found
Still not working in build 14388, also I think it probably won't work in the official Anniversary Update coming for everyone on August 2.
Incredibly working as intended in build 14393, which is a RTM candidate, so I'm hoping it also works in the Anniversary Update. Fingers crossed
Hopefully it does.
I added a new setting to disable virtual desktop support in v3.3.9 This can be a workaround until the issue is fixed.
In the new version, 3.4.2, I removed the virtual desktop library completely.
To allow the Sidebar to persist between different desktops, you can disable "Show in Alt + Tab" instead.
I found a bug. I don't think it's caused by me using Insider builds but I currently don't have another machine with vanilla Windows 10 to test it.
1. Your Operating System Windows 10 Pro Insider build
1433214342 (just updated)2. App Version 3.3.8 (Maybe you could add it to the settings window, it could be useful. If the taskbar icon is disabled there is no way to tell which version is being used)
3. Any Relevant Settings
4. Steps to Reproduce