Resolving TIA Portal V13 Installation Error 7ab4d.msi After BSOD

Siemens TIA Portal V13 (Totally Integrated Automation Portal, released 2014) is the engineering framework used to configure SIMATIC S7-1200, S7-1500, ET 200, SINAMICS drives, SIMOTION, HMI Panels, and WinCC V13 SCADA stations. The installation package is built on Microsoft Windows Installer (MSI) technology and stores staged components in the protected C:\Windows\Installer cache and corresponding HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer registry hive. A blue screen (BSOD) that interrupts the installer mid-transaction can leave the system in a half-installed state where the MSI database cache is corrupted, the registry still references the missing file, and every subsequent re-run of Setup.exe aborts with "Failed to open Windows Installer database; C:\Windows\Installer\7ab4d.msi" (or a sibling hash such as 8cbb96.msi, a1f3e2.msi). This article documents the engineer-grade recovery procedure used to clear the orphan reference and complete the TIA Portal V13 install on Windows 7 Enterprise 64-bit.

1. Problem Description and Symptom Matrix

The error pattern is deterministic: a clean Windows 7 SP1 x64 workstation, the TIA Portal V13 DVD mounted or extracted, the user double-clicks Start.exe > Setup.exe, and within a few seconds the installer aborts. The visible dialog reads:

Failed to open Windows Installer database.
C:\Windows\Installer\7ab4d.msi

The hash suffix in the filename (e.g., 7ab4d.msi, 8cbb96.msi) is a Windows-generated identifier assigned when the package is first cached. It changes every time the installer is launched, so two consecutive attempts may report different filenames — this is normal and not an indication that the DVD image is corrupt.

2. Root Cause Analysis

The Windows Installer engine (msiexec.exe, version 5.0.x for Windows 7 SP1) uses two coordinated repositories to track installed applications:

1. File cache — C:\Windows\Installer (hidden, system, ACL: SYSTEM:F / Administrators:F / Users:RX). All MSI/MSP packages installed on the machine are copied here under hash names so they can be repaired or uninstalled without the original media.
2. Registry database — HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\<S-1-5-18>\Products and ...\Installer\Folders. Each product key stores a LocalPackage REG_SZ pointing to the cached MSI file.

When Setup.exe starts a TIA Portal V13 install, it streams the MSI payload into the cache, then commits the registry keys. A BSOD, power loss, or forced reboot between these two steps creates an inconsistent state:

• The cache contains a truncated or zero-byte .msi (the file exists, but its size is < the expected several MB and the PE/MSI signature is invalid).
• The registry LocalPackage pointer references the truncated file.
• On every subsequent launch, msi.dll opens the cache file, fails the consistency check, and returns the E_FAIL referenced above.

Because the registry still believes the product is partially installed, Windows Installer refuses to start a fresh transaction. Simply re-running the setup, re-extracting the DVD, or running Setup.exe /repair will not clear the reference; the installer always reads the registry before it touches the media. The fix is to delete the orphan file and its registry reference so the installer can stage a clean copy.

3. Prerequisites and Pre-Flight Checks

Verify the following before making any destructive change to C:\Windows\Installer or the registry:

1. OS eligibility — TIA Portal V13 (without Update) is supported on Windows 7 SP1 (32/64-bit) Professional, Enterprise, and Ultimate. TIA Portal V13 SP1 also supports Windows 8.1 and Windows Server 2012 R2. The DVD is not supported on Windows 10 / 11 directly; on those OS versions, upgrade to TIA Portal V15.1 or later.
2. .NET Framework prerequisites — .NET Framework 4.5.x is installed. Verify with reg query "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" /v Release. The value 378389 or higher is required.
3. Administrator context — Run cmd.exe as Administrator (right-click → "Run as administrator"). UAC must not be silently blocking the writes to C:\Windows\Installer.
4. Windows Installer service — Confirm the service is running: sc query msiserver. STATE: 4 RUNNING is expected. If it is STOPPED, run sc start msiserver and set the start type to Manual (the service stops when not in use by design).
5. Free disk space — Minimum 20 GB free on C: for the full TIA Portal V13 install (STEP 7 V13, WinCC V13, S7-PLCSIM V13, SINAMICS Startdrive V13, and component media).
6. Pending reboots — No pending restarts. Run shutdown /a to abort any pending restart, then complete all outstanding Windows Updates and reboots before continuing.
7. Antivirus exclusion — Temporarily disable or exclude the TIA Portal install path and C:\Windows\Installer from real-time AV scanning. Some endpoint protection products quarantine MSI files mid-write, which recreates the same corruption symptom.

4. Step-by-Step Resolution

The procedure below is the field-proven recovery sequence. It removes the orphan reference without uninstalling any other TIA Portal components that may already be present (e.g., a previous V12 install or a partial V13 SP1).

4.1 Reveal the Hidden Installer Cache

