Troubleshooting
Recovering access to a password-protected HMI panel without a backup
Short answer
With no project and no backup, the panel on the machine is the only working copy, and the password cannot be removed non-destructively: the documented change path is a project transfer that overwrites passwords, and any reset that restores access deletes the application. Preserve the running panel, recover the project from the machine builder or integrator, and involve vendor support with the full order number and serial before anything destructive.
On this page
Your TP900 is not faulty, and securemode.exe is not an infection: it is the enforcement that appears when password protection was configured for the panel's Control Panel, which on Comfort panels automatically enables SecureMode. With no project and no backup, the panel in the machine is the only working copy of the application, and every documented way to clear that password either requires the engineering project or erases the application you are trying to save. The committed path: identify which boundary is asking, preserve the running panel untouched, and get the recovery from the machine builder, the integrator or Siemens support, quoting the complete order number and serial number. Nothing gets reset until a restore path or an approved rebuild exists.
Which password is asking #
The file name securemode.exe does not tell you which credential applies; the prompt's location does. Capture its exact text and the sequence that produces it before anything else, because that one fact routes the whole recovery.
- A prompt in the panel's Control Panel or transfer dialog is the device password. On Comfort panels, protecting the Control Panel with a password automatically enables SecureMode, so this is the classic locked-backup case: the credential was set in the engineering project and is enforced by SecureMode on the device.
- A login screen inside the running application belongs to the project's user management, which is also project data.
- A password demanded by the transfer itself on a Basic panel can be the transport password, and that boundary has a documented on-device reset: the "Reset password" action generates a new certificate without a password and does not touch the project. If that is your prompt, use it and take the backup.
Decision: a Basic-panel transport password gets cleared today with the documented reset; a Comfort Control Panel password has no on-device removal, and you continue below.
Why there is no non-destructive removal #
The password lives in the project, not in a service file on the device. The documented way to change it is to set new passwords in the TIA Portal project and run a project transfer to the HMI with the option to overwrite passwords. Without the project, that path is closed.
The documented resets are deliberately destructive. For a Basic panel with transfer locked, the documented restore is a factory reset of the HMI runtime, after which the project must be transferred again from TIA Portal. The PLC side shows the same design: the documented recovery for a lost password on a password-protected S7 CPU is an empty transfer card that deletes the protected program. One documented support case even ties changing a password or username field to a factory reset to clear it. These protections are built so that recovering access costs the protected content.
Two consequences follow. Tools that claim to read a password hash or strip protection from the compiled runtime are not a recovery path: they sit outside the vendor's procedure, and they put the only working copy at risk. And even a successful backup would not have given you an editable project — the difference is covered in why an uploaded HMI copy is not an editable project — but in this case even that lesser artifact is blocked.
Preserve the only working copy first #
Treat the installed panel as the master copy until a second copy exists and has been validated:
- Photograph the nameplate and transcribe the complete order number and serial number; "TP900" alone identifies nothing.
- Record everything reachable without changing it: image and version screens, communications settings, station name and address.
- Inventory the application by observation: number of screens, alarm behavior, recipes and setpoints the operators rely on.
- Search controlled records — commissioning handover, maintenance archives, builder deliveries, approved engineering laptops — and work through how to recover an HMI program when the source file is lost before concluding the source is gone.
- Run no exploratory resets, operating-system updates, storage-card swaps or anything that raises a transfer dialog.
While this proceeds, the machine keeps running: SecureMode restricts the Control Panel, not the runtime.
The recovery request that actually works #
Route the request to whoever owns the application before the vendor support line. The machine builder or integrator may still hold the engineering project, a commissioned backup or a credential record, and your commissioning or service agreement may obligate them to deliver it — those clauses settle who authorizes what.
Then open the support case with a complete package: order number, serial number, image version, the exact prompt text with a photo, the failed transfer sequence, and a plain statement that no project or backup exists. Ask one precise question: does the documented procedure for this exact device retain the application, settings and recipes? Support identifies the procedure that applies to your hardware; the credentials and the project ownership stay with whoever built the application.
What each documented operation costs #
| Operation | Documented effect | Prerequisite | Decision |
|---|---|---|---|
| Transport-password reset (Basic panels) | New certificate generated without a password; project untouched | Access to the transfer settings | Use it if that is the boundary |
| Project transfer with overwrite passwords | Passwords replaced by the project's values; application replaced by the project's version | The TIA project for this machine | The clean fix once the project is back |
| Runtime factory reset or OS recovery | Factory state restored; runtime application, recipes and settings deleted | A validated restore or an approved rebuild plan | Last step of a planned job, never a first attempt |
| Rebuild on replacement hardware | New application written from observed operation | Approved scope and commissioning plan | The committed endpoint when nothing is recoverable |
Reset entry points described for these panels include a recessed Service/Reset button behind the right side of the front bezel, pressed with a 2.5 mm pin while power is applied. Whatever the entry point, confirm its documented effect for your exact order number first, and put the machine in a safe state before any reset or transfer attempt: a panel that comes back empty or parked in transfer mode is not an operator interface.
One maintenance window or nine and a half days #
Illustrative planning numbers for a mid-size application, not measured data: 18 screens, 96 PLC tags, 4 alarm classes, one machine.
The documented recovery route costs half a day to assemble the support package plus one maintenance window of 4 h for the authorized procedure and its verification. The machine has its HMI back the same shift.
Reset-first with no project means rebuilding: 18 screens at 3 h per screen is 54 h; 96 tags at 10 tags per hour is 9.6 h of retagging; alarms and recipes take 4 h; commissioning takes 8 h. Total 54 + 9.6 + 4 + 8 = 75.6 h, which at 8 h per day is 75.6 ÷ 8 = 9.45 — about nine and a half days of HMI downtime, and 75.6 ÷ 4 = 18.9, roughly nineteen times the maintenance-window route, before counting behavior nobody documented.
Decision: with that arithmetic in front of you, a reset is never trialed on the only working panel.
When nothing is recoverable #
If every record search and every support answer comes back empty, commit to the rebuild and stop treating the password as the problem: the panel has reached the end of its recoverable life. Document the running behavior while it still runs, then follow the route in replacing an old HMI when no project files exist. The rebuilt application can target industrial panel PCs as a PC-based station instead of a like-for-like terminal.
Once any second copy exists — recovered project or commissioned backup — the emergency is over: set new passwords in the project and transfer with the overwrite option, and the next lockout becomes a routine change.
Questions asked
Is securemode.exe a virus or a sign the panel is failing?
No. On Comfort panels it is the enforcement that comes with password protection: configuring a Control Panel password enables SecureMode automatically. It is protection working as designed, and deleting or replacing the file is not a recovery path, because access is governed by credentials set in the engineering project.
Can Siemens support simply read the password out of the panel?
No. Support can identify the documented procedure that applies to your exact order number and serial number, but passwords configured in the project are not read back out of the device, and ownership of the application usually stays with the integrator who built it. That is why a complete, specific support package matters more than an urgent phone call.
Will a factory reset at least give me a clean panel to work with?
Clean means empty. The reset that restores access deletes the runtime application along with recipes and settings, and recovery then requires a project transfer from TIA Portal. With no project you are trading a locked backup for a blank panel, so a reset belongs at the end of a planned rebuild, never at the start of a recovery attempt.
The machine builder no longer exists. What now?
Search the purchase and commissioning records anyway: handover media, service reports and old engineering laptops often still hold the project or a commissioned backup, and service obligations sometimes passed to a successor company. If nothing surfaces, commit to the rebuild and photograph every screen and setpoint while the panel still runs.
What happens if the panel fails before we recover anything?
Then the application fails with it. With no project, no backup and a dead runtime there is nothing left to read, and the rebuild starts from whatever you recorded while it ran. That is the entire argument for documenting the running application now rather than after a failed experiment.