I’ve seen this error in numerous occasions now (in both virtual pc and virtual server) and even so many solutions on the web: ‘please wait while the installer finishes determining your disk space requirements’. The last time was when installing the Web Deployment tool (‘MSDeploy’) on a vitual machine:
It just sits and waits… nothing more.
Since i found a number of solutions on the web I decided to summarize them here.
Here they are:
- Run the installation with administrative privileges;
- Execute the msi via the command-line msiexec command: ‘msiexec /i <filename.msi>’;
- Move the msi to the root of a local drive and re-run the msi; Could be an issue with the path length;
- Temporarily uninstall virtual machine additions and reboot, before installing the msi; This did the trick for me when installing Operations Manager 2007 R2 but not in this case;
- If the msi was in a zip-file, and executed directly from the archive >> First extract the file from the zip-file and then execute it;
- If disks are dynamically expanding disks, convert the dynamic disks to fixed size disks (Thanks WaatzeG for the tip);
- Run the msi with a reduced UI: ‘msiexec /package <filename.MSI> /qr’; Since i wanted control over my installation this was not an option for me. I would only turn to this option as a last resort;
- Someone ran into this problem after installing XP SP3 and re-registered some dll’s; I don’t know about this one ’cause I haven’t tried so use at your own risk:
- Manually extract the file and then run the msi from the command line (option 2); <filename.exe> /extract <workingfolder>; The file I had was not an executable however;
regedit /s “Installer2Manual.reg”
RMDIR /S /Q %TEMP%
del /q %systemdrive%temp*.*
del /q %systemdrive%%windir%temp*.*
As said, 4 was not an option for me. I tried options 1, 2, 3 and 4 but they didn’t work either… individually. Eventually what did the trick for me was a combined solution of options 2 and 3. I moved the file to the root and then executed it via the command-line… Oh, and by the way. I used an elevated command prompt.
So if you run into this problem, try the above options and try to combine them, and should you have any other solutions to this problem please mail me.