In other words, don`t get your hopes high, we don`t care too much about this piece of software and is not anyware near the top of our priorities. I have the same problem, related to the Window Blinds and new Windows 10 update. Don`t plan to update any subscription unless I see clear signs that the developers still care about this product.

We are working on an update for a number of issues.  The issue with the taskview will be resolved in this update.

I was hoping we could get it out last week, but other things came up which made that not possible.

Getting an update out is a priority for us and it should not be long at all, gang - thanks for your patience and understanding. 

Regards,
Sean Drohan
Stardock Support

Apply this settings on windows. Fix 50% of the issue. Just try it. 

So... How things are going with the update? Any news?

A month ago the needed update was to arrive "later this week or next". Don't promise what you can't deliver. The recommendation is "under promise and over deliver".

So I just upgraded to Win 1803 and the task view was broken.  I uninstalled WindowBlinds, ShadowFX and WindowsFX and all is good now.  When I get a chance I'll try to determine which was the offending program.

Edit:

Just read the entire thread here and realized a fix is in the works, I guess I'll just wait

When will the issue you had last week a month ago be fixed?

I know I said I was happy to wait so the problem was resolved right, however I have just noticed the "Summer Holiday" announcement posted today:

"by Island Dog

Jun 30, 2018 10:02

Stardock will be closed for the week starting on Monday, July 2nd and we will be returning on Monday, July 9th. We will be monitoring support tickets and forums during this time, but expect delays in responses during this time."

 Don`t wait for a alternative suggestion on this forum. I`ve posted a link to an alternative for the windows 10 native virtual desktop ( this is at the moment the only viable workaround if you want to use windowblinds in windows 10) and the moderators deleted my post, although I was not suggesting, as you ask, an alternative software that was competing against their products. I was actually trying to help their existing customers to hang on to this software, until they will manage to find a way to make windowblinds work in windows 10.

 The only thing that I can say ( I hope they will allow this, at least) is there are workable alternatives to windowsblinds, just google it.

 Anyway, Neil Banfield, the man behind windowblinds, has put a lot of effort into this software over the years. I still hope that he did not gave up. If he did not gave up, a workable version of windowsblinds will come and I can tell you that that will be better than the existing options from other developers. After all, this software has many years of experience in it and in the past, at least, there was a large team involved into development. It is not easy for a new piece of software (especially one of this complexity) to compete with that.

Since I'm pretty much going to disappear into the woodwork now, I would like to leave a more detailed account as to why.

My feedback on this issue is that:

 - The developers should (I assume) have had access to 'Windows Insider Program'. Which means that should have been aware of this issue from about mid to late March.

 - There seems to be some confusion/doubt as to whether the 1803 update is the exclusive cause of the problem. Since uninstalling Windowblinds; I can say that everything works as it should. (For me anyway).

 - The developers seem to want to bundle the solution with their next release. (Can understand that to a degree, but months...)

 - There is (at least in this case) poor communication with regards to when that will be and assurances about the release being 'soon' are clearly premature and so are not at all helpful or reassuring.

 - The time it has taken so far has run into a staff holiday break. I do understand that this is just unfortunate timing;. however since that leaves me waiting for even longer for a solution; I can not help but feel somewhat irritated.

So after waiting over 2 months with no solution, and no indication that the long wait is ending anytime soon; I have abandoned Windowblinds and looked for an alternative. It took me less than 2 hours to find one, select the skin I wanted and customize it the way I like.

It is great having things back to normal after all this time, especially with the added bonus of the new 'task view/timeline' feature.

Finally I should say that:

Windowblinds is a good versatile program, I and will miss the ability to easily add textures which I feel adds and 'organic' look to Win 10. IconPackager is still a very useful and reliable program for me and so will continue to use it.

I will also miss the theme; 'Dark Mode' by Vad_M. Which while not perfect; is the most aesthetically pleasing and professional looking dark theme I could find that worked with Windowblinds.

All the best.

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.