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),
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 until the fix ships in
6.9.5 HF2.
📄 Contents
Status
| Issue Status | FIX IN PROGRESS |
| Fix Version | ProfileUnity Client 6.9.5 HF2 — expected later this month |
| Workaround Available | Yes — see below |
Affected Configurations
This issue affects any environment where the ProfileUnity Client was originally installed using the setup EXE:
It does not matter how the EXE was invoked — manually, via a GPO startup script, or through a software deployment tool. Any endpoint where the setup EXE ran for the initial 6.9.5 GA install may be affected when the HF1 setup EXE is subsequently run.
Symptoms
After running the HF1 setup EXE on an endpoint where the GA setup EXE 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 EXE 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 outerstartup_log showslaunchStartupUpdateExeResult: False.
pulog.txt)
reflects only the outer MSI wrapper and will show success even when the client
was not installed or upgraded. Always validate the actual version on the
endpoint using the steps in the next section.
Cause
When ProfileUnityClient.Setup_6.9.5ga7.exe
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:
| Install Context | Residual File Path |
|---|---|
|
SYSTEM context e.g. GPO computer startup script |
C:\Windows\Temp\LwL.ProfileUnity.Client.Startup.Update.exe.config |
|
User context e.g. run manually as a logged-in user |
%TEMP%\LwL.ProfileUnity.Client.Startup.Update.exe.config |
When the HF1 setup EXE 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
Check 1 — Verify the installed version
Open Apps & features (or Programs and Features) on the endpoint and look for ProfileUnity Client. If it still shows the GA build after running the HF1 installer, the upgrade did not apply.
Check 2 — Look for the residual file
Check the Temp path appropriate for your install context (see the table above). If the file exists, the upgrade was blocked by it.
Check 3 — Review the installer logs
After the HF1 installer runs, check for a startup_update_
prefixed log in:
If no new startup_update_
log exists for the HF1 run, or the shorter startup_
log contains launchStartupUpdateExeResult: False,
the residual file was present and the upgrade was skipped.
Workaround
Delete the residual file before running the HF1 installer. Both Temp paths
should be cleared to cover SYSTEM and user context installs. The
del
commands below are safe to run even if the file does not exist.
Option A — Script the cleanup as a pre-step
Add the following lines before the HF1 installer call in your deployment script:
del /f /q "C:\Windows\Temp\LwL.ProfileUnity.Client.Startup.Update.exe.config" 2>nul
:: Delete residual file — user context
del /f /q "%TEMP%\LwL.ProfileUnity.Client.Startup.Update.exe.config" 2>nul
:: Run the HF1 installer
ProfileUnityClient.Setup_6.9.5hf1.exe /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 HF1 installer. A full uninstall of the existing client is not required — deleting the file alone is sufficient.
| Product | Liquidware ProfileUnity with FlexApp |
| Applies To | ProfileUnity Client 6.9.5 GA and 6.9.5 HF1 |
| Updated | July 9, 2026 |