Client installation fails with error: Temp folder full or inaccessible
Last Updated August 24, 2017
When installing the Symantec Endpoint Protection Enterprise Edition (SEP EE), Cloud (SEP C) or Small Business Edition (SEP SBE) client the installation fails with MSI error code 1632 (Temp folder either full or inaccessible) reported by install logs.
MSI error code 1632 will be recorded within various installation logs, depending on the specific product being installed. MSI error code 1632 translates to:
"The Temp folder is either full or inaccessible. Verify that the Temp folder exists and that you can write to it."
This exact error verbiage may be echoed within an install wizard dialog window, or another error message reporting "error 1632" may be displayed.
This error may be accurate, so it is recommended to confirm that standard temp locations are accessible and can be written to. However this error has also been observed in instances where no discernible issue with temp locations can be identified.
Manually creating the C:\Windows\Installer directory, then re-running the client installation, has proven to be a workable solution for cases such as this.
A Procmon recording taken during a failed installation attempt will assist with confirming whether adding the Installer folder would resolve the MSI 1632 error. Entries similar to the following can be observed in PML data recorded during an install that fails due to a missing C:\Windows\Installer folder:
SymantecLauncher.exe IRP_MJ_DIRECTORY_CONTROL C:\Windows\Installer NO SUCH FILE
msiexec.exe IRP_MJ_CREATE C:\Windows\Installer NAME NOT FOUND
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe