@Dmitry@Parallels. As the original poster, I thank you for your response... finally. But before I say anything else you need to know I'm a very unhappy customer at this point. Let's do a recap...
Here's the thing. Sure, if you guys are having a hard time getting to the bottom of the issue, then fine. I'm a software developer. I get bugs, especially intermittent ones, are difficult to track down and fix. But Since Henmath's post in November last year, 6 months have gone past, with 17 more comments to this post, and only now does someone at Parallels pay any attention.
- I originally posted about this issue SEVEN MONTHS ago. I also called your phone support multiple times to report it and they kept directing me back here.
- As you can see from other replies it's not isolated to me.
- It does seem to be isolated to Mac guests (not Windows) and it seems those of us using Parallels for the purposes of using Mac guests are in the minority. Every time I've spoken to Parallels support they tell me to do something to Windows. I've figured out what they're really trying to say is to do something to the guest VM, but it's infuriating when I've repeatedly pointed out that it's a *****Mac***** OS X guest. It's hard to believe anyone's listening.
- For example. Hemnath@Parallels on Nov 25 (more than a month after I posted the issue - why so long??) told us to shut down Windows re-install Parallels, then try a couple of other things. That seemed to solve it for one commenter, but a lot of other commenters are still posting since then that that didn't solve it and the issue persists - myself included. But again... Windows?? No... it's a Mac guest!!!
- Now... 6 more months after that happened (including another detailed post from me in January) and finally someone from Parallels responds.
- According to this page: https://kb.parallels.com/en/124262, in the time since I posted this, Parallels has been publicly updated three times: 13.2.0-43213, 13.3.0-43321, 13.3.1-43365. I had reported the issue by phone at some point before the 13.1.1-43120 release, and then posted this forum message when I found that that release didn't fix it.
This bug isn't some little inconvenience. This bug makes Parallels Desktop for Mac 13 UNUSABLE. I haven't needed to virtualize a Mac in that time, and so I've been quietly hoping you'd fix it by the time I needed to again. But today I've needed it again, and it's still not fixed. It's a handy coincidence that someone from Parallels (you) finally responded a few days before I needed that, otherwise I'd be calling for a refund today instead of writing this.
Now, you've responded. You've asked two things:
Ok. The answer to your first question is yes. Suspending and resuming the VM releases the mouse click. The VM is usable again until the next time the issue occurs. In the last hour of using a Mac VM today, the issue has occurred four times. Ok... is that Unusable? Yes and no. I'm trying to use it as a FileMaker Server. If I have to suspend and resume the machine every 15 minutes, that means kicking off my users to do so. That's not an option. So in my case it's unusable. But even without it being a server, having to do that every 15 minutes or less... barely usable. And the competition (VMWare Fusion) has issues of its own (that are what made me switch to Parallels 8 months ago in the first place) but their issues don't make it unusable, so that's looking a lot more attractive at this point. Yes, Parallels has some features VMWare Fusion doesn't, that I'd really like to stick with, but if this issue doesn't get resolved soon, I'll be done and I'll make that call for a refund.
- Does suspending and resuming the VM release the mouse click?
- If not please send a technical report and post the ID here.
To your second question: given that suspending the VM and resuming it resolves the issue, it's hard to know if a technical report can help you, since you only said to send the technical report "If not...". Needless to say I did create one just now anyway, as the issue recurred, in case it might help. The ID is 258542314. The technical report behind that ID was made while the mouse is stuck in the VM and can't be released. I encountered the issue, made the report, suspended the VM, resumed the VM, and then the VM is working again. I then tried to create another technical report immediately, but on trying to submit it, Parallels Desktop crashed ("unexpectedly quit"). I reopened Parallels Desktop again and tried again. Same thing. I now can't send a technical report without it crashing. I suppose I'll have to reinstall the application again. If I have any success after that, I will post more information here.
I sincerely hope you guys can resolve this issue very very soon. Again, I can understand if the issue takes time to fix, but when you're not even communicating anything, meaning you're not even working on it, that's a deal breaker. For an issue that makes the application unusable, I'd think you'd pay a little more attention. If you'll reply to me soon I will work with you on this. If I don't hear anything back soon enough I will call for a refund.
[To others with the same issue, I'd recommend a similar strategy. Please give Dmytri what he's asked for and let's do everything we can at our end to help get this issue resolved. But if they don't respond promptly to that, then after all of us call for a refund, perhaps then they'll listen.]
Last edited: May 26, 2018