# Train-wreck trying to switch to Hyper-V, back to WSL 2, all new sites 403 forbidden

**URL:** <https://community.kinsta.com/t/train-wreck-trying-to-switch-to-hyper-v-back-to-wsl-2-all-new-sites-403-forbidden/1686>\
**Category:** Application Support\
**Created:** [August 25, 2022, 11:54pm UTC](https://community.kinsta.com/t/train-wreck-trying-to-switch-to-hyper-v-back-to-wsl-2-all-new-sites-403-forbidden/1686 "2022-08-25T23:54:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chevas](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/chevas/32/1384_2.png) [@Chevas](https://community.kinsta.com/u/Chevas)\
**Post date:** [August 25, 2022, 11:54pm UTC](https://community.kinsta.com/t/train-wreck-trying-to-switch-to-hyper-v-back-to-wsl-2-all-new-sites-403-forbidden/1686/1 "2022-08-25T23:54:34Z")

</div>

I recently tried to switch Docker to Hyper-V mode instead of WSL 2 because WSL 2 is super slow. I understood that anything currently in DevKinsta would be inaccessible if I did that, but anything I created under Hyper-V mode would work thereafter.

Hyper-V mode created a lot of problems with permissions. I am not as technical as most here, but it was such a pain, I decided to delete all my sites, uninstall DevKinsta, uninstall Docker, reboot, and reinstall everything from scratch (Docker in WSL 2 mode).

Now that I’ve done that, every new site in DevKinsta throws a 403 forbidden nginx error when I try to load the [site-name].local in a browser.

This is with a fresh install. As an aside, it would be nice if DevKinsta had a “clean uninstall” that would remove everything it could as if your machine never had it installed in the first place.

---

<div class="post-metadata">

**Author:** ![Kevin](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/kevin/32/808_2.png) [@Kevin](https://community.kinsta.com/u/Kevin)\
**Post date:** [August 26, 2022, 5:47pm UTC](https://community.kinsta.com/t/train-wreck-trying-to-switch-to-hyper-v-back-to-wsl-2-all-new-sites-403-forbidden/1686/2 "2022-08-26T17:47:12Z")

</div>

Hi @Chevas, welcome to DevKinsta and thanks for reaching out.  
So are the 403 errors under WSL2 the same as what you were getting with Hyper-V? I personally find Hyper-V easier to set up but I’ve also never had this issue with switching back and forth.

As a note, is seems like if you just uninstall Docker, it doesn’t necessarily remove past images/containers. I recommend deleting your sites then either Clean/Purge data or reset Docker to factory defaults

 ![image](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/5/5a7fbeec8992bfca8b88ebdae23edcd5746cee4d.png)

That will guarantee that DevKinsta recreates everything. I agree about needing a full uninstall option. For now the best we have are these instructions: [Uninstall DevKinsta](https://kinsta.com/knowledgebase/devkinsta/uninstall-devkinsta/#clean-up-after-removal)

Please let me know if nothing solves this for you and I’ll continue to assist you.

---

<div class="post-metadata">

**Author:** ![Chevas](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/chevas/32/1384_2.png) [@Chevas](https://community.kinsta.com/u/Chevas)\
**Post date:** [October 29, 2022, 5:54pm UTC](https://community.kinsta.com/t/train-wreck-trying-to-switch-to-hyper-v-back-to-wsl-2-all-new-sites-403-forbidden/1686/3 "2022-10-29T17:54:54Z")

</div>

By the way, I finally got around to following this guidance and I was able to resolve the 403s. Recap:

I first did a data purge in Docker  
Then I uninstalled Docker  
Then I uninstalled DevKinsta  
Then I followed the steps on the “Uninstall DevKinsta” link you provided which mostly involved deleting folders (Windows)

I then rebooted.

For the following, when given the choice, I always chose “only install for me” vs “all users”.

Then I reinstalled Docker in Hyper-V mode.  
Then I installed the latest version of DevKinsta (which still detected registry entries), but so far so good.