I have already reverted to 11.0 using the solution mentioned by @RichardM4 -- will re-applying the 11.1 update trigger the problem again? I understand it's "fixable" using the process you link to, but I'd be much more confident knowing that this is a low-probability problem, or (much much better) that Parallels has actually fixed the issue altogether.Hi Nelson, you may try this article to fix the issue