1. Open Control Panel → Folder Options (Windows 7: also accessible via Organize → Folder and search options in any Explorer window).
2. Switch to the View tab.
3. Select "Show hidden files and folders".
4. Uncheck "Hide protected operating system files (Recommended)". Confirm the warning dialog.
5. Click Apply, then OK.
6. Navigate to C:\Windows\Installer. The folder will now show hash-named MSI/MSP files. Do not open or run any of these files directly.

4.2 Delete the Orphan .msi File

1. In C:\Windows\Installer, sort by Size.
2. Identify the file named in the error dialog (e.g., 7ab4d.msi).
3. Right-click the file → Properties and confirm the file size. A corrupted file is typically 0 KB or a few hundred KB instead of the expected 5–200 MB for TIA Portal V13 product MSIs.
4. Close Properties, then Shift+Delete the file to bypass the Recycle Bin. Confirm the elevation prompt.
5. If the OS reports "Access is denied", take ownership: right-click → Properties → Security → Advanced → Owner → change to Administrators, apply, then retry the delete.

Equivalently, from an elevated command prompt:

takeown /f "C:\Windows\Installer\7ab4d.msi" /a
icacls       "C:\Windows\Installer\7ab4d.msi" /grant Administrators:F
del /f /q    "C:\Windows\Installer\7ab4d.msi"

4.3 Remove the Orphan Registry Reference

The registry keys that point to the corrupt MSI live under the product hive. Open regedit.exe as Administrator and perform the following searches. Back up the registry hive first: File → Export → Selected branch → Installer and save as installer-backup.reg.

1. Search 1 — by filename: Press Ctrl+F, search for 7ab4d.msi (or the hash from your error). Delete each value-data match that contains the full path. Only delete REG_SZ values named LocalPackage or LocalPatchPackage; leave product InstallSource, DisplayName, and similar values intact.
2. Search 2 — by folder path: Press F3 to repeat the search until the message "Finished searching the registry" appears. Common hive locations to inspect manually if the search misses a value:\li>

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\<ProductCode>\InstallProperties
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\<ProductCode>\Patches
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Folders
HKLM\SOFTWARE\Classes\Installer\Products\<ProductCode>
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\<ProductCode>

The <ProductCode> GUIDs are 32-character hex strings, e.g., {4D8C9F71-3A8E-4B1C-9F5A-2E7B6C1A8D9F}. Identifying the right GUID requires matching the DisplayName string against "Siemens TIA Portal" or "STEP 7" in InstallProperties.

3. Close regedit without saving (you have already exported the backup).

4.4 Clear the TEMP Directories

Stale .tmp MSI staging files in the user and system temp directories can re-introduce the same corruption on the next attempt.

1. Open an elevated cmd.exe.
2. Stop the Windows Installer service: net stop msiserver (it will report "The Windows Installer service is not started" if it is already stopped — this is normal).
3. Delete the contents of the system temp directory:

del /f /s /q "%SystemRoot%\Temp\*.*"
del /f /s /q "%TEMP%\*.*"
del /f /s /q "C:\Users\<user>\AppData\Local\Temp\*.*"

4. Optionally, rename the system temp folder and let the OS recreate it: ren %SystemRoot%\Temp Temp.old. Windows will rebuild the folder on the next installer run.
5. Reboot the workstation. The reboot ensures that no lock handles from the previous failed install are still attached to C:\Windows\Installer.

4.5 Re-Run the TIA Portal V13 Installer

1. Insert or remount the TIA Portal V13 DVD. If the original media is on a network share, disconnect and reconnect to clear SMB locks.
2. Right-click Start.exe → Run as administrator. The Start.exe is the autorun launcher that detects prerequisites (MSXML 6.0, .NET 4.5, SQL Server 2012 Express, WinPcap 4.1.3) and pre-installs them before launching the main product installer.
3. On the language selection, accept English (default) and continue.
4. Accept the license agreement and enter the Siemens Automation License Manager (ALM) license keys if available. The installer can proceed without keys in "Trial" mode for 21 days.
5. Select the products to install. For a typical commissioning laptop, select: STEP 7 V13, WinCC V13, S7-PLCSIM V13, Startdrive V13, and the SIMATIC NET PC software component.
6. Click Install. The setup will now pass the Windows Installer check, re-stage a fresh copy of every MSI in C:\Windows\Installer, and write the registry keys for each product.
7. Allow 30–90 minutes for the full install. Do not interrupt the process; if a second BSOD occurs, restart the workstation and rerun Setup.exe with the /reinstall switch — it will detect the partial state and resume.

5. Verification

After the install completes, run the following checks to confirm a clean state and to catch any residual orphan references:

