Does it really matter if it runs on Win7/8.1? Surely nobody uses these OS for network connected production (even personal) machines?
A small update (copy/paste from convo), since there is a few members that hope to get v17 running on Windows 7. I can make patched msi install v17, same as with v16, i can finalize and install license. Caveat is that i first must preinstall vmx86 driver and they must be from v16. This is done by adding following 4 files to c:\Program Files\Common Files\VMware\Drivers\vmx86\Win8 vmx86.cat vmx86.inf vmx86.sys vmx86ver.dll This will not work later and replacing v16 vmx86 with v17 will simply bsod and i must delete vmx86 in safe mode to be able to start Windows again. Same as previous posted (in convo) that installation will bsod if i set VersionNT64>=602 -> VersionNT64>=601 (or any) In short: none of the vmx86 drivers from any v17 build is compatibel with Windows 7. I believe this is partial because of the encryption for Windows 11 guest OS that is new for v17 Spoiler I can play "ping-pong" with different versions of vmx86 and predict the end result but, yeah, vmx86 was not made with love for Windows 7. The complete patch with changes and files involved (originally) Spoiler * u32w80.dll - no modification to do, is a companion dll to vmware-vmx.exe, no clue where this one originates from. * vmware-vmx.exe - version/build spesific, located in C:\Program Files (x86)\VMware\VMware Workstation\x64 - patch strings, any hex editor is good: Code: Search string - unmodified vmware-vmx.exe v16.0 83 F8 01 0F 8E B8 00 00 Replacement string 83 F8 00 0F 8E B8 00 00 Search string - unmodified vmware-vmx.exe v16.2++ 83 F8 01 7E 6E 33 C9 E8 Replacement string 83 F8 00 7E 6E 33 C9 E8 (we are setting 1 byte from 0x01 to 0x00) Search string - unmodified vmware-vmx.exe 43 75 72 73 6F 72 57 00 55 53 45 52 33 32 Replacement string 43 75 72 73 6F 72 57 00 55 33 32 57 38 30 (we rename import function from USER32.dll -> U32W80.dll) "Original", later supplied modified file had an checksum fix in header but i don't see much use of it since the file signature is broken anyway when we patch. * VMwareWorkstation.msi - extracted from the installation file, Orca - InstEd - Pace Suite, all good msi editors: Code: Original patch with new changes: Module: Component _driver_vmx86_Win8 {A6B7BC20-0A7B-42AC-9554-7C4483F6133C} DRIVERS_VMX86_WIN8 320 VersionNT64>=602 _driver_vmx86_ver_Win8 Old value: VersionNT64>=602 Mod value: VersionNT64>=600 New value based on that v16 is not Windows Vista compatible: VersionNT64>=601 Special note - v17 must be unchanged - If not, system will bsod: VersionNT64>=602 Module: ControlCondition HostedVerifyReadyDlg DirectX11SupportText Show DirectX11_1_Supported = "False" Old value: Show Mod value: Hide (can be omitted) Module: LaunchCondition VersionNT64>601 [ProductDisplayName] is only supported on 64-bit Windows 7 or newer operating systems. Old value: VersionNT64>601 Mod value: VersionNT64>501 New value based on that v16 is not Windows Vista compatible: VersionNT64>=601 (this value is absolute minimum to start installation) There is a lot of guessing (from my side, would'nt be fun without) but i don't think the driver is easily modified. It's way over my head anyway but for special interested i added them anyway.
Can you simplify the prosess. How will we use this info? If you can share the patched msi file will be better. You can not replace patched vmware-vmx.exe inside msi file? As i understand. We should edit msi with orca. We will install from it. Hex edit vmware-vmx.exe. Replace driver files with that you shared. But which driver files? If i installed v17 under windows 7 should change driver files with VMware-workstation-full-17.5.2-23775571.7z or VMware-workstation-full-16.2.5-20904516.7z VMware-workstation-full-17.5.2-23775571.7z contains v16 driver files? Naming only tells us if you installed v17 use this? Or says patched v17 drivers but you said you can not patch v17 driver. Then why you share v17 driver.
@liliactr v17 will not work on Windows 7! Use v16. The rest is just collection of info for/if someone more clever than me can spot a solution.
Not installable (over an existing VMware)) "An error has occurred while applying security settings. Users is not a valid user or group." This could be a problem with the package or a problem connecting to a domain controller on the network. Check your network connecting and click retry or cancel to end install"
The 17.6 install needs to modify the Users and Authenticated Users groups during the install. It will fail on non-english Windows. The fix for the problem is relatively simple. All users need to do is access the command line or Windows Terminal, and type the following command: net localgroup /add "Authenticated Users" net localgroup /add "Users"
For windows 11 use bypass ... works fines or install 24h2 iot enterprise and after you can downgrade to pro sku after install by change product key
I had tested Windows 7 Pro all the way to Windows 11 Pro and LSTC as well on VMWARE 17 Pro (latest one..).. NO trouble.. Now they just released few numbers on 17 pro that now support Windows Server 2025!!!! ATGPUD2003