How to Install WordPress on Windows Hosting (Plesk)

The steps below use Plesk, the panel Windows hosting plans ship with, and flag every point where a Windows stack differs from the cPanel route most WordPress guides assume. If your site sits on Linux shared hosting, none of the web.config work in the middle of the page applies to you.

Does WordPress belong on Windows?

Yes. WordPress runs unchanged on Windows hosting: IIS serves PHP through FastCGI, MySQL holds the content, and every plugin, theme and update path behaves exactly as on a Linux server. Nothing inside WordPress requires Unix.

Windows hosting earns its keep in three situations:

• You also run ASP.NET apps or MS SQL databases — one Windows server hosts them beside WordPress.
• Administration is already Windows-native — your team maintains Plesk and Windows Server daily.
• You want the Plesk WordPress Toolkit — updates, staging and security scans in one dashboard.

For a plain content site with no Microsoft dependencies, the WordPress hosting route on Linux stays the default. Choose Windows for the reasons above, not by habit.

Installing via Plesk

Plesk installs WordPress from its own catalog — no FTP client, no manual database setup. Before you start, make sure the domain is added to the subscription and, if you plan to install below the root, that the target folder exists and is empty. The Toolkit ships with Plesk hosting plans.

1. Open your subscription in Plesk and go to Applications, or open the WordPress Toolkit directly.
2. Click Install next to WordPress and pick the domain plus the target directory — leave it empty for the site root.
3. Set the admin username, password and email. These are your wp-admin credentials, separate from the Plesk login.
4. Let Plesk provision the MySQL database; it writes the connection details into wp-config.php for you.
5. When the installer finishes, the site appears in the Toolkit with its version and update status listed.

It worked when the domain loads over HTTPS with the default theme showing, and /wp-admin/ accepts the credentials you set. If the installer stalls, the Toolkit entry shows the failure reason rather than leaving you with a browser error page.

What to check right after install

Three checks before you touch the theme. Load the homepage over HTTPS — a certificate warning means the SSL binding is not active yet. Log in at /wp-admin/ and delete the sample post and page plus the unused default themes, which are unpatched files otherwise. Then set your permalink structure, because it needs the rewrite rule the next section covers.

Permalinks and the web.config URL Rewrite

IIS has no .htaccess. Pretty permalinks such as /post-name/ resolve only when the IIS URL Rewrite module is installed and a web.config file in the site root forwards unmatched requests to index.php. Plesk on Windows ships the module, and provisioning normally drops the standard WordPress rewrite block in for you.

Test it: set Settings → Permalinks to Post name, open a post, and confirm the pretty URL loads without a 404. A 500 error at this point usually means a malformed web.config rather than a WordPress fault — restore the last known-good rule or ask support to place the standard block.

Plugin compatibility notes

Pure-PHP plugins — the large majority of the directory — run identically on IIS. The failures are the minority that shell out to Unix utilities, such as image-processing wrappers around Linux binaries, and cache plugins that write .htaccess directives, which IIS never reads. Check a plugin's requirements before installing it on a Windows plan.

Update plugins after a backup, one at a time when the site is a shop. If a white screen follows an update, rename that plugin's folder in the Plesk File Manager to disable it instantly, reload the site, then report the conflict.

Performance and update reality

Published benchmarks historically give Linux a small edge because PHP performance work lands on it first. In practice a Windows plan serves content sites and WooCommerce stores at normal speed when the PHP version is current, caching is on and the database responds fast — the same three levers that decide speed on Linux.

Keep the Toolkit's update runs enabled so core and plugin updates apply the day they ship. On a day-to-day basis that matters more to speed and security than the operating system does.

When Windows makes sense

• ASP.NET apps or MS SQL databases must live on the same server as WordPress.
• The admin team is Windows-native and manages Plesk and Windows Server already.
• Toolkit staging and cloning is the workflow you want on a shared plan.

Everything else belongs on the Linux default. Moving an existing WordPress site between stacks is a migration service job, not a manual reinstall — site files, database and URLs travel together, subject to terms and approval.