OK, but this is not exactly what I meant with my questions (yet, again, I'm looking for indirect influencers):

---

1.

>llocated in regard to overall 120 GB space? The normal way would be something like: max 90 GB with all the virtual disks (could be two inside the VM) and in slices, not one file.

It is a one C:\ drive with 100 GB, 80-90 GB are in use.

/Ra - the important thing is the overall disk consumption on your physical drive. If you have 100 GB within the VM, you may have over-committing 120 GB on the physical drive. You should look what the size of the VM folder is, when VM is running.

Is it a pre-allocated single file (very bad if there is over-commitment). Also, in this case, your overall disk consumption would be very close to 120 GB on the physical drive - which is no good, for the fore-mentioned reasons.

Yet, not sure, how RDP is linked to this, but this is something to look after in every case (if there is a problem).
/

---

2.

>Is your VM-computer on the level of 15.x?

my version is 15.5.6 build-16341506

/Ra - No. I mean the VM version. Version 15 software can run very old VM-versions. I don't think it is a problem if the version is not very old. I think 21 GB has been supported for quite some time. /

3.

Now, for a test - if you haven't already done this.

Use RDP in the office to connect to your Host and see what happens. Not everything that is going on, might be transmitted with the RDP view to your home office.

Your guess is as good as mine, but I suspect Windows 8.1 - RDP -bug for the source of this problem. It just appears with VMware, because VMware requires more functionality to be working. If you have more hardware available, you could run the VM on a different platform with RDP at work - like on a Windows 10 computer ... and see what happens. You said that you have low security and thus this would be reasonably easy, even if this isn't a corporate standard.