![]() ![]() This issue came back with Fusion Pro 11.5.5, running macos 10.15.5 on both the host and the guest, on a 2018 15" MBP. I note that the KB article that says how to fix this issue is no longer there (but Google cached it on July 11, 2020, so you can still find it if you google "vmware kb 52589" and select the cached version). Nothing like having an issue, searching for it because you have vague recollections about the issue, and finding this thread and seeing in it someone thanking yourself for helping them fix it! ![]() I've spend WAY more time typing up this response than I did simply applying the workaround. OK, yeah, you shouldn't have to do anything, but, gees. ![]() Unless they have a ton of people report the same problem, the first assumption is that it's localized to an individual user.įinally, I'm unclear why this isn't marked as resolved, since the Fusion 8 behavior is trivially restored with a single file creation and restarting the app. Yeah, companies often try to figure out if it's some configuration error or hardware thing. I think it's fair to said that "they" (who do you really think you're talking about here? The people who work for the company and are looking for a solution? Really? They don't care when they say they've found the issue and it will be released? Do you mean the release folks who are certainly running whatever release tests they run so that they don't release crappy code? Do you mean the marketing people who abhor the negativity that can snowball if they don't address issues? I'm just unclear who "they" are here) care.Īs for trying to identify the problem, when I read the thread, your second post three days later said VMware acknowledged this was a bug. Folks from VMware have been asking for information and looking into the problem for some time, and now there is at least a mitigation for this issue. 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. I raised this issue and started this over thread three months ago and this annoying issue has not yet been resolved. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |