Hi there,
Okay, so here is an example of how it often goes, and did go in this case.
The issue is raised as a bug at some point after the being raised on the forum, (responded to by someone or not) this can be immediately or even or after a few days or a week.
In this case, the bug was raised a few days and then completely misfiled and ended in some other unrelated groups queue.
That group's queue then got mistakenly, again, not triaged (or skipped over) for quite sometime, spending most of the two months since it was raised at that queue.
A developer triaging that queue eventually realized the error and it got redirected to the correct group, i.e., me, and I responded here.
Now, that is not the normal sequence events but that is what occurred in this case.
It was never intentionally set to any "low" priority of any sort.
At that point I scheduled it into my existing workload and outstanding issues to be fixed. Including some urgent high priority issues.
I have got help from Dominic's application that he attached and reproduced the issue and then investigated the issue. Along with another report that sounded like the same issue but a different way of manifesting itself.
However, also what can typically happen on these forums is that bugs do get filed but no-one responds to the posts from the VMware developer side.
So no mention of any bug filed or even fixes are relayed back to the forum users.
So please just be aware, that even if you don't get replies here, it doesn't guarantee that the issue is not being addressed or even looked at or given a low priority.
I know that is not ideal, but that it does happen. I have even replied to issues raised on behalf of other developers, and I know other developers have chimed in on issues to do with VMware Shared Folders.
What I will say, is that if you do have VMware developers responding to the thread, and have concerns about priorities and urgency and workarounds that may help, then please just ask first. You will probably get more details back which can often help clarify things for you.
There is an awful lot of points that need to be taken into account when we schedule work and bug fixes. (I cannot enumerate them all here.)
I also will let you know, that often developers own expectations of what is deemed the highest priority is sometimes not the case for VMware developer's own recommendation aside). Often in worse cases, these not articulated back to the user either. That being said, I often try and do mention when this is the case to users and why.
Here corruption bugs are high priority, and rare, as you might expect or indeed hope. In a case where it only occurs in an OS used by very few users, then it may pushed out a little (not totally ignored) if there are equally bad issues in OS platforms used by a very high percentage of users.
You are all free to make all the assumptions you want, but if someone is responding ask first, so you don't have to assume anything. If there are no comments from VMware people, then that is are fault if you make assumptions and they are wrong.
I hope this helps at least this case, and I hope when other issues are reported too.
Please always report your issues and please give as much information as you can about reproducing it. It is often very hard to replicate issues that can rely on some specific environment which is usually not at all obvious. 
I also appreciate that you are placing so much importance on the VMware Shared Folder issue, as it indicates to me at least, that you do intend to make it a central part of your set up and usage. (Or I could be making the wrong assumptions there..)
Thanks.
Steve
PS I make no assumptions or distinctions on what the individual users case is in terms licenses or paying fees, but I do go on how many of our general customers from our usage data are likely to be affected by these issues, and the nature of the issue and whether it can avoided by a sensible workaround or not (along with many other issues our Program Manager raises too).