skip to Main Content
New DesktopServer Version 3.2.3 Released

New DesktopServer Version 3.2.3 Released

Note: Existing users should use our update instructions below to preserve existing sites.

A new version of DesktopServer (version 3.2.3) is now available in our downloads section. This version includes important updates to both our free DesktopServer Limited and premium member access DesktopServer version. Unlimited virtual servers, unlimited aliases, and WordPress Multisite are only supported in the premium access full version.

Update Instructions

  1. First, you must stop web and database services using DesktopServer’s first option “Stop or restart the web and database services”, followed by “Stop the web and database services”. Once database and web services have stopped, be sure to close the DesktopServer application.
  2. Download the ZIP archive for your specific platform (Windows or Macintosh) with the ‘update only’ option from your account.
  3. Replace the main application program inside your current server folder:
    1. For Macintosh computers, replace the “” file inside your Applications ? XAMPP folder.
      1. Only delete your existing application by dragging it to the trashcan.
      2. Move the new application to your existing Applications ? XAMPP folder.
    2. For Windows computers, replace the “DesktopServer.exe” file inside your c:\xampplite folder.

Change Log

This version (3.2.3) includes the following updates:

  • New “Versions” option when setting up a new WordPress site. You may now add beta, and additional versions of WordPress.
  • New “blueprints” folder for housing WordPress versions. Place additional WordPress versions with plugins or other content in a named folder under the blueprints folder (inside XAMPP/xampplite).
  • Additional fixes for Lion 10.7.2 compatibility.


  • Users on Macintosh may experience an “Unable to upgrade wordpress folder bluepreints\WordPress 3.2.1, upgrade failed”. Upon restarting the message goes away. The false positive is a permissions problem that is self-correcting during the upgrade. The upgrade should succeed on subsequent restart and can safely be ignored.