1. Programs and Features inventory — Open Control Panel → Programs and Features. Confirm that STEP 7 V13, WinCC V13, S7-PLCSIM V13, and Startdrive V13 are listed with publisher "Siemens AG" and version "13.0.0.0" (or 13.0.1.0 for the SP1 update).
2. TIA Portal launch — Launch TIA Portal from the Start menu. The first launch performs a one-time workspace initialization (typically 60–120 seconds). The Portal view should display the "Start" page with options to "Create new project", "Open existing project", and "Migrate project".
3. Version verification — In TIA Portal, click Help → About. Confirm the version, build number, and that no red X marks indicate missing components.
4. Add new device — From the Portal view, click Add new device and confirm that the controller catalog includes S7-1200, S7-1500, ET 200SP, and ET 200AL. If the catalog is empty, the SIMATIC device description (SDDUP) installation is missing — rerun Start.exe and select only the device libraries.
5. Cache integrity — From an elevated cmd.exe, list the MSI cache files larger than 5 MB:

dir /a /s "C:\Windows\Installer\*.msi" | findstr /R "MS.* 5[0-9][0-9][0-9][0-9][0-9][0-9][0-9]"

There should be roughly 30–60 large MSI files for a full TIA Portal V13 install. Any 0 KB file is a new orphan and should be removed as described in §4.2.

6. Service health — sc query msiserver should return STATE: 1 STOPPED (the service is manual-start and only runs on demand) and START_TYPE: 3 DEMAND_START.
7. Event log — Open Event Viewer → Windows Logs → Application. Filter for Source = MsiInstaller. There should be no "Product: ... Installation failed" events from the current install attempt. Informational events with Event ID 1040 / 1042 / 11728 are expected and benign.

6. Alternative Recovery Methods

If the registry cleanup in §4.3 does not resolve the error — for example, because the orphan is a patch (MSP) rather than an MSI, or because the product code cannot be matched — use one of the following advanced procedures.

6.1 Force-Reinstall via msiexec

Use the msiexec command line to re-stage a known-good MSI directly from the DVD without invoking the registry cache:

msiexec /fvomus <path-to-DVD>\Siemens.Automation.Portal.V13.msi /l*v C:\Temp\tia_repair.log REINSTALL=ALL REINSTALLMODE=omus

6.2 Reset the Windows Installer Database

If multiple orphan references are suspected, run the Microsoft Fix It / Program Install and Uninstall troubleshooter to scan the registry and rebuild the Programs and Features list. The tool is published under KB 2438651 and runs without network access.

6.3 Last-Resort: Re-Image the Workstation

If the workstation is shared with other engineering tools (EPLAN, TIA Multiuser Server, S7-PCT) and the registry cannot be guaranteed clean, the most reliable engineering practice is to re-image the laptop with a known-good Windows 7 SP1 x64 image and reinstall TIA Portal V13 cleanly. The cost of a 4-hour reinstall is typically lower than the risk of chasing cascading MSI errors across a long deployment.

7. Prevention and Field-Proven Caveats

1. Never interrupt a TIA Portal install. The TIA setup writes 30+ MSI files to the cache, then 1,200+ registry keys. Any interruption between the MSI staging and the registry commit reproduces the exact error in this article.
2. Disable sleep/hibernate during install. Windows 7 power policies can put the laptop to sleep mid-install, which behaves like a BSOD for MSI purposes. Use powercfg -change -standby-timeout-ac 0 and powercfg -change -hibernate-timeout-ac 0 for the duration of the install.
3. Exclude C:\Windows\Installer from AV real-time scanning. Several endpoint protection suites (Symantec Endpoint Protection, Trend Micro OfficeScan, McAfee ENS) misclassify large MSI files and quarantine them mid-write. Configure an exclusion for the directory and the .msi/.msp extensions.
4. Snapshot the laptop before install. Use Windows Complete PC Backup, a Veeam Agent, or a vendor recovery partition to snapshot the disk immediately before the first TIA Portal install. Recovery from a snapshot is 5 minutes; full recovery from a corrupt registry is a day.
5. Install TIA Portal V13 SP1 immediately after V13. SP1 (released October 2014) addresses several installer resilience issues and adds Windows 8.1 / Server 2012 R2 support. The upgrade install performs its own MSI consistency check and will report a clean state.
6. Avoid parallel installs. Do not run other MSI installers (e.g., .NET updates, SQL Server cumulative updates) in parallel with the TIA setup. MSI is a single-threaded service in Windows 7, and concurrent transactions will deadlock.

8. Related Errors and Adjacent Troubleshooting

9. Documented Build Versions and Compatibility

For active commissioning in 2024 and beyond, Siemens officially supports TIA Portal V17 (Win 10 1809+) and V18 (Win 10 20H2+). TIA Portal V13 is in the "Limited / Mature" lifecycle phase and is no longer recommended for new installations. The fix described in this article remains valid for any engineer maintaining a legacy commissioning laptop running Windows 7.

10. Frequently Asked Questions