Resolving STEP 7 Basic V11 SP2 Crashes on Windows 7 64-bit

Problem Summary

STEP 7 Basic V11 SP2 (the engineering tool bundled with TIA Portal for the SIMATIC S7-1200) presents two distinct failure modes on Windows 7 64-bit hosts:

1. Installation crash: Setup terminates with the .NET unhandled exception "Access to the path 'Q:/' is denied" very early in the installation wizard, before any TIA Portal components are deployed to disk.
2. Online monitoring crash: After a successful install and project download, switching from offline to online (Monitor/Modify) drops the TIA Portal process. A second, related symptom appears in which the S7-1200 CPU can be stopped from TIA Portal but cannot be started again until the engineering station is cycled offline/online.

Both failures are environment-related, not defects in the S7-1200 firmware or the user program. The root causes are Windows installer prerequisites, User Account Control (UAC) path virtualization, and the legacy SIMATIC installer behavior when it is pointed at non-NTFS or non-Unicode paths.

Affected Versions and Environment

Root Cause Analysis

Why the installer crashes with "Access to the path Q:/ is denied"

The TIA Portal V11 setup is a Windows Installer (MSI) chain that, before copying any files, attempts to write temporary housekeeping data to a drive letter Q:\. That drive letter is not a real physical volume; it is the legacy SIMATIC setup's reference for a redirected scratch path on 64-bit systems. When the following conditions coexist, the write fails:

• The Windows user is a member of Users (not Power Users or Administrators) and UAC is enabled. UAC virtualizes the write to %LOCALAPPDATA%\VirtualStore, but the legacy setup checks for write success at the literal path and throws an unhandled UnauthorizedAccessException.
• The path where the setup cache is unpacked contains non-Unicode (legacy 8.3 / codepage-specific) characters, accents, or a mapped network share.
• An antivirus, encryption filter driver, or backup agent is locking the parent directory while the setup probes it.

Why online monitoring crashes

When TIA Portal V11 first opens an online connection to the S7-1200, it negotiates the PG/PC interface, opens an ISO-on-TCP (port 102) or PROFINET AR to the CPU, and starts a subscription to cyclic variable services. The crash reported by the engineer ("as soon as I go to monitor it crashes") is consistent with:

• An incompletely installed SIMATIC NET PC software stack. TIA Portal V11 redistributes a minimum subset, but if the system previously had STEP 7 V5.x or a partial SIMATIC NET install, the TIA installer can leave stale OEM drivers (e.g., NDISProxy, s7oieh64x) registered. These clash with V11's online subsystem.
• Residual firewall rules on Windows 7 blocking outbound TCP/102 or TCP/34964 (PNIO) for S7-TIA-Portal.exe.
• The "Auto-hotspot" PROFINET device name discovery flooding the PG/PC interface with name-of-station ARP packets.

Why the CPU won't restart after STOP without an offline/online cycle

After CPU > Stop in TIA Portal V11, the internal session handle is left in a half-disconnected state. Issuing CPU > Run on that handle fails silently because the TIA Portal workbench believes the connection is still in RUNNING-state. Cycling offline/online drops the handle and opens a new one, which is why the workaround (go offline, go online, then Run) works. This is a known V11 SP2 workbench bug fixed in V11 SP2 Update 5 and in all V12+ releases.

Pre-Installation Prerequisites

Perform every step below on the target Windows 7 64-bit host before launching the TIA Portal V11 SP2 setup. Each item addresses one of the root causes identified above.

1. Log in as a local administrator. Right-click the setup executable and choose Run as administrator even when the active account is already in the Administrators group, because UAC tokens are still constrained for MSI chainers.
2. Enable .NET Framework 3.5.1. Open Control Panel > Programs and Features > Turn Windows features on or off and tick .NET Framework 3.5.1. Reboot.
3. Install Windows Installer 4.5 (KB942288) and the KB971644 patch for the MSI 5.0 chainer compatibility. The V11 SP2 setup requires MSI 5.0; Windows 7 ships with 5.0 but the KB above ensures correct handling of nested MSI sequences.
4. Confirm %TEMP% resolves to a clean NTFS path. Open cmd.exe as administrator and run echo %TEMP%. The path must be on a local NTFS volume, must not traverse a junction, and must not contain characters outside the Unicode BMP (no accents, no ideographs, no combining marks). Rename the user profile folder if necessary.
5. Disable UAC file virtualization for the setup process by launching setup from an elevated shell that has __COMPAT_LAYOUT unset, or set the HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\EnableLUA registry value temporarily to 0, reboot, install, then restore it to 1 and reboot again.
6. Exclude the install volume from real-time antivirus scanning for the duration of the install (real-time scan only; on-access is too aggressive against MSI cabinets).
7. Verify free disk space. TIA Portal V11 SP2 requires 6 GB for the engineering tool plus 1 GB for the project working directory on the system drive.
8. Verify PG/PC interface assignment. Open Control Panel > Set PG/PC Interface and ensure the network adapter that faces the S7-1200 is assigned to TCP/IP (Auto). If a SIMATIC NET version is already present, set the access point S7ONLINE to the same adapter.

Step-by-Step Resolution

Step 1 — Capture the install log before any retry

The setup log is the only reliable signal for the V11 chainer. Run the install from a Windows Explorer address bar:

explorer.exe "%autinstlog%"

This opens the auto-installation log directory. Note the most recent .log file, then launch the setup with:

Setup.exe /log "%autinstlog%\TIAV11SP2_install.log" /v"/l*v \"%autinstlog%\msi_verbose.log\""

The /v switch forwards the verbose MSI log flag to the inner MSI chain. After the crash, attach both files to the Siemens Support Request (see below).

Step 2 — Eliminate the path-source of the "Q:/" error

The literal error Access to the path 'Q:/' is denied means the chainer tried to probe Q:\ as a writable scratch drive. On clean Windows 7 installs there is no such drive; the chainer expects to remap it to a TEMP subfolder. Force the remap by:

1. Creating the scratch directory manually on the system drive, e.g. C:\SiemensScratch.
2. Adding the environment variable SIMATIC_SCRATCH=Q:\ for the elevated shell session, and using subst Q: C:\SiemensScratch to bind it.
3. Running subst with no arguments to confirm Q:\ is mapped before invoking the setup.

mkdir C:\SiemensScratch
set SIMATIC_SCRATCH=Q:\
subst Q: C:\SiemensScratch
subst
Setup.exe

After install completes, run subst Q: /D to remove the binding.

Step 3 — Clean any prior partial install

If a previous attempt left registry artifacts, the next install will reuse the bad state and crash in the same place. Remove:

• HKLM\SOFTWARE\Siemens\Automation
• HKLM\SOFTWARE\Wow6432Node\Siemens\Automation
• HKLM\SOFTWARE\Wow6432Node\Siemens\SharedTools
• The folders %ProgramFiles%\Siemens\Automation and %ProgramFiles(x86)%\Siemens\Automation
• The folder %CommonProgramFiles%\Siemens

Then reboot. This step is mandatory before re-running the V11 SP2 setup after a failed install.

Step 4 — Install with elevated, non-virtualized context

Open Start > All Programs > Accessories, right-click Command Prompt, choose Run as administrator, then launch the setup from that elevated shell:

cd /d "D:\Install\TIA_Portal_V11_SP2"
Setup.exe

Do not launch setup from a network share, from a USB drive with drive-letter reassignment, or from within a compressed NTFS folder.

Step 5 — Apply language and codepage defaults

The V11 SP2 chainer validates the system locale against its built-in MSI strings. Set the install language to English (United States) during setup even if the working language is German, French, etc. The UI language can be switched post-install from Options > Settings > General > User Interface Language. This prevents the chainer from choking on non-Unicode codepages (CP1252 vs CP1251).

Resolving the Online Monitoring Crash

Once the install completes, perform the following before opening any project.

1. Confirm the PG/PC interface. In TIA Portal, Options > Set PG/PC Interface → select the Ethernet adapter bound to the S7-1200 subnet as TCP/IP (Auto). The S7ONLINE access point must point at the same adapter.
2. Disable Windows Firewall for the engineering network or add inbound rules allowing S7-TIA-Portal.exe and Siemens.Automation.Portal.exe for TCP/102, TCP/34964 (PROFINET IO), and UDP/34964.
3. Verify S7-1200 reachability from cmd.exe: ping <CPU IP> and arp -a should both succeed. The default IP is 192.168.0.1 / mask 255.255.255.0.
4. Re-seat the PROFINET device name if it was assigned on a previous network. Use Online > Accessible Nodes → right-click the CPU → Assign PROFINET Device Name. The S7-1200 will refuse online subscriptions if its stored name conflicts with another node on the LAN.
5. Clear the TIA Portal online cache. Close TIA Portal. Delete %LOCALAPPDATA%\Siemens\Automation\TIA Portal V11\<version>\Cache\Online. Reopen and go online.
6. Patch to V11 SP2 Update 5 (build number 11.0.2.5) or later. This addresses the monitor-crash signature where the workbench lost its connection handle the first time it switched to Monitor after a download.

Resolving the CPU Start/Stop State Hang

If TIA Portal refuses to put the CPU back into RUN after a STOP, perform the following in order. Each step is less invasive than the next.

1. Toggle the online state. Click Go offline, wait two seconds, then Go online. Issue CPU > Run.
2. Use the MRES button on the CPU. Hold the MRES button for 3 s to clear the workbench session from the CPU side. Re-establish online from TIA Portal.
3. Power-cycle the S7-1200 with the 24 V supply off for at least 10 s, then on. The CPU will run from its last loaded project if no re-download is required.
4. Re-download the project from Online > Download to device. This drops and recreates the connection table inside the CPU.

Permanent fix: install V11 SP2 Update 5 (or migrate to V13 SP1 / V15.1 / V17 where the workbench session state machine is rebuilt).

Verification

After applying the resolution, verify the install and the online path end-to-end.

1. Open TIA Portal V11 SP2 and create a new project. Save it to a path on the system NTFS volume without Unicode characters.
2. Add an S7-1200 device with the firmware matching the physical CPU.
3. Compile the empty project (right-click the PLC → Compile > Software (rebuild all)). The compile must complete without warnings related to TIA Portal installation integrity.
4. Connect to the CPU: Online > Accessible Nodes. The CPU should appear within 5 s on a 100 Mbit LAN.
5. Download and go online. Place a tag in the Monitor/Modify table. The watch value must update within the OB1 cycle (default 100 ms).
6. Toggle CPU Run/Stop ten times in a row. Every Run command must take effect within 1 s and the RUN LED on the CPU must illuminate. This confirms the workbench session bug is patched.
7. Reboot the engineering station. Re-open the project and confirm that online monitoring resumes without a TIA Portal crash.

Alternative: Windows XP Mode Virtual Machine

When the engineering host must remain on Windows 7 64-bit and the steps above cannot be made to work (locked-down corporate image, antivirus that cannot be disabled, missing admin rights), install TIA Portal V11 SP2 inside the Windows XP Mode (XPM) virtual machine that shipped with Windows 7 Professional and above. XPM provides a 32-bit Windows XP SP3 environment with USB passthrough, sufficient for an S7-1200 connected via the PROFINET interface of the host.

1. From Programs and Features > Turn Windows features on or off, enable Windows Virtual PC and download Windows XP Mode.
2. Boot the XPM VM, install TIA Portal V11 SP2 inside it.
3. Configure the VM's network in Shared Networking (NAT) mode for online use, or in Bridged mode if the VM must be on the same subnet as the S7-1200.
4. Disable UAC inside the VM; it is not required for an XP guest.

This is the path the source engineer originally resisted but is the highest-success-rate option when the host image cannot be modified.

When to Open a Siemens Support Request

Open a ticket with Siemens Industry Online Support when any of the following holds after applying all steps above:

• The setup still aborts at the same "Access to the path" error after the subst Q: workaround and a clean registry.
• The online monitor crash is reproducible on two different Windows 7 64-bit hosts.
• The CPU Start/Stop toggle still hangs after applying V11 SP2 Update 5.
• Antivirus / encryption software is non-removable and the install abort signature matches the encryption filter driver pattern in the log.

Attach the install logs from %autinstlog%, the exact Windows build number (winver), and the CPU's order number (e.g., 6ES7214-1AG40-0XB0) and firmware version (read from the CPU display or from Online > Accessible Nodes → Diagnostics). Siemens assigns these to the STEP 7 Basic / TIA Portal product family under the Installation / Commissioning subtopic; expected response time on a paid support contract is one business day.

Troubleshooting Matrix

FAQ