Linux subsystem w Windows 10, połączenie SSH

Cześć, nie mogę sobie poradzić z utworzeniem połączenia SSH, potrzebuję je do Visual Studio 2015, dzięki czemu będę mógł debugować wszystkie wersje programu na 1 maszynie. Problem w tym że cały czas mam "Permission denied", nie wiem co mam dodatkowo skonfigurować, poza tym gdy wpiszę komendę
"sudo service ssh start" mam:
* Starting OpenBSD Secure Shell server sshd                                                 [ OK ]

natomiast gdy sprawdzam "sudo service ssh status" mam:
* sshd is not running

przy próbie zalogowania się dla testu przez putty mam komunikat z błędem "Permission denied"

wklejam zawartość mojego pliku sshd_config:
---------------------------------------------------------------------------------------------------
# Package generated configuration file
# See the sshd_config(5) manpage for details

# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/protocols sshd will bind to
#ListenAddress ::
ListenAddress 0.0.0.0
#ListenAddress 192.168.1.18
Protocol 2
# HostKeys for protocol version 2
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key
HostKey /etc/ssh/ssh_host_ecdsa_key
HostKey /etc/ssh/ssh_host_ed25519_key
#Privilege Separation is turned on for security
UsePrivilegeSeparation no

# Lifetime and size of ephemeral version 1 server key
KeyRegenerationInterval 3600
ServerKeyBits 1024

# Logging
SyslogFacility AUTH
LogLevel INFO

# Authentication:
LoginGraceTime 120
PermitRootLogin without-password
StrictModes yes

RSAAuthentication yes
PubkeyAuthentication yes
#AuthorizedKeysFile     %h/.ssh/authorized_keys

# Don't read the user's ~/.rhosts and ~/.shosts files
IgnoreRhosts yes
# For this to work you will also need host keys in /etc/ssh_known_hosts
RhostsRSAAuthentication no
# similar for protocol version 2
HostbasedAuthentication no
# Uncomment if you don't trust ~/.ssh/known_hosts for RhostsRSAAuthentication
#IgnoreUserKnownHosts yes

# To enable empty passwords, change to yes (NOT RECOMMENDED)
PermitEmptyPasswords no

# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
ChallengeResponseAuthentication no

# Change to no to disable tunnelled clear text passwords
PasswordAuthentication yes

# Kerberos options
#KerberosAuthentication no
#KerberosGetAFSToken no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes

X11Forwarding yes
X11DisplayOffset 10
PrintMotd no
PrintLastLog yes
TCPKeepAlive yes
#UseLogin no

#MaxStartups 10:30:60
#Banner /etc/issue.net

# Allow client to pass locale environment variables
AcceptEnv LANG LC_*

Subsystem sftp /usr/lib/openssh/sftp-server

# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication.  Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
UsePAM yes
PermitRootLogin yes
AllowUsers Maciek
---------------------------------------------------------------------------------------------------

nie wiem co to za wynalazek ale spróbuj normalnie odpalić demona bez service. u mnie na ubuntu robi się to tak
 A jeśli to jest windows olał bym sudo. Bo to służy uzyskaniu uprawnień roota na Linux. Na windowsie i tak wszystkie wirusy mają prawa administratora :P
PS. może jest jakiś problem że ci się proces sshd zamyka po stracie. Coś powinno być w logach.
logi zwykle są w katalogu /var/log