• Hey Guest, we're evolving the future of TeaSpeak.
    You're invited to join the discussion here!

Server [Unofficial] Installation on Windows via WSL

d0nar

New member
Hi all,

this is a quick overview, how you can run Teaspeak on Windows 10 and Windows Server 2019 (and Windows Server 1709).

IT IS NO NATIVE EXECUTION, IT WORKS WITH THE LINUX SUBSYSTEM FOR WINDOWS FROM MICROSOFT.

for advanced/experts/server1709/nogui users, look at the end of the post to PART 42..

for PART 1 and PART 2 i have hacked an Script together
https://github.com/d0narnbl1tz/install-WSL-and-ubuntu/blob/master/wsl_ubuntu.ps1
it should work for win10 and Server 2019, for server 1709 i have found no info, about the Caption String, tested on Windows Server 2019

PART 1
INSTALLING THE WINDOWS SUBSYSTEM FOR LINUX

At first, we need access to an administrative PowerShell.
If you don´t know, how to start the shell, press the windows key (assuming you use an GUI-Installation of Windows)
scroll down to the entry "Windows PowerShell", click once on it to see the sub-entrys.
Now, assuming you are not using the mouse on the left side like me ^^
Perform an right-click, to get the menue where "Run as Administrator" or so is, use the run as admin and you get the administrative PowerShell.

Inside the PowerShell you copy paste following:

Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux

In the picture below, you can see how it should look inside the PowerShell..

1532447060290.png

Now press enter and wait until the subsystem is installed, this might take some time, and eventually might require an reboot (on my system i didn´t need one, but it can happen)


PART 2
INSTALING LINUX ONTO THE WINDOWS SUBSYSTEM FOR LINUX

After the installation, you need an linux distribution for the subsystem,
i recommend you to use the ubuntu version as i will write, how i did it with ubuntu (would prefer debian ofc, but no appx download for server 2019 :/ )

we will now install Ubuntu, doing this is simple:
download this and rename the extension from .appx to .zip (or open it with 7-zip/unrar/etc)
extract the content of the folder into an new folder called ubuntu wherever you want, i recommend using

C:/ubuntu

for simplicity.

Now you navigate to your new folder and look into his content, there is an:
ubuntu.exe

which you will now start.

after some beers the installation might be finished...
yeah you will now be asked for an username and an password

PLEASE, REMEMBER THEM BOTH, MAYBE WRITE THEM DOWN, AS YOU WILL NEED THEM

so you now have an ubuntu console ... ^^


PART 3
INSTALLING TEASPEAK

as I am lazy, i send you now over to:
Sporesirius great TeaSpeak installer
or if you want it harder:
h00n1g4n´s Setting up from 0

PART 4
ENABLE AUTOSTART IN LINUX

for this, just use the tutorials around here


PART 5
ENABLE AUTOSTART OF THE UBUNTU

refer to
this neat tutorial on github

PART 6
FIREWALL

D onot forget to open the teaspeak ports in the windows firewall



PART 42
EXPERT MODE

refer to
for win10
for win server (2019 or 1709)
setup enviroment as described in the links

and then
goto PART 3





THE END,

Sry for the grammar and typos ^^
Some parts (4 and 5) are not tested by me, but should work :D




EDIT: added part 6
 
Last edited:

Bluscream

Well-known member
i get

Installing, this may take a few minutes...
It appears this distro's installation has become corrupted.
Please try uninstalling and reinstalling the app.
Installation Failed!
Error: 0x800700b7
Press any key to continue...
 

d0nar

New member
i get

Installing, this may take a few minutes...
It appears this distro's installation has become corrupted.
Please try uninstalling and reinstalling the app.
Installation Failed!
Error: 0x800700b7
Press any key to continue...
Hi, at first you can try reboot and try to enable WSL again
also, you could use my script i hacked together, when i saw your post ;)
hope it works for you..

other troubleshooting would be
try to run
sc query LxssManager
sc stop LxssManager
sc start LxssManager
via administrative powershell, as mentioned as workaround on https://github.com/Microsoft/WSL/issues/3352