This problem has been present in Windows native multi-desktop implementation since day one. When one application spawns another application, the new window for the new application pops up on the current desktop instead of appearing on the original spawning desktop. For example, when Visual Studio on desktop 1 finishes compilation and launches a console program, the new console window pops up on the current desktop 2, instead of staying on desktop 1.

I was hoping that eventually Windows developers will find a solution for this problem, but alas it is still there and because of it Windows built-in multi-desktop functionality remains a beta-level demo, not something actually usable.

So, is there some inherent problem with Windows architecture that prevents it from better isolating the desktops from one another? Or maybe there is there a tweak or workaround they would fix this annoying behavior? A third-party solution maybe?