![]() ![]() ![]() But I think it's a little unfair to paint VMware with the paintbrush of "they don't care". I get the frustration with people who have this problem (I suffered from it for several months). I found I just had to log out, not reboot, to resolve the issue.īut I followed the steps in the KB article and it resolved my issue (and is actually the behavior I prefer, anyway). So, I was having this issue with Fusion Pro 10.1.1 with host os 10.13.3 and guest os 10.13.3 (yeah, I run a Mac VM on a Mac. This is not acceptable vmware you obviously don't care about your customers. I am always amused when companies want our feedback when they've done something right but ignore our feedback when they've done something wrong. Whilst I commend their support team for trying to resolve the issue there is no doubt that it is an issue wth Fusion and not a configuration issue on the users end and there is no doubt that the issue arose from version 8 to version 10. For the most part they approached this issue as if something was wrong on my end and so we spent hours trying to find that (swap multiple keyboards, reset pram, support request to Apple, re-install, remove other software and on and on).Īs consumers it is in our best interest to support companies that listen to us and take our needs and problems as priority. I have also spent about 6 hours of my time trying to resolve this issue with vmware support. Continually having to click caps lock every few seconds makes this product unusable for me. Under Australian consumer law companies must give a full refund for faulty products and similar laws are present in other countries. ![]() Obviously this is not a priority for vmware and so the best option is to ask for a full refund (as I did, and received) and move to another option. Please understand that this opinion is not a form of racism or supremacy, it just reflects our society's total lack of education in problem solving and that it's not going to improve anytime soon because complexity and information are growing exponentially.I raised this issue and started this over thread three months ago and this annoying issue has not yet been resolved. When they come to a dead end, they flood the support forums with noise, asking vague questions and end up either blaming the product or bitching at the helpful people who struggle to understand their mess. These people can't even understand what a System Restore or a Snapshot is for. I am fully behind software companies' decision to not document every option and every switch, because there is always a class of users who still think that asking questions is a sign of weakness and proceed to experiment with settings, without keeping a proper log of what they're doing, eventually rendering their system non-repairable. The existence of search engines made things much, much worse because by their nature they promote minimal effort solutions. The solutions are just hard to find, because of too much noise, too much overlap and principally because we have not been taught in schools how to search for relevant information in this Information Age. The Communities are a treasure trove of information because all methods of solving a problem that work for more than one person are documented here, and ideally they should be listed separately in the Documents section ( Workstation Pro ). It is impossible to have a complete, exhaustive documentation for every aspect of a program having a history of decades behind its development (applies to OSs too). ![]() To add to wila's point of view, my personal view is that a forum (this Community) is a chapter of Documentation, namely its Troubleshooting section, and this is one of the two main reasons it exists - the other being providing peer support. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |