DriversRecommendedOutdated drivers can make a good PC feel brokenScan driver issues before chasing fixes manually.Scan NowOctober DealsAmazon USOctober deal check: compare before you payAmazon US: current deals, useful picks and tech finds.Check DealsPC HealthRecommendedCrashes, freezes, slowdowns? Check your PC nowSpot repairable issues before they interrupt work.Check PC×
Skip to content
VGSources
Blog

How to Install a SilverStripe Website on a VPS

Install SilverStripe on a VPS with Composer, a supported PHP 8.1–8.3 runtime, a database, and a web server rooted at public/. Follow the .env, dev/build, rewrite, permissions, and security steps to bring the site online safely.
Length12 min Posted Quest giverVGSources Team
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Install SilverStripe on a VPS by creating a Composer project, pointing the web server at its public/ directory, supplying database credentials in a project-root .env file, and running vendor/bin/sake dev/build. The current Silverstripe CMS 5.2+ requirements call for PHP 8.1–8.3, at least 48M of PHP memory, the required extensions, Composer 2, and a supported database connector. The most common failed installations expose the project root instead of public/, omit URL rewriting, or give the web-server user insufficient access to assets.

What you need before creating the site

A VPS is only the operating system and network environment. SilverStripe (now commonly styled Silverstripe CMS) still needs a correctly matched PHP runtime, extensions, Composer, a database, and a web server. Choose the VPS size from your expected traffic, uploaded-asset volume, scheduled jobs, and database workload; the documented requirements do not publish a universal CPU, RAM, storage, or traffic recommendation.

As an Amazon Associate I earn from qualifying purchases.

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Runtime and package requirements

  • PHP: Silverstripe CMS 5.2 and later currently support PHP 8.1 through 8.3. Keep the command-line PHP used by Composer and sake on the same supported version as PHP-FPM or the Apache PHP module serving requests.
  • PHP memory: Set memory_limit to at least 48M. A larger limit may be appropriate for image processing, imports, or sizeable builds, but the documented minimum is 48M.
  • Extensions: install ctype, dom, fileinfo, hash, intl, mbstring, session, simplexml, tokenizer, and xml.
  • Image processing: provide either gd or imagick.
  • Database connectivity: install the PHP connector matching your selected database.
  • Composer: use Composer 2, which SilverStripe uses to install and update the framework and modules.
  • Web server: Apache or Nginx can serve the site. Apache can use SilverStripe’s supplied rewrite files; Nginx needs equivalent rules written in its server configuration.

Choosing a database

MySQL and MariaDB are Silverstripe’s built-in commercially supported database options. PostgreSQL, SQL Server, and SQLite are third-party or community-supported choices, so confirm module compatibility and support expectations before selecting one for a production site. Create an empty database and a dedicated user before the web installer/build step, and record the host, database name, username, and password for the .env file.

Plan the directory layout

Keep the application in a deployment directory such as /var/www/my-project. The project root contains application code, Composer’s vendor/ directory, and environment configuration. Only /var/www/my-project/public should be reachable as the web root. This boundary is a security requirement, not merely a preferred layout: it keeps app/, configuration, dependencies, and secrets out of direct URL routing.

#1 Best Overall
Sale
Gaoye Blue Light Blocking Glasses
  • BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
  • EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
  • COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
  • LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
  • WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.

Create the SilverStripe project with Composer

  1. Log in to the VPS with an account that can create the deployment directory and install packages. Complete operating-system updates, PHP, the required extensions, your database server or remote database access, and Composer 2 using your distribution’s supported package method.
  2. Move into the parent directory in which the application should live. For example, use cd /var/www, then create or select a deployment directory owned by your deployment account.
  3. Run the official project-creation command from that deployment location:
    composer create-project silverstripe/installer my-project

    The command creates my-project and installs its Composer-managed dependencies.

  4. After Composer finishes, confirm that my-project/public, my-project/vendor, and the application directories exist. Do not move vendor or the configuration files inside public.

Run Composer as the account that owns the deployment files rather than making the entire tree writable by the web server. This keeps later updates and rollback packages predictable while allowing you to grant the runtime only the write access it actually needs.

Configure the web root and URL routing

Apache

Set Apache’s virtual host document root to the project’s public/ directory. The installer supplies public/.htaccess and public/assets/.htaccess; enable Apache’s mod_rewrite and allow the relevant directory overrides so those files can operate. Requests that do not map to a real public file must be rewritten to public/index.php, which boots SilverStripe.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

A typical virtual-host arrangement therefore has a document root equivalent to /var/www/my-project/public, a matching Directory rule that permits the supplied rewrite file, and PHP handling connected to the PHP version you installed. Keep TLS and canonical-host redirects in the virtual host rather than editing application files.

Nginx

Nginx does not read Apache .htaccess files. Set the server’s root to /var/www/my-project/public, pass PHP requests to PHP-FPM, and send non-file requests to /index.php. A minimal routing pattern looks like this:

server {
    root /var/www/my-project/public;

    location ^~ /assets/ {
        sendfile on;
        try_files $uri =404;
    }

    location / {
        try_files $uri /index.php?$query_string;
    }

    location ~ .php$ {
        include fastcgi_params;
        fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
        fastcgi_pass unix:/run/php/php8.3-fpm.sock;
    }
}

The PHP-FPM socket in this example is illustrative: use the socket exposed by your distribution and installed PHP version. Add your real server name, TLS configuration, logging, and security restrictions. The important SilverStripe behaviors are the public root, existing-file handling for assets, and fallback of application routes to index.php.

Rank #2
Windex Gaming Cleaning Wipes, Pre-Moistened Wipes to Instantly Clean all Gaming Gear and Electronics, Resealable Packaging for a Freshness Lock, 25 count (Pack of 1)
  • WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
  • AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
  • PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
  • ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
  • COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed

Asset and protected-file handling

For ordinary public assets, the documented Nginx pattern uses location ^~ /assets/ with sendfile on and try_files $uri =404. That serves an existing file and returns a 404 instead of passing a missing asset through an arbitrary handler. Non-file requests continue to the framework.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Do not allow PHP execution in uploaded-asset directories. Protected assets must not be directly downloadable: deny direct requests and let SilverStripe’s access checks deliver authorized content. For stronger separation, set SS_PROTECTED_ASSETS_PATH="../.protected/" so the protected store is outside public. Review any Nginx or Apache deny rules alongside your asset locations so a broad allow rule cannot override the protection.

Create the environment file and database settings

Create .env in the project root, for example /var/www/my-project/.env. Never place it under public/. It contains connection details and the initial administrator password, so keep it out of version control and restrict its file permissions to the deployment/runtime accounts that require it.

SS_DATABASE_CLASS="MySQLDatabase"
SS_DATABASE_NAME="your_database_name"
SS_DATABASE_SERVER="localhost"
SS_DATABASE_USERNAME="your_database_user"
SS_DATABASE_PASSWORD="use-a-strong-database-password"
SS_DEFAULT_ADMIN_USERNAME="admin"
SS_DEFAULT_ADMIN_PASSWORD="use-a-unique-admin-password"
SS_ENVIRONMENT_TYPE="live"

Replace every example value with the credentials you actually created. If the database is on another host, use that host rather than localhost; ensure the database firewall permits the VPS and that the account is limited to the required database. The class shown is the built-in MySQL connector; use the connector and class appropriate to a supported database you selected.

Protect secrets during deployment

  • Store production secrets in the VPS secret mechanism or deployment environment, then render the root .env file with restrictive permissions.
  • Do not commit the file, paste its password into a public issue, or copy it into a web-accessible directory.
  • Use a long, unique administrator password and database password; do not retain the example strings.
  • When rotating a credential, update the database account and the environment file in a controlled order, then verify a fresh request and a CLI build.

Build the schema and open the administrator

  1. Change to the project root: cd /var/www/my-project.
  2. Run the SilverStripe build task:
    vendor/bin/sake dev/build

    This creates or updates the schema and loads the initial database data using the environment settings.

  3. Watch the command output for PHP extension, permission, or database-authentication errors. Fix those on the server, then rerun the build; do not expose the project root to make an error disappear.
  4. Open the configured domain in a browser. Sign in at /admin with the administrator credentials from .env.

If the build completes but the browser shows a routing error, check the web-server root and rewrite fallback before changing application code. If the administrator form loads but authentication fails, verify the database selected by SS_DATABASE_NAME, the username/password pair, and that the build was run against the same environment file used by the web process.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Rank #3
Sale
LISEN Cell Phone Stand Phone Holder for Desk, Office Decor Gadgets for Men
  • Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
  • Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
  • Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
  • ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
  • Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)

Set permissions without exposing the application

The web-server user needs read access to the public webroot and write access to public/assets/ and SilverStripe’s temporary or cache locations. It should not receive blanket write access to the project root, vendor/, application source, or configuration. Use ownership and group permissions that let deployments update code while the runtime writes only to directories designed for generated or uploaded data.

Directories that may need special treatment

  • public/assets/ for uploaded and generated asset files.
  • Temporary and cache locations used by the framework.
  • .graphql-generated and public/_graphql when the project uses GraphQL.
  • public/_resources/ and other recipe-generated resources produced during a build or deployment.

GraphQL and recipe-generated directories must either be writable during the build or generated in CI and copied into the release package. Avoid solving permission errors with a recursively world-writable project; that also makes an application compromise more damaging.

Apache versus Nginx: which fits your deployment?

Deployment concern Apache Nginx
Rewrite expression Uses the supplied public/.htaccess and public/assets/.htaccess; enable mod_rewrite and directory overrides. Requires explicit server-block rules equivalent to rewriting application routes to public/index.php.
PHP integration Use the PHP handler installed for the virtual host; keep its version aligned with CLI PHP. Pass PHP requests to the matching PHP-FPM socket; the socket path is distribution-specific.
Assets Allow the supplied assets rules to serve public files and prevent execution of uploaded scripts. Use an assets location with try_files $uri =404, then add explicit deny and protected-file rules.
TLS and proxying Configure certificates and proxy headers in the virtual host or front proxy. Configure certificates, proxy headers, and PHP-FPM parameters in the server block or front proxy.
Automation Package the virtual-host template and enabled modules with the server build. Package the server-block template, socket selection, and deny rules with the server build.
Best practical choice Convenient when you want SilverStripe’s quickstart rewrite files with minimal translation. Convenient when your team already standardizes on Nginx and can maintain explicit routing and security rules.

Neither server is inherently required by SilverStripe. Choose the one your team can patch, monitor, reproduce, and troubleshoot consistently; a perfectly routed Nginx configuration is safer than an unfamiliar Apache installation, and vice versa.

Reverse proxies, HTTPS, and host headers

When a load balancer, CDN, or TLS-terminating proxy sits in front of the VPS, preserve the valid Host header and the correct forwarded protocol information. SilverStripe uses the host when constructing links, including password-reset URLs. If the proxy replaces the host with an internal name or fails to communicate HTTPS correctly, users can receive links pointing to the wrong domain or scheme.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  • Choose one canonical public hostname and redirect alternate hostnames at the edge or web server.
  • Pass the original host and protocol headers according to your proxy’s documented behavior.
  • Test generated links from the administrator and password-reset flows rather than checking only the home page.
  • Do not trust arbitrary client-supplied forwarding headers; accept them only from your known proxy path.

Production deployment with CI

A repeatable release process can build the application in continuous integration, then deploy an immutable package to the VPS. Keep Composer-managed modules in vendor/ outside the public boundary, and include or deterministically generate front-end resources mapped into public/_resources/.

Rank #4
Ledagic IC+RGBW USB Powered Led Light Bar with App & Remote Control, 2 Pack
  • Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
  • Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
  • 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
  • Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
  • USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
  1. Pin the project dependencies in the Composer lock file and run the same supported PHP version in CI that the VPS uses.
  2. Install dependencies and run the required build steps in CI, including GraphQL schema generation and recipe-generated files where the project uses them.
  3. Package public/, application code, vendor/, and generated resources without including production secrets.
  4. Transfer the release to a new versioned directory on the VPS, link the root .env, and apply ownership and permissions before switching the web-server release path.
  5. Run vendor/bin/sake dev/build against the production database during the controlled deployment window, following the project’s migration and backup policy.
  6. Switch the web server to the new release, clear or warm caches as appropriate, and retain the previous release for rollback.

The exact CI platform and release tooling are operational choices. The invariant is that generated resources, schema files, and Composer dependencies are either shipped with the release or produced deterministically; relying on untracked files left over from a previous deployment makes a new VPS or rollback fail.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Post-install verification checklist

Perform these checks on the actual VPS after the first deployment and after meaningful server or dependency changes:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  • Home page: the configured domain returns the expected page over HTTPS.
  • Administrator: /admin loads, accepts the new account, and displays the CMS without missing resources.
  • Database: a page request and vendor/bin/sake dev/build use the intended database and credentials.
  • Rewrites: a nested page URL works directly, not only after visiting the home page first.
  • Uploads: an authorized editor can upload an asset and the web server can serve it from public/assets/.
  • Permissions: the runtime can write required caches and assets but cannot modify application source or vendor/.
  • Protected assets: an unauthorized direct request is denied, while an authorized application response still works.
  • Error handling: missing pages return the intended error response and do not reveal stack traces, environment files, or filesystem paths.
  • Proxy behavior: generated absolute links use the public hostname and HTTPS scheme.
  • Logs and backups: web-server, PHP, application, and database logs are available, and the database plus uploaded assets are included in the backup plan.

Diagnose the failures you are most likely to see

“Composer requires a different PHP version”

Check both php -v in the shell and the PHP-FPM or Apache runtime reported by a controlled diagnostic. Install a supported PHP 8.1–8.3 version and its extensions, then rerun Composer. A server can have multiple PHP versions, so changing only the CLI binary may leave the web process incompatible.

Missing class or extension errors

Install every required extension, including less-obvious entries such as intl, dom, simplexml, and mbstring. Restart the PHP service after package changes and verify the module is enabled for the same SAPI that serves requests. Confirm that either gd or imagick is available before testing image uploads.

404s on every friendly URL

Confirm the document root ends in /public. On Apache, enable mod_rewrite and permit the supplied .htaccess. On Nginx, verify that the try_files fallback reaches /index.php and that PHP-FPM receives the correct script filename. Test a real static file and a nested CMS page separately to identify whether the problem is asset routing or framework routing.

Best Value
Sale
HUANUO FlowLift™ Dual Monitor Stand, Fully Adjustable Gaming Monitor Desk Mount for 13–32″ Computer Screens, Full Motion VESA 75x75/100x100 with C-Clamp & Grommet Base, Each Arm Holds 4.4 to 19.8 lbs
  • Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
  • Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
  • Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
  • Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
  • Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.

Assets cannot be uploaded or generated

Check ownership and write permissions on public/assets/ and the temporary/cache directories. Ensure the filesystem is not full and that a security policy has not blocked the PHP process. Do not make the whole project writable; grant write access only to the directories SilverStripe needs.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Database connection or build errors

Read the values in the project-root .env, confirm the database server is reachable from the VPS, and verify the account’s permissions. Ensure the CLI build and web process read the same environment file. After correcting credentials or connectivity, rerun vendor/bin/sake dev/build.

Protected files are publicly downloadable

Inspect the web-server locations for an allow rule that overrides your deny rule. Uploaded assets must not execute as PHP, and protected assets must not be served as ordinary static files. Consider SS_PROTECTED_ASSETS_PATH="../.protected/" to place the protected store outside public/, then retest both an unauthorized URL and an authorized application response.

Password-reset links use the wrong domain

Check the public Host and forwarded protocol headers through every reverse proxy or CDN. SilverStripe uses the host while constructing links, so an internal proxy hostname or incorrect scheme can produce unusable URLs even when page routing itself works.

Security and maintenance after launch

  • Patch the operating system, PHP, web server, database, Silverstripe core, and Composer modules on a planned schedule.
  • Review Composer changes before deployment and keep a tested rollback release.
  • Keep .env, app/, configuration, and vendor/ outside the public web root.
  • Back up the database and public/assets/ together; restoring only code does not restore uploaded content.
  • Monitor disk space, PHP-FPM or Apache errors, database availability, failed administrator logins, and unexpected writes under public directories.
  • Re-run the verification checklist after changing PHP versions, web-server rules, proxy settings, or deployment automation.

With the public boundary, rewrite rules, environment file, permissions, and build command all aligned, a VPS installation is a conventional Composer deployment rather than a special hosting variant. The same separation also gives you a safer path for upgrades, CI releases, and rollback.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

Leave a Reply

Your email address will not be published. Required fields are marked *

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

More quests from Patch Notes

  1. How to Set Up a RedM (RDR2) Server in 2026: License Key, txAdmin and server.cfg, Step by StepBlog11min
  2. Best RedM (RDR2) Server Hosting in 2026: Comparing Four Hosts on Slots, Memory and PriceBlog10min
  3. How to Host a Mindustry Server in 2026: server-release.jar, Port 6567 and the Commands That MatterBlog7min
Recommended PC Tool
Recommended PC Tool
Crashes, No Sound, or Screen Glitches?Free driver scan
Windows Errors? Fix Them Before They SpreadFree repair scan

Two free Windows tools

One Free Minute Could Fix That PC

Before you go - each of these free tools takes about a minute and tackles what quietly slows a Windows PC down.

Special offer. View Outbyte info, uninstall instructions, EULA, and Privacy Policy.