Skip to content

Instantly share code, notes, and snippets.

Last active February 18, 2023 16:17
What would you like to do?
WSL Startup Script


  1. Save the file to your computer in a location like C:/tools/wsl-startup/.
  2. Download the WSL Statup.xml and import it into Task Scheduler.
  3. Modify as needed for you personal use.
sudo service dbus start
sudo service cron start
sudo service atd start
sudo service memcached start
sudo service redis-server start
sudo service mysql start
sudo service php7.4-fpm start
sudo service nginx start
<?xml version="1.0" encoding="UTF-16"?>
<Task version="1.4" xmlns="">
<URI>\WSL Startup</URI>
<Principal id="Author">
<Actions Context="Author">
<Arguments>sh /mnt/c/tools/wsl-startup/</Arguments>
Copy link

You should just be able to set them to start on boot with:

sudo update-rc.d rsyslog defaults
sudo update-rc.d dbus defaults
sudo update-rc.d cron defaults
sudo update-rc.d atd defaults
sudo update-rc.d atd defaults
sudo update-rc.d dnsmasq defaults
sudo update-rc.d mysql defaults
sudo update-rc.d php7.2-fpm defaults
sudo update-rc.d nginx default

Copy link

I will test this in the latest wsl but I don't know that it supports modifying the run class.

Copy link

@codepuncher That does appear to work but any time you open additional bash windows it seems to create separate instances of the services in task manager. By having the services started by the script it only creates one instance of the services. Worth testing some more though. Thanks for the tip.

Copy link

kkm000 commented Dec 25, 2018

It is possible to launch WSL services with a Windows Task at logon. That decouples them from bash instances. The only trick, IIRC, is to allow the startup script to run without asking for a password in /etc/sudoers with a NOPASSWD: prefix.

Never tried the task at boot option, but maybe it can also work?

Copy link

hendrep commented Feb 23, 2019

I struggled with my pages sometimes loading and sometimes timing out.
I kept getting upstream timed out (110: Connection timed out) while reading upstream, client:, errors in my valet log.
As per this post, microsoft/WSL#393 (comment),
I added fastcgi_buffering off; to my site's Nginx config under .valet/Nginx.

Seemed to have solved my issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment