Windows 10 Virtual Desktop Manager completely borked after Windows Update v17074 by WindowFX

Windows 10 major update to v17074 Insider Preview (a few hours of waiting - major Windows 10 insider update) just completed last night and now Virtual Desktop Manager is completely broken and unusable.  Literally nothing happens when you attempt to hit the Win+Tab hotkey except that sometimes you see the virtual screen and then no amount of clicking makes it go away.

I just spent a couple of hours trying to figure out what was going on, because I depend on Windows 10 Virtual Desktops.  Finally it occurred to me to attempt to disable WindowFX.  The moment I did so - instantly Windows Virtual Desktops were back to working 100%.  This was trivially reproducible - enable WindowFX, Windows Virtual Desktop becomes completely unusable; disable WindowFX, Windows Virtual Desktop works perfectly again - every single time.

I further tried to isolate it to a specific feature in WindowFX, by disabling one WindowFX feature at a time, but no matter what I did, Windows Virtual Desktop is still borked while WindowFX is enabled.

It's a bummer because WindowFX is a major part of my day - I love it and it makes me happy actually working all day long at the computer.  However, it is more important for my actual work that I have Windows Virtual Desktop working, so I have to disable WindowFX now.

I know that I'm running an Insider build of Windows 10 (version 17074), so maybe most people with the regular current Windows 10 don't have this problem.  I didn't have the problem before yesterday's Insider Build update.  Maybe it's a glitch in Windows 10 inside build that will be fixed by the time this insider version goes live to regular users later this year.  But perhaps this is a sign of a coming incompatibility...

I look forward to the glitch going away, because as of today, I cannot use WindowFX any more.  I'll keep checking back for updates and/or try again as updates to Windows get installed and I'll be happy when the problem goes away and I can re-enable WindowFX!  But in the meantime I wanted to let you know about this problem.  Maybe you even are aware of it and have a workaround.

Best,

Dan N