I've installed Kali from the Windows 10 Store. I've followed the steps in https://www.kali.org/penetration-testing/openvas-vulnerability-scanning/ to install the package but I'm hitting errors and blocks.

After the initial installation, the following messages are displayed:

/usr/sbin/openvasmd

[>] Stopping OpenVAS services
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down

[>] Starting openvassd

(openvassd:5758): lib kb_redis-CRITICAL **: 22:45:29.385: get_redis_ctx: redis connection error: No such file or directory

(openvassd:5758): lib kb_redis-CRITICAL **: 22:45:29.389: redis_new: cannot access redis at '/var/run/redis-openvas/redis-server.sock'

(openvassd:5758): lib kb_redis-CRITICAL **: 22:45:29.390: get_redis_ctx: redis connection error: No such file or directory
[>] Migrating openvassd
[>] Rebuilding openvassd
[>] Stopping openvassd
/usr/bin/openvas-setup: line 30: killall: command not found

/usr/bin/openvas-start: line 20: lsof: command not found
[] Please wait for the OpenVAS services to start.
[]
[] You might need to refresh your browser once it opens.
[]
[*] Web UI (Greenbone Security Assistant): https://127.0.0.1:9392

System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down

[*] Opening Web UI (https://127.0.0.1:9392) in: 5... 4... 3... 2... 1...

After installing lsof and killall, I then looked at trying to solve the redis errors. It looks like the default redis configuration file (/etc/redis/redis.conf) is installed and not configured to meet openvas's needs, namely support for Unix sockets and using the path /var/run/redis-openvas. After fixing that, things look a bit better except for:

[>] Migrating openvassd

(openvasmd:6410): md manage-WARNING **: 00:03:53.397: sql_exec_internal: sqlite3_step failed: locking protocol

(openvasmd:6410): md manage-WARNING **: 00:03:53.399: sqlv: sql_exec_internal failed

(openvasmd:6410): md manage-WARNING **: 00:04:03.417: sql_exec_internal: sqlite3_step failed: locking protocol

(openvasmd:6410): md manage-WARNING **: 00:04:03.419: sqlv: sql_exec_internal failed

(openvasmd:6410): md manage-WARNING **: 00:04:13.433: sql_exec_internal: sqlite3_step failed: locking protocol

(openvasmd:6410): md manage-WARNING **: 00:04:13.435: sqlv: sql_exec_internal failed

[>] Rebuilding openvassd

I'm not sure what is causing these problems or how to fix them.

Even with all of that fixed, it looks like openvas-start is going to have problems because it uses systemctl and, as far as I can tell, WSL doesn't yet support systemd/systemctl.