IMDTouchKnowledge BaseShop main store

Troubleshooting

Why WinCC 7.5 Runtime Fails Under a New Windows User

HMI and touchscreens Published 8 min read

Short answer

Runtime failing under a newly created Windows account while Explorer opens is a Windows security-context problem, not a WinCC project problem. Put the account in the SIMATIC HMI group, sign out fully, verify effective access to the project, and after an Admin password change update the logon identities of services and scheduled tasks.

On this page
  1. Why does WinCC Explorer start but Runtime never launch?
  2. Which Windows groups does a WinCC 7.5 user have to be in?
  3. Why didn't adding the group change anything?
  4. How do I check the new account's access to the project?
  5. Why did WinCC stop after an Admin password change?
  6. How do I find the component still using the old password?
  7. What order do I fix this in?
  8. How do I prove Runtime is really fixed?
  9. Questions asked

When WinCC 7.5 Runtime refuses to start under a newly created Windows account while WinCC Explorer opens normally, the fault is in the account's Windows security context, not in the project. Three things decide the outcome: membership in the documented SIMATIC HMI group, effective access to the project location, and, after an Admin password change, valid credentials in the services and scheduled tasks that start WinCC components. Fix them in that order and sign out fully after any group change. The same discipline explains the password-change outage: components that keep their own copy of the old password fail while the desktop sign-in still succeeds.

Why does WinCC Explorer start but Runtime never launch? #

Because launching an executable and activating a project are two separate Windows authorization checks: an open Explorer window only proves the account can start WinCC Explorer, not that it can activate the project or reach every resource Runtime touches.

A security context is the identity, its group memberships and its permissions, carried by every process the account starts. Explorer opening proves one fact: this account may launch that executable. Activating a multi-client project asks Windows several further questions, and Runtime stops at the first refusal.

In the layout described here, two servers, several clients, existing Admin and User accounts working, the client, the project and the servers are proven by the working accounts. The only new variable is the account, so compare accounts before touching the project. One pre-check first: look in Task Manager for an orphaned Runtime process from an earlier session, and end it or restart the client, because a stale process blocks a new activation on its own.

What you observe What it proves Next check
Explorer opens; Runtime never creates a process Launch rights exist; activation refused before start Group membership, then effective access
Runtime starts and exits within seconds Activation began, then lost a resource or credential First error in the application event log at that second
Runtime runs but shows no picture Process alive; data or server authentication failing Server-side identity and connection diagnostics
Every account fails, including known-good ones Fault is not account-bound Treat it as a project fault; see the rebuild note below

A start-and-exit on every account is a different family of problem, the project itself, as in why WinCC 8.0 runtime deactivates after a v7.5 migration. Your symptom, never launching on one account only, stays in the security-context column until a working account on the same client proves otherwise.

Which Windows groups does a WinCC 7.5 user have to be in? #

Membership in the documented SIMATIC HMI group is the baseline requirement: Siemens states all users must be members of this group to create, process, start and remotely access projects, so that is the first thing to compare against a working account.

Siemens states the requirement in the WinCC V7.5 system information, entry 109762744: every user must sit in the "SIMATIC HMI" group, and it is these members who may create local projects and process, start and reach projects remotely. Remote access is precisely what a client in a two-server multi-client system does, so the group is not optional in that layout. Related groups such as "SIMATIC HMI Viewer" exist where the installed components create them, and the documentation for the installed version defines each role.

Your working accounts are the reference configuration. In Computer Management, under Local Users and Groups, place the new account in the same WinCC-related groups a working account holds, and confirm the two lists match before testing anything else.

Why didn't adding the group change anything? #

Because Windows stores group membership in the access token issued at sign-in, an account whose groups were changed mid-session keeps using the old token until you sign out completely and sign back in.

Windows builds the token at sign-in. Group edits made afterwards never reach tokens already issued, and anything launched from the old session, a WinCC Explorer window left open, an auto-start inherited from the previous logon, keeps running on the stale token. Closing the application is not enough: sign out completely, sign back in, and only then retry activation. A restart issues the same fresh token and clears an orphaned Runtime process besides.

One caution belongs here: support threads report User Account Control settings interfering with WinCC simulation and runtime startup in some installations, but disabling UAC is a last-resort test, not a fix, because it removes an operating-system guard from the runtime PC. Exhaust the group and access work first.

How do I check the new account's access to the project? #

Use the effective-access view of the project folder's advanced security dialog for the new account, not a reading of group names: it resolves every applicable permission, including explicit deny entries that override grants and block Runtime regardless of membership.

Effective access resolves every permission applying to the account, groups, explicit grants, explicit denies, and one deny entry overrides any grant, which is why a membership check can pass while Runtime still fails. Evaluate it from the account itself, never from an administrator session, because the token you test with is the token Runtime will carry.

Two boundaries decide the result in a multi-client system. When the project sits behind a network share, the decision combines share permissions with file permissions and both must allow the account. And local accounts exist per machine: the same username on a client and on a server is two identities, so success on the client proves nothing about either server.

Why did WinCC stop after an Admin password change? #

Because services and scheduled tasks that run WinCC components under that Admin account store their own copy of the password, a password change strands them with stale credentials even though a desktop sign-in with the new password succeeds.

A password change touches authentication only; it removes no membership and no permission, which makes this outage a separate branch even though it ends in the same dead Runtime. Services and scheduled tasks that start WinCC components under that Admin account keep their own stored logon credentials, keep presenting the old password, and are refused. Stored credentials for remote connections to the servers fail the same way.

Keep these Windows identities apart from the operator accounts inside the project's user administration. That layer governs runtime operations, breaks differently, HMI user management working in simulation but not on the panel is the typical picture, and is repaired in the project, not in Windows.

How do I find the component still using the old password? #

Open the Services console and Task Scheduler and list every entry whose logon identity is the affected account, then read the Windows system event log for logon failures from those components at the time WinCC stopped.

List the consumers first: every WinCC-related entry in the Windows Services list and in Task Scheduler whose logon identity is that Admin account, plus stored remote credentials pointing at the two servers. Then open the system and application event logs for the minute the failure began and find the first failed operation; errors logged later are downstream effects of that first refusal.

Worked example with illustrative timestamps: the Admin password changed at 16:00 on Friday, and Monday's automatic start fails. The system event log records a logon failure for a WinCC-related service at 06:30:12 and an identical one at 06:30:27. The second is 06:30:27 - 06:30:12 = 15 s after the first, a retry, not a new cause. The application log's first project error appears at 06:30:29, which is 06:30:29 - 06:30:12 = 17 s after the service logon failure, so the credential failure precedes the project error. Decision: update the stored password on that service's logon identity; expect the project errors to disappear with it.

Update a stored credential only after tracing its component into the startup path; blanket password changes across services you have not traced add new unknowns to an already noisy failure.

What order do I fix this in? #

Work from the working account down: confirm the baseline with a known-good account, add the missing group, refresh the session, verify effective access, then repair credentials, one change per activation attempt so each result means something.

  1. On one affected client, activate the same project with a known-working account, using the same startup method, and record the result as your baseline.
  2. Check Task Manager for an orphaned Runtime process; end it or restart the client.
  3. In Computer Management, compare the new account's WinCC-related groups with the working account's and add what is missing, starting with SIMATIC HMI.
  4. Sign out completely, sign back in, and retry the activation unchanged.
  5. If it still fails, check effective access on the project location and repair the specific missing permission, one deny entry or share restriction at a time.
  6. For the password-change outage, update the logon identity on every traced service and scheduled task, and the stored credentials to the servers.
  7. Retest after exactly one change and record the result; keep a correction only if it removes the identified failure without widening privileges beyond the required role.

How do I prove Runtime is really fixed? #

Sign out and back in on the affected client, activate the project with the corrected account alone, and watch the Runtime process through startup: it must stay running and reach its normal picture without a second account or elevation.

  • Fresh-session activation: after a full sign-out and sign-in, the corrected account alone activates the project and Runtime reaches its normal picture.
  • Persistence: the Runtime process survives startup and initialization instead of appearing and exiting within seconds.
  • Repeat access: the operation that previously failed, project-folder access or server authentication, completes with no access-denied or logon-failure entry at that time.
  • Cross-client check: repeat on a second client, because each client's local accounts are provisioned separately in a multi-client layout.

If every account now fails where one worked before your changes, the account work is done and the fault is in the project: copy the IM folder aside, delete the original, and recompile with "Software (rebuild all)", the repair sequence reported for corrupted projects, or restore the project from backup.

Questions asked

Is adding the account to local administrators a quicker fix than the SIMATIC HMI group?

No. Administrator rights are a diagnostic shortcut that hides the missing permission instead of fixing it, and they widen what the runtime account can do on a production PC. The documented requirement is group membership plus effective access to the project; grant exactly that. If Runtime only works when launched as an administrator, treat it as a symptom of a broken permission elsewhere, usually a deny entry or a share-level restriction.

Do the operator logins inside WinCC use the same passwords as Windows accounts?

No. WinCC's own user administration is a separate authorization layer that governs runtime operations such as screen commands; Windows governs process, file and network access. Changing an operator password inside the project does not touch the Windows password a service or scheduled task depends on, and the reverse holds too. Match the layer you change to the layer that is failing.

Does restarting the PC replace signing out and back in?

Yes for the access token: a restart builds a fresh session that carries current group membership, and it also clears an orphaned Runtime process that can block a new activation. It does not repair a service or scheduled task still storing the old password, because those credentials live in the component's configuration, not in the session. After restarting, retest, then check services if the failure returns.

Why does the same username work on one client but fail on another?

Because a local account exists only on the machine where it was created: the same username on two clients is two separate identities, each with its own group memberships. Either add the WinCC groups to that account on every machine it signs in on, or move the operator stations to domain accounts so one identity and one group list follow the user across clients and servers.

How many groups does WinCC 7.5 install on the PC?

The count depends on which components and options are installed, and the documentation for your installed version lists each group's role. SIMATIC HMI is the documented baseline for every user, and a viewer-role group, where present, is narrower than full project operation. Instead of counting groups, compare the new account's complete group list against a working account in Computer Management and close the difference.

Keep reading

  • How-to

    How to set up Pro-face historical trend channels in GP-Pro EX

    The channel selector reads undetermined because a historical trend pen can only select channels from a saved sampling group. In GP-Pro EX, open Common Settings, create the Sampling group with your RSLogix 5000 tags, then bind the trend pens to those logged channels. No PLC-side buffer list is needed.

    HMI and touchscreens

  • How-to

    How to Show Only a PLC Connection Alarm in WinCC Flexible

    Yes, but on WinCC flexible 2005 you do it with a dedicated application alarm driven by the connection status, not by filtering the system-alarm stream: the 2005 alarm view selects whole alarm classes, not single messages. Decide first whether the operator must see communication loss or a CPU in STOP, since a stopped PLC can still communicate, and keep the unfiltered system-alarm view on a maintenance screen.

    HMI and touchscreens

  • How-to

    Keep a PanelView Plus Trend Logging After Screen Changes

    A PanelView Plus Trend object only records while its screen is visible. Configure a Data Log model to start at power-up, show it through an XY trend with pen 2 as the X axis, and give the log a bounded record limit so it overwrites the oldest records instead of growing without bound.

    HMI and touchscreens