RaSystemlord's Posts

@BlackGator  For your convenience, I created a summary of the install process here: System where this is tested since 8-Oct-2021. Host: Kubuntu 20.04.2, i7 (2nd gen), no TPM, no VMware firmware changes. VMware Workstation Player version: 16.1.0 build-17198959 All the virtualization options checked in VM Settings. 6 GB RAM allocated. For more and for a disclaimer, refer to the site: "https://www.techpowerup.com/287584/windows-11-tpm-requirement-bypass-it-in-5-minutes" Use this at your own risk. If you are worried, according to Microsoft official announcement, that you loose the manufacturer warranty of your computer, which is so old that it won't fulfill all the Win 11 requirements, don't use these instructions. (sarcasm warning) 1. Download Windows 11 ISO from Microsoft Site (public). Tested with Win 11 Pro, English with ISO as published 5-OCT-2021. 2. Start install normally. When the error message of not fulfilling Win 11 requirements, comes, use Shift+F10 to get into the registry editor (regedit). 3. Edit the following keys: [HKEY_LOCAL_MACHINE\SYSTEM\Setup\LabConfig] "BypassTPMCheck"=dword:00000001 "BypassSecureBootCheck"=dword:00000001 "BypassRAMCheck"=dword:00000001 "BypassStorageCheck"=dword:00000001 "BypassCPUCheck"=dword:00000001 These are script contents. When doing this in an interactive manner, you need to do this manually. These mean a 32-bit dword with hexa value 1, as they are shown in registry. If you are installing on a physical computer, you can use these as a script and read the file from a USB stick. 4. Continue the install normally. In my experience, all Windows 11 Updates are also working after the install.  

@BlackGator  You are right, but I already answered this question in length, a week ago, in the thread mentioned below. The answer is based on actual testing last weekend. TPM Module in Workstation 16 (non-pro) To my surprise, nobody has even commented on this, I thought this was of interest? The thread gives a perfect way to install Windows 11 on any computer using Microsoft delivered official ISO file, published Oct-5-2021 ... which is exactly the preferred way for VMware install. Even Updates are working - which I have observed during this week. The contents of the link gives also other ways, perhaps preferred in some cases. Please comment this on that thread.

Very good! Could the original poster mark this as Solved (for record keeping and for easier browsing of the topics)? @aussiedan  EDIT: There is a topic category for that - not (just) text in the subject.

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. 

@v_enom  Obviously, we haven't found anything which would directly explain this. I'm trying to figure out reasons, which might indirectly influence this - something which is not configured optimally or something which could have a foreseeable bug in it ... and thus cause the failure that you are seeing. In your system and the way how you use memory and disks, I cannot anticipate any problems. There is perhaps one thing: how is your VM storage space allocated, also how it is allocated 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. Is your VM-computer on the level of 15.x? If there is nothing there - I would search for Windows 8.1 and RDP themselves for a fix.  EDIT: For the latter: Obviously Event Viewer needs to be checked, like if some service interrupted and started again. Also *temp* with its logs would be an important study.

@DrakeofAvlee  I don't know this particular router, but I wouldn't expect that a client needs to exist when port forwarding is configured. Anyhow, the router doesn't, in theory, need the client for making such a config ... which also sponsors the matter of having a fixed ip-address on the guest.

As an addition, similar thoughts as wila, which I forgot: - there is no need to fiddle with swap in normal Windows use. Do not take swap OUT and think that it fixes anything. I would return everything to defaults and see what happens. You need to do something about your disk, if that is why you have done this (see my post above) - I would also reserve only 2 cores out from 4 to a VM

