Built kernel and get ACCESSDENIED error

[awaldfogel]

Followed the instructions to build a kernel for Win10. On loading the new kernel I get

Access is denied.
Error code: Wsl/Service/CreateInstance/CreateVm/E_ACCESSDENIED

Fortunately when I remove the .wslconfig file everything works again. Any suggestions on where to look for the privilege problems? I'm not a Windows ACL expert.

[awaldfogel]

Good news. This problem was just mistyping the name of the new driver...

With the new kernel running the USB devices appear

$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

but the permissions are

0 crw-rw-rw- 1 root root 4, 9 Apr 19 14:08 /dev/tty9
0 crw------- 1 root root 166, 0 Apr 19 14:13 /dev/ttyACM0
0 crw-rw-rw- 1 root root 4, 64 Apr 19 14:08 /dev/ttyS0
0 crw-rw-rw- 1 root root 4, 65 Apr 19 14:08 /dev/ttyS1
0 crw-rw-rw- 1 root root 4, 66 Apr 19 14:08 /dev/ttyS2
0 crw-rw-rw- 1 root root 4, 67 Apr 19 14:08 /dev/ttyS3
0 crw------- 1 root root 188, 0 Apr 19 14:16 /dev/ttyUSB0

and I can't read or write to them

[awaldfogel]

Just so it's all in one place:

I got an Aeotec Z-Wave adapter connected to WSL and visible in docker containers under Win10.

-> built the kernel following the directions and added .wslconfig file as a pointer to it
-> Added /etc/wsl.conf with
[boot]
systemd=true
-> added a udev rule for the device in /etc/udev/rules.d/
-> attached the device from Powershell using the usbipd command
-> lsusb shows the device in WSL and ls -sl /dev/tty* shows the device with "crw-rw----" privileges

TBD is automating the wsl attach. I know this is all obvious to those of you who live in system level world, but not so much for us visitors. Still happy it's all moving in the right direction