reg.exe: command not found

[gitfool]

Background Information:

• Build: 19041.264
• WSL: Ubuntu 20.04
• Version: ubuntu-wsl 1.450; wslu 2.3.6-0ubuntu1

Describe the bug
wsl.conf:

[automount]
enabled = true
mountFsTab = true
options = "metadata,umask=0022,fmask=0011,case=off"
root = /

[interop]
enabled = true
appendWindowsPath = false

[network]
generateHosts = true
generateResolvConf = true

Note: I do not append Windows paths so I often see the error:

reg.exe: command not found

To Reproduce

❯ wslfetch
/usr/bin/wslfetch: line 108: reg.exe: command not found
/usr/bin/wslsys: line 108: reg.exe: command not found
/usr/bin/wslsys: line 108: reg.exe: command not found
/usr/bin/wslsys: line 108: reg.exe: command not found
/usr/bin/wslsys: line 108: reg.exe: command not found
/usr/bin/wslsys: line 108: reg.exe: command not found

                          ./+o+-      Windows 10 Linux Subsystem
                  yyyyy. 'yyyyyy+     sean@hal
              .;//+/////h yyyyyyo     BUILD:    19041
           .++ .:/++++++/-.`sss/`     BRANCH:   vb_release
         .:++o: `\++++++++/:---:/-    RELEASE:  Ubuntu 20.04 LTS
        o:+o+:++. `````'-/ooo+++++\   KERNEL:   Linux 4.19.84-microsoft-standard
       .:+o:+o/.          `+sssooo+\  UPTIME:   0d 4h 15m
  .++/+ +oo+o:`             \sssooo;
 /+++//+: oo+o
 \+/+o+++ o++o               ydddhh+
  .++.o+ +oo+:`             /dddhhh;
       .+.o+oo:.           oddhhhh+
        \+.++o+o` -,,,,.:ohdhhhhh+
         `:o+++  ohhhhhhhhyo++os:
           .o: .syhhhhhhh'.oo++o.
               /osyyyyyyy.oooo+++\
                   ````` +oo+++o:/
                          `oo++'`

❯ wslview http://www.google.com
/usr/bin/wslview: line 108: reg.exe: command not found

❯ xdg-open http://www.google.com
/usr/bin/x-www-browser: line 108: reg.exe: command not found

Expected behavior

Don't show spurious "command not found" errors.

[patrick330602]

Thank you for the report! I am aware of this bug and this bug is tracked here: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1877016

I am closing this issue but will update once the fix is committed to Ubuntu.