ProfileUnity Client 6.9.5 HF1 Upgrade Silently Blocked by Residual Config File

When upgrading the ProfileUnity Client from 6.9.5 GA to 6.9.5 HF1 using the setup EXE (ProfileUnityClient.Setup_6.9.5hf1.exe) or MSI (ProfileUnityClient.Setup_6.9.5hf1.msi), the installer may report success while the client is not actually upgraded. This article describes the symptoms, how to confirm whether the upgrade succeeded, and the workaround. ProfileUnity Client 6.9.5 HF2 resolves this defect and is the recommended target for any upgrade from 6.9.5 GA.

Status

Affected Configurations

This issue affects any environment where the ProfileUnity Client was originally installed using either the setup EXE or the MSI for 6.9.5 GA:

ProfileUnityClient.Setup_6.9.5ga7.exe
ProfileUnityClient.Setup_6.9.5ga7.msi

It does not matter how the installer was invoked — manually, via a GPO startup script, Intune Win32 deployment, or any other software deployment tool. Any endpoint where either the setup EXE or MSI ran for the initial 6.9.5 GA install may be affected when the corresponding HF1 installer is subsequently run. Both installer types leave the same residual file and both trigger the same skip behavior on the HF1 run.

Symptoms

After running the HF1 installer on an endpoint where the GA installer was previously used, you may observe any of the following:

• The installer exits without error and the MSI log (e.g., pulog.txt) reports installation completed successfully.
• The ProfileUnity Client version on the endpoint remains at 6.9.5 GA — it is not upgraded to HF1.
• Running the HF1 installer on a fully uninstalled endpoint also silently succeeds but leaves the client uninstalled.
• No startup_update_ log file is generated for the HF1 run, or the outer startup_ log shows launchStartupUpdateExeResult: False.

Cause

When either the 6.9.5 GA EXE or MSI runs, it writes a configuration file to the Windows Temp directory as part of the installation process. Due to a defect in 6.9.5 GA and HF1, this file is not cleaned up after installation completes.

The file path depends on the context the installer ran under:

When the HF1 installer subsequently runs, it detects the existing file and treats the installation as already complete — skipping the actual client install or upgrade entirely. The outer MSI layer reports success regardless, which is why no error is visible in pulog.txt.

How to Confirm Whether the Upgrade Succeeded

%LOCALAPPDATA%\Temp\ProfileUnity\

Workaround

Delete the residual file before running the installer. Both Temp paths should be cleared to cover SYSTEM and user context installs. The commands below are safe to run even if the file does not exist — they will silently succeed either way.

Option A — Script the cleanup as a pre-step (EXE or MSI deployments)

Add the following lines before the installer call in your deployment script. This applies whether you are deploying via GPO startup script, Intune, or any other software deployment tool:

:: Delete residual file — SYSTEM context (GPO, Intune Win32 System install)
del /f /q "C:\Windows\Temp\LwL.ProfileUnity.Client.Startup.Update.exe.config" 2>nul

:: Delete residual file — user context (manual run)
del /f /q "%TEMP%\LwL.ProfileUnity.Client.Startup.Update.exe.config" 2>nul

:: Run the installer (HF2 EXE example - recommended)
ProfileUnityClient.Setup_6.9.5hf2.exe /qn /log C:\Windows\Temp\pulog.txt ...

:: Or run the MSI directly
msiexec /i ProfileUnityClient.Setup_6.9.5hf2.msi /qn /log C:\Windows\Temp\pulog.txt ...

Option B — Delete manually on affected endpoints

On endpoints already affected, delete the residual file from the appropriate Temp path and re-run the installer. A full uninstall of the existing client is not required — deleting the file alone is sufficient.