This is getting extremely frustrating. More so the fact that this has not been prioritized as an issue requiring an immediate hotfix and it's been going on for months now. And yes, it does affect local transfers as well as we can see on our workstations with Megaraid RAID6 SSD arrays. Not only it has not been prioritized but it is also being downplayed in the KB notes as something affecting few users when it is affecting everyone as it looks like a kernel issue.
And no we can not use robocopy. Not everyone just "copies files". A lot of us use applications over the network.
We are a small software engineering company and we heavily use very large VMWare Workstation images served over the network. The performance is crawling and we are resorting to copying images locally in order to work. Our entire workflow is messed up and we're spending 4/5 of work time, swapping images around. And we can not revert workstations to previous builds either because we need the latest WDK.
Just because the majority of Windows users do not notice the underlying problem, it doesn't mean this should not have been fixed yesterday. Do we really have to contact every major tech news outlet site informing them of the situation so this gains publicity and traction before Microsoft prioritizes a hotfix?