yggdrasilos

WB 10.65 causing Task View to glitch out in Windows 10 v1803

▼

WB 10.65 causing Task View to glitch out in Windows 10 v1803

from Stardock Forums

I'm getting a strange issue with WB on the latest release of Windows 10 (v1803). Whenever I open the Task View, either by clicking the button on the taskbar or by pressing Win+Tab, the Task View behaves very erratically. It basically refuses to close, and renders my mouse unusable. Unloading Windowblinds doesn't seem to fix it, I have to fully uninstall WB to get Task View to behave correctly.

windowblinds
258,579 views 62 replies
Reply #51 from Stardock Forums Top

Thank you Neil for taking the time to post a reply! I can imagine that you are very busy. Anyway, enjoy your rest time, in case it is rest time for you also....

Reply #52 from Stardock Forums Top

Also I suppose Visual studio is not used that much either with most likely a workaround (exclude it). Nothing preventing releasing a beta fixing one issue with another one not fixed, beta's are not stable are they? Or maybe you should start an apha version program and people can choose if they want to use potentially broken versions if their pet bug has been fixed at least?

Also maybe try to find out why Firefox window gets larger every time a youtube video is fullscreened.

Offworld Trading Company
Reply #53 from Stardock Forums Top

Quoting Neil, reply 49

I do apologise for the delays with the WB update.

Unfortunately the issue was not spotted during the insider builds.

I was hoping we could simply put out an update with the fix, but it became apparent there were other things which needed addressing too, so the update has to wait for those too.

The good news is one of the remaining sticking points (an issue with VS 2017) has been addressed now and the update will come with a new feature as well.

As for timing, I hope the update can go into beta soon, obviously this week is a holiday so we will see if we have available QA time next week or the week afterwards.

For clarification, the issue is indeed with the very latest Windows update only and specifically to the fairly rarely used virtual desktops feature.

 

Thank you so much for getting back to us. As a consumer's perspective, the communication is highly appreciated. I am one of those who uses virtual desktops feature all the time. It's something I cannot live without ever since it was introduced on Windows10. The fact that WB10 has issues with the latest Windows update specifically to the feature I always use on my computer, makes me really upset because as much as I love WB10's aesthetics features, I will always choose functionality over aesthetics and the Virtual desktops has been a huge part of my workflow and without it functioning properly with WB10, I have no other choice but to not use your product. Which sucks because I truly love Stardock products (When they work).  I hope you guys enjoy your Holiday so that when you guys are back in business, you can work on a solution with a fresh mindset. I can't express how excited I am to use WB10 again... Good luck!

+1 Loading…
Reply #54 from Stardock Forums Top

After waiting for months, I finally decided to just go with installing the latest Windows 10. I think I can work around one little problem. First of all, hide task view button from taskbar so I don't just go click it and freeze explorer.

Saw someone suggested using the start+tab shortcut for the task view menu thing, tried that but that freezes as well. Simple solution if it's frozen is to restart explorer: "Start+R" > "taskkill /f /im explorer.exe" and then "Start+R > explorer.exe" and I didn't have to restart windows.

Workaround for using virtual desktops: Use shortcut keys Ctrl+Start+D for a new desktop, Ctrl+Start+Left/Right arrow keys to navigate between virtual desktops and Ctrl+Start+F4 for closing a virtual desktop.

However, I have no clue on how to work around and still use the task view / window history feature.

I don't really need it anyway so, all okay for now. Everything else is working fine.

Reply #55 from Stardock Forums Top

You just need to install the WB beta, it solves that issue.

I will find out when we are moving it to release as it should be shortly.

Reply #56 from Stardock Forums Top

The WB beta seems seems to resolve the latest Windows update problems. It's taken a while but it's worth the wait! 

Reply #57 from Stardock Forums Top

I have that problem to ever since the Win 10 1803 update but I don't have the "not closing issue" seems to do it only when transparencies/blurring effects are enabled. I just ignore it cuz its not causing any system issues for me

Reply #58 from WinCustomize Forums Top

i installed windowblinds 10.71 on my windows 10 laptop everything seems to work fine on it.... 10.71 is the beta i would think correct?

Reply #59 from WinCustomize Forums Top

Hello,

 For any of you having an issue with the latest WB 10.71 release we recommend to 

do a Purge uninstall https://forums.stardock.com/486023/windowblinds-support-faq#reinstalling

Reboot and reinstall WB10.65 https://cdn.stardock.us/support/uploads/WindowBlinds_10.65_setup_sd.exe

a correction is being made for WB10.71 and there will be another release/update for it soon.

If it's working fine for you then a update will be available soon.

Thank You for your Patience .

 


AzDude
Stardock Community Assistant

Reply #60 from Stardock Forums Top

Hi, I'm having this issue too on 10.65, it's a complete show stopper for me as I work with multiple displays and need the Task view to pin windows. How do I get access to the beta releases?

 

-- EDIT --

 

Found the beta thread and installed 10.70 beta, solves the issue for me. Great!

Reply #61 from Stardock Forums Top

Quoting nicosensei, reply 60

Hi, I'm having this issue too on 10.65, it's a complete show stopper for me as I work with multiple displays and need the Task view to pin windows. How do I get access to the beta releases?

 

-- EDIT --

 

Found the beta thread and installed 10.70 beta, solves the issue for me. Great!

 

Would you be able to point me in that direction? I bought an OD subscription about a week back, with WB being the main piece I'm interested in, and had to uninstall because of this particular bug. :(