# Installation notes for Discourse on Bash for Windows

**URL:** <https://meta.discourse.org/t/installation-notes-for-discourse-on-bash-for-windows/48141>\
**Category:** Development\
**Created:** [August 3, 2016, 3:10am UTC](https://meta.discourse.org/t/installation-notes-for-discourse-on-bash-for-windows/48141 "2016-08-03T03:10:48Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [April 13, 2017, 5:08pm UTC](https://meta.discourse.org/t/installation-notes-for-discourse-on-bash-for-windows/48141/3 "2017-04-13T17:08:46Z")

</div>

I just upgraded to creators update, with latest WSL.

**The good news**

Postgres can now be installed inside WSL and run as a service, no need to run it on the host 🎊 . Overall everything is much more polished, you can see tasks that are running in WSL in the task manager, it feels like one cohesive unit.

**The not so good news**

Filesystem access is still terrible, in fact this round of testing on my new computer (that uses bitlocker) gives me **35 seconds** to run `bin/rake routes`, the same command takes **3.2** seconds on the **same** computer under vmware.

My recommendation here is to keep observing, but still use a VM for now for any real dev work needed.

---

_[View the full topic](https://meta.discourse.org/t/installation-notes-for-discourse-on-bash-for-windows/48141)._