Troubleshoot WinCC Explorer Freezing After PCS 7 V9.1 OS Activation

In one migrated PCS 7 V9.1 installation, OS Runtime activated and clients connected, but the WinCC Explorer window became unresponsive; the report says the condition stopped after the startup task OSStateMachine.exe was removed. That is a case-reported workaround, not a Siemens-documented universal fix. Confirm the executable's origin and how it is started before changing startup behavior, then verify both Explorer responsiveness and OS Runtime operation in a controlled test.

Reported Symptoms and Scope

The report describes a newly installed virtual system with a project migrated from PCS 7 V8.2 to V9.1. On both OS servers, WinCC Explorer opened the project and OS Runtime activated, after which Explorer stopped responding and showed a busy cursor. Windows remained usable, CPU and memory use were not reported as high, clients connected to the servers, and attempts to reset WinCC and restart did not help. The final report attributes the symptom to OSStateMachine.exe listed as a startup task and says removing it restored operation.

Separate Runtime State From Explorer Responsiveness

The reported runtime activation completed and OS clients connected while the WinCC Explorer interface was frozen. Those observations distinguish the reported problem from a simple failure to start OS Runtime. The greyed-out deactivate button in Explorer and the failed attempt to deactivate from Runtime are additional reported symptoms, but the available evidence does not establish their cause.

Assess the Reported Workaround Safely

The case does not identify the full path, publisher, startup mechanism, arguments or purpose of OSStateMachine.exe; it also does not describe how the task was removed or whether the change was tested after a controlled restart. Before changing an OS server:

Record the exact executable path, file properties and publisher, startup entry or task name, trigger and command-line arguments. Preserve relevant logs and the WinCC/PCS 7 versions.
Establish whether this is a production or redundant server and ensure the site's approved backup, availability and change-control arrangements are in place.
Identify what installed or configured the task and whether it is required by the project's startup design. Do not delete the executable or disable an unidentified startup item based only on its name.
If engineering review confirms the entry is the same one implicated in the case and a controlled test is authorized, test the startup change on a nonproduction or approved maintenance system first. Make one change at a time and retain a rollback path.
After a controlled restart, verify that Explorer remains responsive, Runtime activation completes, clients connect and operators can perform the functions expected for that station. A single successful test does not prove the change is suitable for other projects or PCS 7 installations.

Version and Migration Context

The project was reported as migrated from PCS 7 V8.2 to V9.1. The report does not identify the V9.1 service pack, virtual-machine platform, WinCC component build, source or publisher of OSStateMachine.exe, or the task configuration. Migration history is useful diagnostic context but is not proof that migration caused the freeze.

Verification

Reproduce the original condition under change control and record the exact stage at which Explorer becomes unresponsive. During any authorized test, check Explorer separately from Runtime: confirm the engineering interface accepts input, Runtime reaches its expected state, and clients remain connected. Review Windows and PCS 7 logs for the same interval and compare the startup-task inventory before and after the change.

Limitations and Operational Precautions

The reported removal of OSStateMachine.exe is a user-reported resolution without independent manufacturer documentation in the available references. Its executable identity and operational role remain unknown. Do not use the observation as a general instruction to remove the file or disable a service. On a redundant or production OS, coordinate changes to preserve availability and establish how to restore the prior startup configuration.

Engineer FAQ

Did OS Runtime fail to activate in the reported case? The report says activation completed and clients connected, even though WinCC Explorer became unresponsive.

What task was reported as the cause? The final reply names OSStateMachine.exe as a startup task and says removing it stopped the problem.

Is removing OSStateMachine.exe a Siemens-approved fix? No such approval or general procedure is established by the available documentation.

Should the executable be deleted? No. The report says the startup task was removed; it does not specify deleting the binary. Identify its origin and preserve a rollback path.

Does migration from V8.2 to V9.1 prove a compatibility fault? No. The migration is reported context, but the case attributes the symptom to a startup task and provides no evidence that migration caused it.

Does a connected OS client prove the server is fully healthy? No. It is one reported observation; verify Explorer, Runtime and expected operator functions separately.

What details are missing to reproduce the workaround? The report omits the executable path, publisher, task mechanism, trigger, arguments, service pack and a controlled retest procedure.

Should the change be tested on both redundant servers at once? The report does not establish a safe redundancy sequence. Follow the site's version-specific redundancy and maintenance procedure and preserve server availability.

What should be monitored after an authorized startup change? Check Explorer responsiveness, Runtime state, client connections, relevant Windows/PCS 7 logs and any station-specific operator functions.

What if the window still freezes after the task is removed? Restore the prior configuration if appropriate and investigate the full process/task inventory and logs with version-specific Siemens support; the source gives no further confirmed remedy.

Technical References

Siemens, PCS 7 V9.1 Readme (Online), document A5E42575789-AA (version-specific installation and usage reference; it does not document OSStateMachine.exe as a cause or fix): https://cache.industry.siemens.com/dl/files/270/109780270/att_1057737/v1/pcs7-readme_en-US.pdf
No opened Siemens manufacturer reference located for the reported OSStateMachine.exe startup-task workaround. The cause and repair remain case-reported and require review.

Related Tags

SIMATIC PCS 7
WinCC Explorer
OS Runtime
OS server

Troubleshoot WinCC Explorer Freezing After PCS 7 V9.1 OS Activation