Still cannot figure out why this is, but I can offer a few points: - what I meant with memory "monitoring" is that you observe all the things that you do, which consume lots of memory (I cannot know, if you have any of such), while it is not freezing - with 21 GB, I would assume that you cannot eat up all the memory with "extra software" running on host or with RDP However, I cannot understand how much you have reserved space for your VM and how much memory you have allocated to Guest? If you have a single 120 GB HDD and running a VM from that - this IS very bad, if the HDD is any older, which it probably is based on the size. Perhaps you mean SDD? If you have a single file allocation for VM, running on an old HDD (ide?), I'm expecting anything bad happening. An old HDD is much more slower than a bandwidth comparison to SDD would suggest. Even if you have a SDD of that size, I'm sure it is close to 90% consumption or even over that. That will deteriorate the disk fast (if it is from an older generation) and perhaps you feel the symptoms of that already? The solution is easy and rather affordable: a second disk, which holds all the data including your VM, or if you have a laptop, an external disk with USB-3 interface with SDD inside. The disk cover costs under 20 euros and the SDD-disk is a standard one (M.2 NVME disk is also possible, but covers are much more expensive, and you might not have any speed advantage, if your USB-3 level isn't very recent). If not clear, an external USB-3 is exponentially better than any old HDD ... if not obvious, you need to have USB-3 interface in your computer, USB-2 is very bad, too). However, none of those explain why it happens with the 2nd RDP usage. Running out of memory and a very slow disk, would explain everything. Running out of memory, would mean that you need to have a badly behaving application, which will allocate much more memory than it needs and which behavior you cannot foresee. You could use, on the Host, the Task Manager Details and graphics to find what happens during collapsing RDP and getting back there.

... and monitor how much memory RDP-session "rejoining" will consume. Is your Host memory allocation at the edge? You might not notice this when you first start your RDP-session, but when you "rejoin", you will notice it an interrupt, because nothing is supposed to happen. Running out of memory, will cause an interrupt AND hard disk operation at the max. You may need to monitor&calculate with several ways, because Task Manager does not always show the correct vmware memory consumption (there is detailed view and all that), however you always know what vmware takes, because you set it up yourself.

@wila  "try disabling 3D acceleration on the VM" Now, that's a good candidate for VMware-RDP-relationship problem. Thanks! Why the problem occurs on the second RDP session (or whatever that "second" really means, a question arised above) is still obscure ... but let's see what the answers and results are. EDIT: There was already an answer before ending this post. Yes, that is what collapse literally means. I just wanted to make sure.

I have no idea why those Bridged addresses are not showing up on the router, but ... ... if not obvious, you could use fixed addresses on your Guests and then they would not need to show up in *some* router menus. I assume you can still configure port forwarding on the router, even if its display doesn't show all the devices. I mean, they MUST be there behind the router, if Internet connections work. Perhaps, it would make better sense to use a fixed address anyway, when port forwarding is used?

OK, I understand that something indeed happens between two RDP sessions (or between what exactly?, read further). I wonder what your corporate PC is doing and why? You say that disk activity is 100%. That would definitely point to some security measures going on. A few questions: - how long is there between RDP sessions? Is it possible that PC would go to suspend in between? - what do you mean by "collapse RDP"? Does it involve interrupting RDP? - have you studied RDP bugs? This doesn't seem like anything VMware-specific ... although, I'm not an expert in anticipating RDP-VMware -relationship, if there is something specific in that

I'm no RDP specialist, but since you haven't got other replies ... I'm not sure what your workflow really is. There is obscurity in the Steps. However, I assume that you mean that Guest freezes ONLY sometimes when used from the Host when the connection to the Host is RDP. Can you explain what those circumstances are in RDP use, when it freezes. Since this isn't a problem when physically using the Host, this must be RDP related. We seem to be talking about a corporate PC as the virtualization platform. Is it possible that some implemented security is capable of analyzing the use of PC through RDP and deducting that SOME kind of use is suspicious? In principle, a wrongly implemented virus scanner will freeze the Guest use for a certain time, if VMware disk files are being analyzed. Now, in this case it seems that this too-eager-scanning-of-files, would need to be related to RDP use, only ... and perhaps in SOME kind of RDP use only - complicated deduction process is not that far-fetched nowadays. This virus scanner thingy is just one thing - don't know what security programs actually would do in this case.

Yes, it did work. All the way to installing VMware Tools and opening Edge Browser. Picture is attached. Host is Kubuntu 20.04.02 with latest Updates. Hardware is i7 (2nd gen, I think) with a decent Asus motherboard and decent nVidia graphics. VMware isn't the latest, but is: 16.1.0 build-17198959, bundle from VMware Site. In VM Settings for CPU, all 3 virtualization options are checked.

This reg-change does seem to work. At least, it got past the installation checks of Windows 11 install, in VMware on a Host that doesn't meet any of the Windows 11 requirements. On a Windows install, it is still many hours away for finding out if everything really works. The version that I'm using is Windows 11 Pro, English, downloaded Oct-5-2021 from Microsoft Site (public content). I couldn't immediately figure out, how to transfer those reg changes as a file and thus I manually edited the registry - on those steps instructed on the web page (it is 32-bit dword with hexa value 1 for all of the checks, as regedit shows them). If you have a good idea how to transfer the file, let us all know. However, use at your own risk. If you are afraid that you will lose manufacturer guarantee, that Microsoft officially says will happen, on your old computer that doesn't meet Microsoft limitations, don't use this method. (sarcasm warning)  

It is a big deal. I don't this has been solved on this Community Forum, yet. Obviously, the product itself has those fore-mentioned limitations, which are caused by artificial limitations in Windows 11. Microsoft is also saying that you lose your computer manufacturer guarantee, if you break those limitations - I will not open that Pandora's box here (because it is besides the point of this Forum). However, I assume that I have a technical solution for this in the end.  First: - I have tested quite a few ways to get Windows 11 into VMware without fulfilling any of the Microsoft limitations (like TPM, boot and processor)        - Beta releases worked without a problem, when installed from ISO with 3rd Party ISO-downloader/creator, a week ago or so. The very latest, I have not checked.        - Dev versions stopped worked a week or more ago        - Official Windows 11, English, does not work from ISO        - mind you, those were installs without fulfilling any of the Microsoft limitations for Windows 11 use - there have been a couple of scripts, which are said to help with that. I tested one (not published here), but it didn't work, not even for TPM and it was only for Win 11 Upgrade. A more realistic approach with VMware is to install from ISO. - on a physical computer, getting rid of TPM isn't really necessary. I mean, if you have a new enough processor, you probably have TPM as well. So, it doesn't make much sense to give a script for TPM only, on a physical computer.   Second: - it is commented elsewhere on this Forum, if you use encryption, you will achieve TPM as well, on a Player. This functionality is not enough for normal VMware use ... probably it wasn't anticipated by VMware that using TPM on a virtual computer makes no sense, if you are NOT planning to encrypt also. Finally: - on VMware, you may have many other things that you need to sort out, not just TPM. i7-processors are not magically powerful only in their 8th generation and later ... they have been powerful enough for decent use for 10 years or so. Workstation and laptop performance is NOT dependent on a processor alone, especially in normal VMware use. - here is a link to a place, which enables to turn many checks off AND it gives instructions for ISO install as well. This makes those instruction actually useful https://www.techpowerup.com/287584/windows-11-tpm-requirement-bypass-it-in-5-minutes This is a Community Post, not connected to VMware in any way. I have not tested this, yet. So, use it at your own risk and consideration. I'm sure, VMware will come up with official ways, as soon as they can.