How to Troubleshoot and Resolve MSI Installation Issues for Lucen Timeline or Similar Applications
When installing MSI-based applications like Lucen Timeline, you may encounter issues such as leftover data, stale registry entries, or retry behaviors that block the installation. This guide provides step-by-step instructions to identify and resolve these problems.
Common Issues and Their Causes
Leftover Data or Incorrect Product Entries: Previous installations may leave behind data or registry entries that conflict with new installations. For example, the product may appear under a different name, such as "Office Timeline" instead of "Lucen Timeline."
Stale Registry Entries: Partial installations can leave behind registry entries with mismatched permissions, causing error codes like 1603 during installation.
Automatic Retry Behaviors: Tools like Intune may repeatedly attempt installations, encountering leftover data from previous attempts and triggering installation blocks.
Step-by-Step Troubleshooting Guide
Step 1: Verify and Remove Leftover Data
Run the uninstall troubleshooter and ensure you select the correct product entry.
If the product appears under a different name (e.g., "Office Timeline"), remove that entry instead.
Once the correct product is fully removed, attempt the installation again using the MSI installer.
Step 2: Check for Stale Registry Entries
Verify Registry State: - Run the following PowerShell commands as the signed-in user (no elevation required): Get-Acl 'HKCU:\Software\Microsoft\Installer\UpgradeCodes\975394E8D4C80354A8E23B83BD947048' | Format-List Owner, Access Test-Path 'HKCU:\Software\Microsoft\Installer\Products\FA6CCA248BD16B9409A2B23BB3D33E59' Test-Path 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\{42ACC6AF-1DB8-49B6-902A-2BB33B3DE395}' - If the owner is not the signed-in user (e.g., SYSTEM or Administrators), this indicates a permissions mismatch.
Remove Stale Entries: - Open an elevated PowerShell session (Run as Administrator). - Temporarily allow script execution for the process: Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass - Execute a cleanup script (e.g.,
Cleanup-LucenTimeline.ps1) to remove stale registry entries under HKCU for the affected user. - After cleanup, rerun the MSI installer in the correct context.
Step 3: Identify Retry Behaviors
Review the device’s app installation history in Intune or similar tools.
Look for multiple failed attempts prior to the current issue. This indicates that retry behaviors are re-running the installer in the same system context, encountering leftover data and triggering blocks.
Conclusion
By following these steps, you can resolve common MSI installation issues for Lucen Timeline or similar applications. If problems persist, provide detailed outputs from the troubleshooting steps to your support team for further analysis.