You're correct. I meant to say that this is where customupdateengine.exe and the included files usually gets unpacked to this location on my systems, though this is anecdotal, and not authoritative.
Interestingly enough, I don't have this issue with the MSP files, though, I just came up with a better idea altogether:
In your updater, you can move the files out of the unpacked directory to a directory that you define, so move files from .*.msp to PATH_TO_INSTALL_FOLDER, then install the MSP files from there, then delete them or move them back into the current working directory and delete the folder if it's empty afterwards.
Another thing that you could do is use a VBScript to copy the installer to a known working directory and call msiexec from there, then clean up the working directory afterwards, or just use VBScript to get the full current path, and use that to call MSIExec.
Interestingly enough, I don't have this issue with the MSP files, though, I just came up with a better idea altogether:
In your updater, you can move the files out of the unpacked directory to a directory that you define, so move files from .*.msp to PATH_TO_INSTALL_FOLDER, then install the MSP files from there, then delete them or move them back into the current working directory and delete the folder if it's empty afterwards.
Another thing that you could do is use a VBScript to copy the installer to a known working directory and call msiexec from there, then clean up the working directory afterwards, or just use VBScript to get the full current path, and use that to call MSIExec.
