That ISO is still part of Fusion 13, and contains VMware Tools 10.0.12 - the last tools version supported for Windows XP. The file /Applications/VMware\ Fusion/Contents/Library/isoimages/x86_64/winPreVIsta.iso should be mounted by Fusion when a Tools installation requests is made for a Windows XP guest. That's why you're getting the "program is not a valid win32 application" message. The tools in that file are version 12.1.5, and they don't support Windows XP. It is mounting the ISO file /Applications/VMware\ Fusion/Contents/Library/isoimages/x86_64/windows.iso. Looking at both the ISOs mounted in the guest and the contents of the vmware.log file, Fusion 13 is mounting the wrong VMware Tools ISO file for a Windows XP guest when you request an install of VMware Tools. I got the same issue as you when trying to install VMware Tools from the GUI menu. I just installed XP Pro in Fusion 13 on an Intel Mac mini 2014 with the defaults for virtual hardware version. It's sort of the former (new version of Tools), but not really. > So the culprit(s) is/are a new version of Tools and/or new vm hardware version. I just noticed it was SP2 after installing another VM from the WinXP DVD in Fusion 12, which has no trouble with WinXP SP2. This issue really dinged my revenue today.ĮDIT: maybe Fusion 13's VMWare Tools requires WinXP SP3. I can't charge my clients for all the time I spent upgrading, testing then downgrading. If Fusion 13's VMWare Tools wasn't intended to work WinXP and the developers don't care, please let us know so we can avoid the hassle of flailing, failing then downgrading. Several other customers use Fusion 13 with Win10 or Win11 to run Windows accounting software and VMWare Tools updates easily. I still have about 4 customers using XP to run very old, very obscure specialized excellent but abandoned software for their industries. I'm not sure, but it seems Fusion 13 programmers and QA testers didn't try v13 VMWare Tools with Windows XP. So I downgraded VMWare Fusion 13 to v12 and VMWare Tools installed fine in WinXP. NET 4 or earlier from a MS download - AND I don't even know if. NET 4 or earlier, setup.exe would work, but without internet access with very old IE within the VM and without drag and drop file sharing from the Mac and without sharing enabled (because Tools wasn't installed), I don't see how I can install. So I created a new virtual machine from a Windows XP DVD - a total clean install - and the same thing happened: vmware tools wouldn't install even from d:\setup.exe (and the same error appeared "setup.exe isn't a valid Win32 app."). I have lots of experience over the last 10 or so years with customers' old messed up VMWare Tools updates and tried all my tricks, like deleting all registry keys with "vmware tools" matching whole phrase, but none helped. So for some reason the VMWare tools installer is sensitive to the location of the temporary files folder specified by the User TEMP environment variable.I and several of my customers run VMWare Fusion 12 and 13 on Intel-based Macs.įusion 13.0.1 has been fine for Windows 10 and 11, but tonight I upgraded a customer's (macOS Monterey) Fusion 12 to Fusion 13 and VMWare Tools failed to install, including from d:\setup.exe (error appeared that setup.exe isn't a valid win32 program). I guessed that this might be the cause of problems, so I changed the value of the TEMP environment variable to C:\TMP The log file contained the line: Property(S): TempFolder = C:\cygwin64\home\guylar01\tmp\ T14:51:58.783+01:00| inst-build-9925305| W1: Setting temp directory root failed.Īll of this reminded me that I had set the TEMP environment variable for the User to the non-standard value of C:\cygwin64\home\guylar01\tmp\ I thought the double backslash in the path name after tmp looked syntactically incorrect. T14:51:06.601+01:00| BootStrapper-build-9925305| I2: Util_FileExists: Did not find file/directory: "C:\cygwin64\home\guylar01\tmp\\vmreboot.tmp"| posix code 2 (No such file or directory) I then attempted to install again, which failed, and I inspected the logs. I turned on Windows Installer logging by following the instructions here: Thank you for the suggestion agalliasistju
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |