Help / Saver

K-Shield Saver

The CHF 99 clean-up kit for your domain: diagnosis, backup, repair and an intervention report.

Documentation revised on 7 September 2026 · Screenshots show the English interfaces

Have your Saver key and FTP/SFTP access ready. Keep an independent backup if you have one. Saver does not include a firewall or daily monitoring.

1. Order and receive your key

Choose Saver in the order form, enter your domain and email, then the validation code. The displayed reference confirms the order has been recorded, not paid.

Your key is issued after payment has been recorded and is delivered by email. It is tied to the domain and edition. Check its validity date in your customer account.

2. Install the kit

Upload clean.php and kshield.zip together next to wp-config.php, then open https://your-site.ch/clean.php. Leave the archive intact.

Resolve failed environment checks, enter your Saver key and recovery email, then start installation. An old KSL1 token is not a KSL2 key.

Saver — environment checks and licence entry.
Saver — environment checks and licence entry.

3. Keep your administrator access

When installation finishes, store the assistant address and admin token in a password manager. The token opens the assistant; it is not your licence key.

Open the assistant and sign in. If a warning says a token recovery file remains, follow the offered procedure after saving your access details.

4. Establish the diagnosis

In Assessment, run the initial assessment before repairing. The assistant keeps the initial findings to compare with the final result.

Check the backups and read the proposals. Actions that change the site need attention and, depending on risk, confirmation.

5. Follow the repair steps

Follow the assistant in this order. Examine each error before continuing.

  1. WordPress core: check and restore the official core.
  2. Suspicious files: review files and quarantine those that need to be set aside.
  3. Plugins & themes: check plugins and the theme; commercial products may require an archive from their vendor.
  4. Database: review anomalies and proposed fixes.
  5. Back online: check rendering and sign-in before returning the site to service.
  6. Corrective actions: read what was done and what remains, then save the intervention bundle.

6. Check the result

Open important pages and the WordPress administration yourself. Check forms and functions your visitors use. Address any open points in the report before considering the repair complete.

Quarantine remains available from Quarantine. Do not restore a file just to remove an error: review its purpose and detection reason. Keep the report and a backup off the server.

Troubleshooting

My key is rejected.

Check the Saver edition, domain and validity date. Copy the full key without publishing it. Your customer account lets you review or reset the licence.

A repair fails.

Keep the error and report. Avoid repeated actions at random. Use guided restoration after checking which backup to restore.

WordPress no longer opens.

The assistant may remain available at its own address. Review diagnostics and quarantined files, then follow the recovery proposals.

Contact · Customer account