Reply to Message

What Wila writes is exactly true. My post in question was 2 months ago (!) . I haven't seen any development on this Player Forum.

When dealing with technical matters, there are several possibilities.

1.
VMware deals with them as professional support. I described above, how that could proceed in professional world. Usually, this is limited to official support, which, as Wila mentioned, is not freeware. With commercial software, the idea is that you pay for it.

However, I'm not linked to VMware in any way and thus I'm not writing on their behalf. They can explain there workflow here better if they wish. In 2 months they haven't.

2.
Using Community to solve a problem. Given the matter, it felt that this might not work. That's what I said 2 months ago - that was my prediction. Thus Item 1  workflow was explained. I have no idea, if VMware has acted upon this or not. As discussed, this is Community, not VMware company.

In non-professional software analysis, it is often confused what is the cure and what is the underlaying reason. For instance, a new display driver might be the solution. The underlaying reason might be a bug in graphics adapter hardware, which is corrected by the driver.

Having said that, there IS some new development that is possible to express here:

a) I have tested Windows 11 quite a lot in VMware. It does not get the Guest and Host stuck. However, my tests have not been stress tests. Perhaps somebody might want to test this? 

In comparison, in my system, Windows 10 Guest gets stuck very easily. When preparing ISO for Win 11, which involves long network activity and intensive packaging of the ISO, it almost surely gets stuck. There is no intense screen activity going on, only screen power saving (which is one far-fetched possibility). Other than that, I'm running Win 10 in a clean install with basically Microsoft defaults. 

b) VMware announced a new version 6.2 a couple of days ago.

Perhaps that gives a solution this problem? Anybody want to test that?

3. As it may not be obvious to everyone, why separating underlaying reason and the fix is important, a few reasons for this. This is a technical forum and thus a limited, negative-attitude end user perspective, needs to be discouraged. The matters in this item are not always relevant, but in this case, when the problem has been unanswered for months, this is probably rather important.

a) Sometimes, you can change the underlaying reasons and then the fix is not needed. Sometimes, you need to correct the matter as soon as possible and you don't want to wait for a fix. If you cannot change the underlaying reasons it's OK, but consider that as your own limitation in a case where changing them is technically easy and affordable.
b) If you create a fix, but do not understand the underlaying reason, the bug may reappear and you are no wiser about it. Thus in professional analyze, you always try to find the underlaying reason as well, not just provide a fix. This is of course something that VMware does, Community means for this are always limited.

c) MOST importantly, this IS a Forum, not your personal bug fixer. You can pay for that service, just sign-in for Maintenance contract. There are many people reading these posts. While, from your own limited perspective, you do not need anything else than a quick fix, there are always others, who can benefit from an answer which has a wider scope for the matter.