Can't access WSL P9 Network Linux Filesystem Share

Your Windows build number:  (Type ver at a Windows Command Prompt)
Microsoft Windows [Version 10.0.19041.264]

What you're doing and what's happening:  (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)

Updated Windows to Version 2004
First time activation of WSL and Virtual Machine Platform
Download an install WSL2 Linux Kernel update from https://docs.microsoft.com/en-us/windows/wsl/wsl2-kernel
wsl --set-default-version 2
Install Ubuntu WSL Distro from Microsoft Store
Launch Ubuntu WSL
Complete user setup
Try to access \\wsl$\Ubuntu\
Receive error alert  Attempt to access invalid address

What's wrong / what should be happening instead:

Should be able to access files inside the Linux VHD

Additional information
The Ubuntu share shows in Explorer, but trying to access it fails.
No /etc/wsl.conf file in use.
dir \\wsl$ or   dir \\wsl$\Ubuntu in PowerShell fail with Cannot find path ...
apt-get update && apt-get upgrade were ran including WSL restarts

dmesg
[    0.000000] Linux version 4.19.104-microsoft-standard (oe-user@oe-host) (gcc version 8.2.0 (GCC)) #1 SMP Wed Feb 19 06:37:35 UTC 2020
[    0.000000] Command line: initrd=\initrd.img panic=-1 pty.legacy_count=0 nr_cpus=12
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
[    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000e0fff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000001fffff] ACPI data
[    0.000000] BIOS-e820: [mem 0x0000000000200000-0x00000000f7ffffff] usable
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x00000003387fffff] usable
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] DMI not present or invalid.
[    0.000000] Hypervisor detected: Microsoft Hyper-V
[    0.000000] Hyper-V: features 0xae7f, hints 0x2c2c
[    0.000000] Hyper-V Host Build:19041-10.0-0-0.264
[    0.000000] Hyper-V: LAPIC Timer Frequency: 0x1e8480
[    0.000000] tsc: Marking TSC unstable due to running on Hyper-V
[    0.000000] Hyper-V: Using hypercall for remote TLB flush
[    0.000000] tsc: Detected 3200.151 MHz processor
[    0.000005] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.000006] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.000008] last_pfn = 0x338800 max_arch_pfn = 0x400000000
[    0.000037] MTRR default type: uncachable
[    0.000038] MTRR fixed ranges disabled:
[    0.000038]   00000-FFFFF uncachable
[    0.000039] MTRR variable ranges disabled:
[    0.000039]   0 disabled
[    0.000040]   1 disabled
[    0.000040]   2 disabled
[    0.000040]   3 disabled
[    0.000040]   4 disabled
[    0.000041]   5 disabled
[    0.000041]   6 disabled
[    0.000041]   7 disabled
[    0.000041] Disabled
[    0.000042] x86/PAT: MTRRs disabled, skipping PAT initialization too.
[    0.000050] CPU MTRRs all blank - virtualized system.
[    0.000052] x86/PAT: Configuration [0-7]: WB  WT  UC- UC  WB  WT  UC- UC
[    0.000053] last_pfn = 0xf8000 max_arch_pfn = 0x400000000
[    0.000066] Using GB pages for direct mapping
[    0.000068] BRK [0x02e00000, 0x02e00fff] PGTABLE
[    0.000068] BRK [0x02e01000, 0x02e01fff] PGTABLE
[    0.000069] BRK [0x02e02000, 0x02e02fff] PGTABLE
[    0.000093] BRK [0x02e03000, 0x02e03fff] PGTABLE
[    0.000426] RAMDISK: [mem 0x02e35000-0x02e44fff]
[    0.000430] ACPI: Early table checksum verification disabled
[    0.000439] ACPI: RSDP 0x00000000000E0000 000024 (v02 VRTUAL)
[    0.000458] ACPI: XSDT 0x0000000000100000 000044 (v01 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000462] ACPI: FACP 0x0000000000101000 000114 (v06 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000466] ACPI: DSDT 0x00000000001011B8 01E184 (v02 MSFTVM DSDT01   00000001 MSFT 05000000)
[    0.000468] ACPI: FACS 0x0000000000101114 000040
[    0.000470] ACPI: OEM0 0x0000000000101154 000064 (v01 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000472] ACPI: SRAT 0x000000000011F33C 0002D0 (v02 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000474] ACPI: APIC 0x000000000011F60C 0000A8 (v04 VRTUAL MICROSFT 00000001 MSFT 00000001)
[    0.000478] ACPI: Local APIC address 0xfee00000
[    0.000704] Zone ranges:
[    0.000705]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    0.000706]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
[    0.000707]   Normal   [mem 0x0000000100000000-0x00000003387fffff]
[    0.000708] Movable zone start for each node
[    0.000708] Early memory node ranges
[    0.000709]   node   0: [mem 0x0000000000001000-0x000000000009ffff]
[    0.000709]   node   0: [mem 0x0000000000200000-0x00000000f7ffffff]
[    0.000710]   node   0: [mem 0x0000000100000000-0x00000003387fffff]
[    0.001485] Zeroed struct page in unavailable ranges: 31073 pages
[    0.001486] Initmem setup node 0 [mem 0x0000000000001000-0x00000003387fffff]
[    0.001488] On node 0 totalpages: 3344031
[    0.001489]   DMA zone: 59 pages used for memmap
[    0.001490]   DMA zone: 22 pages reserved
[    0.001490]   DMA zone: 3743 pages, LIFO batch:0
[    0.001568]   DMA32 zone: 16320 pages used for memmap
[    0.001570]   DMA32 zone: 1011712 pages, LIFO batch:63
[    0.023208]   Normal zone: 36384 pages used for memmap
[    0.023210]   Normal zone: 2328576 pages, LIFO batch:63
[    0.023950] ACPI: Local APIC address 0xfee00000
[    0.023956] ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
[    0.024336] IOAPIC[0]: apic_id 12, version 17, address 0xfec00000, GSI 0-23
[    0.024340] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.024341] ACPI: IRQ9 used by override.
[    0.024343] Using ACPI (MADT) for SMP configuration information
[    0.024349] smpboot: Allowing 12 CPUs, 0 hotplug CPUs
[    0.024359] [mem 0xf8000000-0xffffffff] available for PCI devices
[    0.024360] Booting paravirtualized kernel on bare hardware
[    0.024362] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>2750000 ns
[    0.155722] random: get_random_bytes called from start_kernel+0x93/0x4bb with crng_init=0
[    0.155731] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:12 nr_node_ids:1
[    0.156516] percpu: Embedded 42 pages/cpu s133400 r8192 d30440 u262144
[    0.156520] pcpu-alloc: s133400 r8192 d30440 u262144 alloc=1*2097152
[    0.156521] pcpu-alloc: [0] 00 01 02 03 04 05 06 07 [0] 08 09 10 11 -- -- -- --
[    0.156536] Built 1 zonelists, mobility grouping on.  Total pages: 3291246
[    0.156538] Kernel command line: initrd=\initrd.img panic=-1 pty.legacy_count=0 nr_cpus=12
[    0.159953] Dentry cache hash table entries: 2097152 (order: 12, 16777216 bytes)
[    0.161551] Inode-cache hash table entries: 1048576 (order: 11, 8388608 bytes)
[    0.187709] Memory: 4096404K/13376124K available (14360K kernel code, 1575K rwdata, 2836K rodata, 1504K init, 2792K bss, 334492K reserved, 0K cma-reserved)
[    0.188000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=12, Nodes=1
[    0.188008] ftrace: allocating 41537 entries in 163 pages
[    0.201148] rcu: Hierarchical RCU implementation.
[    0.201150] rcu:     RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=12.
[    0.201151]  All grace periods are expedited (rcu_expedited).
[    0.201151] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=12
[    0.203218] Using NULL legacy PIC
[    0.203220] NR_IRQS: 16640, nr_irqs: 520, preallocated irqs: 0
[    0.203609] Console: colour dummy device 80x25
[    0.203612] console [tty0] enabled
[    0.203617] ACPI: Core revision 20180810
[    0.203721] Failed to register legacy timer interrupt
[    0.203730] APIC: Switch to symmetric I/O mode setup
[    0.203731] Switched APIC routing to physical flat.
[    0.203750] Hyper-V: Using IPI hypercalls
[    0.203750] Hyper-V: Using MSR based APIC access
[    0.203755] clocksource: hyperv_clocksource_tsc_page: mask: 0xffffffffffffffff max_cycles: 0x24e6a1710, max_idle_ns:<PHONE_NUMBER>20 ns
[    0.203857] Calibrating delay loop (skipped), value calculated using timer frequency.. 6400.30 BogoMIPS (lpj=32001510)
[    0.203858] pid_max: default: 32768 minimum: 301
[    0.203876] Security Framework initialized
[    0.203905] Mount-cache hash table entries: 32768 (order: 6, 262144 bytes)
[    0.203927] Mountpoint-cache hash table entries: 32768 (order: 6, 262144 bytes)
[    0.204205] Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 512
[    0.204206] Last level dTLB entries: 4KB 1536, 2MB 1536, 4MB 768, 1GB 0
[    0.204207] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
[    0.204208] Spectre V2 : Spectre mitigation: LFENCE not serializing, switching to generic retpoline
[    0.204209] Spectre V2 : Mitigation: Full generic retpoline
[    0.204209] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
[    0.204214] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
[    0.204214] Spectre V2 : User space: Vulnerable
[    0.204215] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp
[    0.204454] Freeing SMP alternatives memory: 44K
[    0.205789] smpboot: CPU0: AMD Ryzen 5 1600 Six-Core Processor (family: 0x17, model: 0x1, stepping: 0x1)
[    0.205853] Performance Events: PMU not available due to virtualization, using software events only.
[    0.206011] rcu: Hierarchical SRCU implementation.
[    0.206136] random: crng done (trusting CPU's manufacturer)
[    0.206239] smp: Bringing up secondary CPUs ...
[    0.206299] x86: Booting SMP configuration:
[    0.206300] .... node  #0, CPUs:        #1  #2  #3  #4  #5  #6  #7
[    0.010264] calibrate_delay_direct() dropping min bogoMips estimate 0 = 29292640
[    1.254176]   #8  #9 #10 #11
[    1.853970] smp: Brought up 1 node, 12 CPUs
[    1.853970] smpboot: Max logical packages: 1
[    1.853970] smpboot: Total of 12 processors activated (76595.21 BogoMIPS)
[    1.923861] node 0 initialised, 2236307 pages in 70ms
[    1.925574] devtmpfs: initialized
[    1.925574] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>2750000 ns
[    1.925574] futex hash table entries: 4096 (order: 6, 262144 bytes)
[    1.925574] xor: automatically using best checksumming function   avx
[    1.925574] NET: Registered protocol family 16
[    1.925574] ACPI: bus type PCI registered
[    1.925574] PCI: Fatal: No config space access function found
[    1.934355] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    1.934355] raid6: Forced to use recovery algorithm avx2x2
[    1.934355] raid6: Forced gen() algo avx2x4
[    1.934355] ACPI: Added _OSI(Module Device)
[    1.934355] ACPI: Added _OSI(Processor Device)
[    1.934355] ACPI: Added _OSI(3.0 _SCP Extensions)
[    1.934355] ACPI: Added _OSI(Processor Aggregator Device)
[    1.934355] ACPI: Added _OSI(Linux-Dell-Video)
[    1.934355] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[    1.938806] ACPI: 1 ACPI AML tables successfully acquired and loaded
[    1.939616] ACPI: Interpreter enabled
[    1.939616] ACPI: (supports S0 S5)
[    1.939616] ACPI: Using IOAPIC for interrupt routing
[    1.939616] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    1.939616] ACPI: Enabled 1 GPEs in block 00 to 0F
[    1.944030] SCSI subsystem initialized
[    1.944160] hv_vmbus: Vmbus version:5.0
[    1.944160] PCI: Using ACPI for IRQ routing
[    1.944160] PCI: System does not support PCI
[    1.944668] hv_vmbus: Unknown GUID: c376c1c3-d276-48d2-90a9-c04748072c60
[    1.944346] clocksource: Switched to clocksource hyperv_clocksource_tsc_page
[    1.959195] VFS: Disk quotas dquot_6.6.0
[    1.959207] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    1.959249] FS-Cache: Loaded
[    1.959281] pnp: PnP ACPI init
[    1.959329] pnp 00:00: Plug and Play ACPI device, IDs PNP0b00 (active)
[    1.959367] pnp: PnP ACPI: found 1 devices
[    1.965218] NET: Registered protocol family 2
[    1.965360] tcp_listen_portaddr_hash hash table entries: 8192 (order: 5, 131072 bytes)
[    1.965376] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[    1.965726] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[    1.965815] TCP: Hash tables configured (established 131072 bind 65536)
[    1.965845] UDP hash table entries: 8192 (order: 6, 262144 bytes)
[    1.966067] UDP-Lite hash table entries: 8192 (order: 6, 262144 bytes)
[    1.966123] NET: Registered protocol family 1
[    1.966647] RPC: Registered named UNIX socket transport module.
[    1.966648] RPC: Registered udp transport module.
[    1.966648] RPC: Registered tcp transport module.
[    1.966649] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.966651] PCI: CLS 0 bytes, default 64
[    1.966720] Trying to unpack rootfs image as initramfs...
[    1.966891] Freeing initrd memory: 64K
[    1.966894] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    1.966895] software IO TLB: mapped [mem 0xf4000000-0xf8000000] (64MB)
[    1.968228] kvm: no hardware support
[    1.968230] has_svm: svm not available
[    1.968230] kvm: no hardware support
[    1.968676] Initialise system trusted keyrings
[    1.968819] workingset: timestamp_bits=46 max_order=22 bucket_order=0
[    1.969846] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    1.970279] NFS: Registering the id_resolver key type
[    1.970286] Key type id_resolver registered
[    1.970287] Key type id_legacy registered
[    1.970289] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    1.971448] Key type cifs.idmap registered
[    1.971549] fuse init (API version 7.27)
[    1.971749] SGI XFS with ACLs, security attributes, realtime, scrub, no debug enabled
[    1.973371] 9p: Installing v9fs 9p2000 file system support
[    1.973379] FS-Cache: Netfs '9p' registered for caching
[    1.973458] FS-Cache: Netfs 'ceph' registered for caching
[    1.973462] ceph: loaded (mds proto 32)
[    1.979031] NET: Registered protocol family 38
[    1.979034] Key type asymmetric registered
[    1.979034] Asymmetric key parser 'x509' registered
[    1.979049] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[    1.979051] io scheduler noop registered (default)
[    1.979946] hv_vmbus: registering driver hv_pci
[    1.980269] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    1.980810] Non-volatile memory driver v1.3
[    1.984118] brd: module loaded
[    1.985362] loop: module loaded
[    1.985658] hv_vmbus: registering driver hv_storvsc
[    1.985706] Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
[    1.986165] tun: Universal TUN/TAP device driver, 1.6
[    1.986268] PPP generic driver version 2.4.2
[    1.986403] PPP BSD Compression module registered
[    1.986405] PPP Deflate Compression module registered
[    1.986412] PPP MPPE Compression module registered
[    1.986413] NET: Registered protocol family 24
[    1.986419] hv_vmbus: registering driver hv_netvsc
[    1.988649] scsi host0: storvsc_host_t
[    1.998311] VFIO - User Level meta-driver version: 0.3
[    1.998515] hv_vmbus: registering driver hyperv_keyboard
[    1.998776] rtc_cmos 00:00: RTC can wake from S4
[    2.020806] rtc_cmos 00:00: registered as rtc0
[    2.020819] rtc_cmos 00:00: alarms up to one month, 114 bytes nvram
[    2.020972] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised<EMAIL_ADDRESS>[    2.021457] hv_utils: Registering HyperV Utility Driver
[    2.021458] hv_vmbus: registering driver hv_util
[    2.021490] hv_vmbus: registering driver hv_balloon
[    2.021498] hv_utils: cannot register PTP clock: 0
[    2.021741] drop_monitor: Initializing network drop monitor service
[    2.021767] Mirror/redirect action on
[    2.021997] IPVS: Registered protocols (TCP, UDP)
[    2.022014] IPVS: Connection hash table configured (size=4096, memory=64Kbytes)
[    2.022243] hv_utils: TimeSync IC version 4.0
[    2.022467] hv_balloon: Using Dynamic Memory protocol version 2.0
[    2.023802] IPVS: ipvs loaded.
[    2.023807] IPVS: [rr] scheduler registered.
[    2.023808] IPVS: [wrr] scheduler registered.
[    2.023809] IPVS: [sh] scheduler registered.
[    2.024482] hv_balloon: cold memory discard enabled
[    2.027218] ipt_CLUSTERIP: ClusterIP Version 0.8 loaded successfully
[    2.027752] Initializing XFRM netlink socket
[    2.027827] NET: Registered protocol family 10
[    2.028334] Segment Routing with IPv6
[    2.031268] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    2.031608] NET: Registered protocol family 17
[    2.031626] Bridge firewalling registered
[    2.031633] 8021q: 802.1Q VLAN Support v1.8
[    2.031655] sctp: Hash tables configured (bind 256/256)
[    2.031706] 9pnet: Installing 9P2000 support
[    2.031720] Key type dns_resolver registered
[    2.031729] Key type ceph registered
[    2.032085] libceph: loaded (mon/osd proto 15/24)
[    2.032088] hv_vmbus: registering driver hv_sock
[    2.032188] NET: Registered protocol family 40
[    2.032571] registered taskstats version 1
[    2.032579] Loading compiled-in X.509 certificates
[    2.032889] Btrfs loaded, crc32c=crc32c-generic
[    2.033546] rtc_cmos 00:00: setting system clock to 2020-05-31 19:06:44 UTC<PHONE_NUMBER>)
[    2.033565] Unstable clock detected, switching default tracing clock to "global"
               If you want to keep using the local clock, then add:
                 "trace_clock=local"
               on the kernel command line
[    2.036017] Freeing unused kernel image memory: 1504K
[    2.103910] Write protecting the kernel read-only data: 20480k
[    2.104763] Freeing unused kernel image memory: 1988K
[    2.104992] Freeing unused kernel image memory: 1260K
[    2.104993] Run /init as init process
[    2.335994] scsi 0:0:0:0: Direct-Access     Msft     Virtual Disk     1.0  PQ: 0 ANSI: 5
[    2.336547] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    2.337453] sd 0:0:0:0: [sda] 536870912 512-byte logical blocks: (275 GB/256 GiB)
[    2.337454] sd 0:0:0:0: [sda] 4096-byte physical blocks
[    2.337593] sd 0:0:0:0: [sda] Write Protect is off
[    2.337595] sd 0:0:0:0: [sda] Mode Sense: 0f 00 00 00
[    2.337869] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.338212] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    2.341187] sd 0:0:0:0: [sda] Attached SCSI disk
[    2.354927] EXT4-fs (sda): mounted filesystem with ordered data mode. Opts: discard,errors=remount-ro,data=ordered
[    2.367411] scsi 0:0:0:1: Direct-Access     Msft     Virtual Disk     1.0  PQ: 0 ANSI: 5
[    2.367929] sd 0:0:0:1: Attached scsi generic sg1 type 0
[    2.368808] sd 0:0:0:1: [sdb] 536870912 512-byte logical blocks: (275 GB/256 GiB)
[    2.368810] sd 0:0:0:1: [sdb] 4096-byte physical blocks
[    2.368989] sd 0:0:0:1: [sdb] Write Protect is off
[    2.368991] sd 0:0:0:1: [sdb] Mode Sense: 0f 00 00 00
[    2.369248] sd 0:0:0:1: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.372553] sd 0:0:0:1: [sdb] Attached SCSI disk
[    2.390587] EXT4-fs (sdb): recovery complete
[    2.392002] EXT4-fs (sdb): mounted filesystem with ordered data mode. Opts: discard,errors=remount-ro,data=ordered
[    2.451966] FS-Cache: Duplicate cookie detected
[    2.451968] FS-Cache: O-cookie c=000000001d484063 [p=00000000d518c32c fl=222 nc=0 na=1]
[    2.451968] FS-Cache: O-cookie d=00000000447dde30 n=000000009eb4bc2e
[    2.451969] FS-Cache: O-key=[10] '34323934393337353230'
[    2.451971] FS-Cache: N-cookie c=00000000a9c51d6f [p=00000000d518c32c fl=2 nc=0 na=1]
[    2.451972] FS-Cache: N-cookie d=00000000447dde30 n=000000006fbe2524
[    2.451972] FS-Cache: N-key=[10] '34323934393337353230'
[    2.457658] Adding 4194304k swap on /swap/file.  Priority:-2 extents:2 across:4202496k
[    3.003938] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   50.890482] hv_balloon: Max. dynamic memory size: 13064 MB

From https://github.com/microsoft/WSL/issues/4027#issuecomment-495812634:
dir C:\Windows\system32\p9np.dll
Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----        07.12.2019     16:42         107048 p9np.dll

reg query HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider /s
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder
    ProviderOrder    REG_SZ    P9NP,RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order
    ProviderOrder    REG_SZ    P9NP,RDPNP,LanmanWorkstation,webclient

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\ProviderOrder
    LanmanWorkstation    REG_DWORD    0x7d0
    RDPNP    REG_DWORD    0x3e8
    webclient    REG_DWORD    0xbb8
    P9NP    REG_DWORD    0x1f4

reg query HKLM\SYSTEM\CurrentControlSet\Services\p9np /s
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9np
    Description    REG_EXPAND_SZ    @%systemroot%\system32\p9np.dll,-101
    DisplayName    REG_EXPAND_SZ    @%systemroot%\system32\p9np.dll,-100

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9np\NetworkProvider
    DeviceName    REG_SZ    \Device\P9Rdr
    DisplayName    REG_EXPAND_SZ    @%systemroot%\system32\p9np.dll,-100
    Name    REG_SZ    Plan 9 Network Provider
    ProviderPath    REG_EXPAND_SZ    %SystemRoot%\System32\p9np.dll
    TriggerStartCompleteNotification    REG_BINARY    7510BCA3541EC641
    TriggerStartNotification    REG_BINARY    7508BCA3541EC641
    TriggerStartPrefix    REG_SZ    wsl$

reg query HKLM\SYSTEM\CurrentControlSet\Services\p9rdr /s
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\p9rdr
    DependOnService    REG_MULTI_SZ    RDBSS
    Description    REG_SZ    @%SystemRoot%\System32\drivers\p9rdr.sys,-101
    DisplayName    REG_SZ    @%SystemRoot%\System32\drivers\p9rdr.sys,-100
    ErrorControl    REG_DWORD    0x1
    ImagePath    REG_EXPAND_SZ    System32\drivers\p9rdr.sys
    Start    REG_DWORD    0x3
    Type    REG_DWORD    0x1

If you run the command wsl -l -v in Powershell, do you see your distribution listed as expected?

\wsl$\Ubuntu\ won't work if the distro is not running in background. I prefer setup openssh-server in Ubuntu, so it will run in the background, and \wsl$\Ubuntu\ will work.

If you run the command wsl -l -v in Powershell, do you see your distribution listed as expected?

Yes, the distro is installed, shows up, and is otherwise usable as expected.

\\wsl$\Ubuntu\ won't work if the distro is not running in background. I prefer setup openssh-server in Ubuntu, so it will run in the background, and \\wsl$\Ubuntu\ will work.

The distro is running, and manually navigating to \\wsl$ shows the expected Ubuntu folder when its running. If its not running that folder does not show up.

The distro is running, and manually navigating to \\wsl$ shows the expected Ubuntu folder when its running. If its not running that folder does not show up.

Yeah, maybe it's to be expected like that. Similar to computer in a network, how can we access it if the computer is turned off.

The distro is running, and manually navigating to \\wsl$ shows the expected Ubuntu folder when its running. If its not running that folder does not show up.

Yeah, maybe it's to be expected like that. Similar to computer in a network, how can we access it if the computer is turned off.

It is not. Despite the Ubuntu folder showing up I get the behaviour described in the report.

I have this exact same issue and my p9np.dll and registry keys look identical.

But calling explorer.exe . from bash does it work?
9p access is a bit weird:
PS C:\> wsl -l -v
  NAME                 STATE           VERSION
* Ubuntu-20.04         Running         2
  Ubuntu-20.04.wsl1    Stopped         1
  Alpine               Stopped         2
PS C:\> cd \\wsl$\Alpine
PS Microsoft.PowerShell.Core\FileSystem::\\wsl$\Alpine>

I can only do cd \\wsl$\Alpine, cd \\wsl$\Ubuntu-20.04 and cd \\wsl$\Ubuntu-20.04.wsl1 otherwise it says path does not exist.
So make sure you are typing the exact name of the distro.

@PhilG @gloy-atromitos Only \wsl$\ does not exist.

I don't know if I can be any more clear on this, it doesn't work ever.

I've read there are two 9p running servers, one for admin and the other for the user.
Do you have UAC disabled?
Can you try explorer.exe .  in an elevated WSL terminal (Run as administrator)?

Have previously done so, just verified it now, no change in behaviour across the board.

I have seen more users with the same problem. They can use explorer.exe . from /mnt/c but not from /home/username.
Maybe @SvenGroot has an idea what's happening.

try printenv if windows path is in the wsl path.

try printenv if windows path is in the wsl path.

Not necessary, the executable is found.

Can you post the output of mount?

/dev/sdb on / type ext4 (rw,relatime,discard,errors=remount-ro,data=ordered)
tmpfs on /mnt/wsl type tmpfs (rw,relatime)
tools on /init type 9p (ro,relatime,dirsync,aname=tools;fmask=022,loose,access=client,trans=fd,rfd=6,wfd=6)
none on /dev type devtmpfs (rw,nosuid,relatime,size=6520836k,nr_inodes=1630209,mode=755)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,noatime)
devpts on /dev/pts type devpts (rw,nosuid,noexec,noatime,gid=5,mode=620,ptmxmode=000)
none on /run type tmpfs (rw,nosuid,noexec,noatime,mode=755)
none on /run/lock type tmpfs (rw,nosuid,nodev,noexec,noatime)
none on /run/shm type tmpfs (rw,nosuid,nodev,noatime)
none on /run/user type tmpfs (rw,nosuid,nodev,noexec,noatime,mode=755)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu type cgroup (rw,nosuid,nodev,noexec,relatime,cpu)
cgroup on /sys/fs/cgroup/cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_prio)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
C:\ on /mnt/c type 9p (rw,noatime,dirsync,aname=drvfs;path=C:\;uid=1000;gid=1000;symlinkroot=/mnt/,mmap,access=client,msize=65536,trans=fd,rfd=8,wfd=8)
G:\ on /mnt/g type 9p (rw,noatime,dirsync,aname=drvfs;path=G:\;uid=1000;gid=1000;symlinkroot=/mnt/,mmap,access=client,msize=65536,trans=fd,rfd=8,wfd=8)

I'm seeing this problem also.
Can cd \\wsl$\Ubuntu-20.04 in Powershell but explorer or any other Windows program trying access just reports "Windows can not access \wsl$\Ubuntu-20.04".
PS C:\Users\nick> wsl -l -v
  NAME                   STATE           VERSION
* Ubuntu-20.04           Running         2
  docker-desktop         Stopped         2
  docker-desktop-data    Stopped         2

Interestingly launching explorer.exe . from within WSL2 works but always ends up opening my Documents folder in Windows filesystem instead.

I'm seeing this problem also.
Can cd \\wsl$\Ubuntu-20.04 in Powershell but explorer or any other Windows program trying access just reports "Windows can not access \wsl$\Ubuntu-20.04".
PS C:\Users\nick> wsl -l -v
  NAME                   STATE           VERSION
* Ubuntu-20.04           Running         2
  docker-desktop         Stopped         2
  docker-desktop-data    Stopped         2

Interestingly launching explorer.exe . from within WSL2 works but always ends up opening my Documents folder in Windows filesystem instead. This works however.
PS c:\Users\nick> subst.exe w: \\wsl$\Ubuntu-20.04\home\nick

/dev/sdb on / type ext4 (rw,relatime,discard,errors=remount-ro,data=ordered)
tmpfs on /mnt/wsl type tmpfs (rw,relatime)
tools on /init type 9p (ro,relatime,dirsync,aname=tools;fmask=022,loose,access=client,trans=fd,rfd=6,wfd=6)
none on /dev type devtmpfs (rw,nosuid,relatime,size=6488740k,nr_inodes=1622185,mode=755)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,noatime)
devpts on /dev/pts type devpts (rw,nosuid,noexec,noatime,gid=5,mode=620,ptmxmode=000)
none on /run type tmpfs (rw,nosuid,noexec,noatime,mode=755)
none on /run/lock type tmpfs (rw,nosuid,nodev,noexec,noatime)
none on /run/shm type tmpfs (rw,nosuid,nodev,noatime)
none on /run/user type tmpfs (rw,nosuid,nodev,noexec,noatime,mode=755)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu type cgroup (rw,nosuid,nodev,noexec,relatime,cpu)
cgroup on /sys/fs/cgroup/cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_prio)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
C:\ on /mnt/c type 9p (rw,noatime,dirsync,aname=drvfs;path=C:\;uid=1000;gid=1000;symlinkroot=/mnt/,mmap,access=client,msize=65536,trans=fd,rfd=8,wfd=8)
D:\ on /mnt/d type 9p (rw,noatime,dirsync,aname=drvfs;path=D:\;uid=1000;gid=1000;symlinkroot=/mnt/,mmap,access=client,msize=65536,trans=fd,rfd=8,wfd=8)
G:\ on /mnt/g type 9p (rw,noatime,dirsync,aname=drvfs;path=G:\;uid=1000;gid=1000;symlinkroot=/mnt/,mmap,access=client,msize=65536,trans=fd,rfd=8,wfd=8)

I got exactly the same issue. Nobody found a better solution yet?

Got the same issue after upgrading Windows:
https://github.com/microsoft/WSL/issues/5302#issuecomment-647871602

Fixed now:
https://github.com/microsoft/WSL/issues/5302#issuecomment-648065419

I'm seeing this problem also.
Can cd \\wsl$\Ubuntu-20.04 in Powershell but explorer or any other Windows program trying access just reports "Windows can not access \wsl$\Ubuntu-20.04".

This is very clearly different than the issue I am having; this already doesn't work for me.

Got the same issue after upgrading Windows:
#5302 (comment)

This also doesn't seem to be related to my problem, as the dmesg there output includes errors, which mine does not.

Today I again un- and reinstalled WSL2 with a reboot in-between every step, the issue persists exactly as described in my original comment.

I installed via chocolatey and have the same issue: choco install wsl2 wsl-ubuntu-1804

My issue turned out to be that via Chocolatey WSL Ubuntu is installed to require admin rights (choco install wsl2 wsl-ubuntu-1804). This is also reflected in that the command line is only accessible when running as an admin. I tried running explorer as admin but that didn't help.
It was solved by:

Navigate to (C:\ProgramData\chocolatey\lib\wsl-ubuntu-1804\tools\unzipped) and change the folder permissions to full control for "users"

Afterward:

I can open WSL terminal without admin privileges
I can cd ~ && explorer.exe .
I can navigate to \\wsl$\Ubuntu-18.04 manually from explorer

FWIW, I'm seeing the same issue as well. I installed Ubunto 20.04 from the Windows Store. I can cd into \\wsl$\Ubuntu-20.04 but cannot reach it from explorer. I receive the Cannot access error like most other people.

FWIW, I'm seeing the same issue as well. I installed Ubunto 20.04 from the Windows Store. I can cd into \\wsl$\Ubuntu-20.04 but cannot reach it from explorer. I receive the Cannot access error like most other people. The troubleshooting tips earlier in this bug's conversation also produce the same result. The 9P network interface looks like it's starting normally, but Windows can't see it.

Very same issue on my computer as well.

So, to add another twist to this, if I use the url \\wsl$\Ubuntu-20.04 in Google Chrome (just paste the url into the address bar and hit enter) , I can actually see the WSL file system like I would expect. It's only in Explorer, IE,  or Edge where the error occurs. That tells me something is working right.

So, to add another twist to this, if I use the url \\wsl$\Ubuntu-20.04 in Google Chrome (just paste the url into the address bar and hit enter) , I can actually see the WSL file system like I would expect. It's only in Explorer, IE, or Edge where the error occurs. That tells me something is working right.

That definitely doesn't work for mine (\\wsl$\Ubuntu in my case just leads to a "not found" error page in Chrome and Edge). In Explorer it's just the usual "Attempt to access invalid address".
cd \\wsl$\Ubuntu doesn't work from either Command or Powershell. (You can't even use cd with UNC paths in cmd.exe)
For reference I'm running Ubuntu 20.04 LTS (GNU/Linux 4.19.104-microsoft-standard x86_64) in Windows 10 Pro version 2004 build 19041.388

So, to add another twist to this, if I use the url \\wsl$\Ubuntu-20.04 in Google Chrome (just paste the url into the address bar and hit enter) , I can actually see the WSL file system like I would expect. It's only in Explorer, IE, or Edge where the error occurs. That tells me something is working right.

That definitely doesn't work for mine (\\wsl$\Ubuntu in my case just leads to a "not found" error page in Chrome and Edge). In Explorer it's just the usual "Attempt to access invalid address".
cd \\wsl$\Ubuntu doesn't work from either Command or Powershell. (You can't even use cd with UNC paths in cmd.exe)
For reference I'm running Ubuntu 20.04 LTS (GNU/Linux 4.19.104-microsoft-standard x86_64) in Windows 10 Pro version 2004 build 19041.388
Edit: for completeness:
wsl -l -v
  NAME                   STATE           VERSION
* Ubuntu                 Running         2
  docker-desktop-data    Stopped         2
  docker-desktop         Stopped         2

My versions and symptoms are exactly the same as MartyMacGyver's

I solved this problem by uninstalling and installing the WSL2 kernel component (right click uninstall -> reboot -> install -> reboot):
https://aka.ms/wsl2kernel
Before that I had removed my WSL2 instance.
Maybe this helps some people.

Tried what komander suggested - no luck

I have done the kernel component reinstall during previous full reinstalls. The workaround described in michael-imbeaults issue works for me too.

I have done the kernel component reinstall during previous full reinstalls. The workaround described in michael-imbeaults issue works for me too.

This work around to map a network drive to \wsl$\Ubuntu works for me too.

Same symptoms here, can't access \\wsl$\Debian path within Explorer. Nor can I dir \\wsl$\Debian in PS.
Tried another distro (Ubuntu-20.04) from scratch but no difference.
The "network drive" hack works to access WSL files, I mounted \\wsl$\Debian to L: drive.
However it breaks expectations, especially for IntelliJ IDEs (since 2020.2) watching for \\wsl$\ paths to enable WSL-side git.
This leads to a completely unusable git integration, and the following appears in dmesg output :

[  698.798692] init: (694) ERROR: CreateProcessParseCommon:849: Failed to translate L:\home\username\dev\project\path

Which sounds logical as soon as project is accessed through network drive mount point.
By the way, there is another interesting output in dmesg :

[    1.975420] init: (2) ERROR: UtilCreateProcessAndWait:474: /bin/mount failed with 2
[    1.975486] init: (1) ERROR: UtilCreateProcessAndWait:489: /bin/mount failed with status 0x
[    1.975487] ff00
[    1.975490] init: (1) ERROR: ConfigMountFsTab:2077: Processing fstab with mount -a failed.
[    1.975966] init: (3) ERROR: UtilCreateProcessAndWait:474: /bin/mount failed with 2
[    1.976024] init: (1) ERROR: UtilCreateProcessAndWait:489: /bin/mount failed with status 0x
[    1.976025] ff00
[    1.976028] init: (1) ERROR: MountPlan9:478: mount cache=mmap,noatime,trans=fd,rfdno=8,wfdno=8,msize=65536,aname=drvfs;path=C:;uid=0;gid=0;symlinkroot=/mnt/
[    1.976029]  failed 17
[    1.976434] init: (4) ERROR: UtilCreateProcessAndWait:474: /bin/mount failed with 2

Win10 Pro 2004 19041.423
wsl -l -v
  NAME                   STATE           VERSION
* Debian                 Running         2
  docker-desktop         Running         2
  docker-desktop-data    Running         2
  Ubuntu-20.04           Stopped         2

Mine does the same as @NickBower-Woodside and no access to map the drive

powershell (elevated or not), git-bash,chrome, firefox can all access it.
within Ubuntu /mtn/wsl shows up and I can access all drives. I tried re-installing the kernal update, Ubuntu, adding a different distro, none worked.
Elevated explorer didn't work.
using \wsl\Ubuntu-20.04
Brought up this, but no credentials worked  (mentioned in one of the release notes is that both wsl and wsl$ should work)

I'm wondering if something else is interfering with it, maybe a wrong permission or some kind, maybe windows security firewall settings, or network connections and adapter settings. I've got Malwarebytes premium, I have PIA - but it makes no difference if that is active or not. Bitlocker is active. There's a vEthernet (WSL) Hyper-V Virtual Ethernet Adapter set up, along with a couple of other vEthernet ones.
It makes no difference if Docker is running or not

I can't map WSL distro as a network drive (windows cannot access \\wsl$\Ubuntu\) but I can open a pycharm and project in WSL and work normally

Check whether your distro is really "Ubuntu" or rather something like Ubuntu22...
 wsl -l

I can't map WSL distro as a network drive (windows cannot access \\wsl$\Ubuntu\) but I can open a pycharm and project in WSL and work normally

@Alim-Oezdemir
I have; I actually checked before that I had a different default set after installing docker; I noticed that e.g. VSCode https://code.visualstudio.com/docs/remote/wsl with WSL started working again by changing WSL default distro
wsl -l
Windows Subsystem for Linux Distributions:
docker-desktop-data (Default)
docker-desktop
Ubuntu

@dkocich, try to see if it runs
wsl -l -v
  NAME                   STATE           VERSION
* Debian                 Running         2
  kali-linux             Stopped         2
  Arch                   Stopped         1
  docker-desktop-data    Stopped         2
  docker-desktop         Stopped         2

In my case I only can see \wsl$\Debian, with a short
wsl -d docker-desktop \wsl$\docker-desktop is visible too.

Interoperability between WSL and Windows filesystems is a huge issue.
Files created in WSL/WSL2 aren't visible when Windows APIs try to read or list them.
Full stop.
I am a cloud engineer at Microsoft and this issue has impeded my ability to do posix development for months.
Try creating a directory in WSL/WSL 2 - then try opening it with VSC.
Problem is WORSE with WSL2.  This is not a hard problem to understand if you actually try to use WSL2.
Problem is CLEARLY illustrated here:

Summary: With WSL2 and Ubuntu from the MS store, any attempt to explore \\wsl$\Ubuntu fails. BUT cmd.exe /s /k pushd "\\wsl$\Ubuntu" in an elevated command prompt gives me a (pseudo) Z: drive with read and write access to my Ubuntu installation. This surprises me, and makes me wonder if it's a clue as to what's going on here.
Also, any other app with elevated permissions works (e.g., VS Code running as admin).

So, I've been fighting this for a while and I've yet to see a solution, but the admin thing with Chocolatey game me an idea (Note: I'm just using Ubuntu from the MS store, and have installed the WSL2 kernel update, etc. as noted previously).
Whenever I use explorer (running at the usual user level) to browse to \\wsl$ I see the Ubuntu folder, and clicking it results in the old "Attempt to access invalid address" error.
I have a small helper installed (http://code.kliu.org/cmdopen/) that gives me two context menu entries to open a command shell normally or elevated.
If I right click and open command shell, it fails (or fails to do anything at all). But if I select "Open Elevated Command Prompt", after the UAC prompt (as expected) I get a command prompt at Z:
This is interesting as there is NO Z: drive on my system that's normally visible. In fact, I can create a drive mapping to Z: from something else entirely (non-admin) and there's no conflict whatsoever.
I can touch a file there and see it in Ubuntu, and vice versa. So far I still can't use explorer to interact with WSL2 Ubuntu so that doesn't help there.
The full command line, which apparently only works with elevated permissions, is:
cmd /s /k pushd "\\wsl$\Ubuntu"

A more concise summary of what seems to work, at least for one running WSL2 OS.
Using:

Windows 10 Pro x64, 19041.508 (with experience pack 120.2212.31.0)
Ubuntu from the MS app store
WSL2 with the latest kernel update

When I reboot, there are no drives under \\wsl$ in explorer, and the following are what are installed and aren't yet running.
>wsl -l
Windows Subsystem for Linux Distributions:
docker-desktop-data (Default)
Ubuntu
docker-desktop

I start Ubuntu (wsl -d Ubuntu or opening the Windows Terminal tab for it).
I explore/refresh \\wsl$ and Ubuntu eventually appears. Clicking on it doesn't work (and it never works, even after the subsequent steps):

I then use my normal windows command prompt and enter pushd \\wsl$\Ubuntu
I can browse Ubuntu via the Z: pseudo drive letter via the command prompt.
Soon, a network location appears in This PC:

I can browse and manipulate the filesystem in explorer via that network location only.
Now interestingly, I can then do a pushd \\wsl$\docker-desktop (as it's also installed) and when I do that the network location's effective target changes to... the Docker Desktop filesystem. If I pushd back to Ubuntu I can again interact with it.
So, is this useful? If you can deal with exploring only one WSL2 filesystem at a time then perhaps. I'm surprised it worked at all as a normal user.
The key oddity here is that as far as the system is concerned Z: isn't really mapped, yet clearly it acts as though it is. And I don't see a way to tell pushd to pick another letter.
Thoughts on this?

Same problem here. Any recommendations?

Unfortunately for me there has been no news on this issue. The only new piece of information from the discussion thus far has been that while I can't access \\wsl$\Ubuntu via explorer or command line it is possible to mount \\wsl$\Ubuntu as a network drive and access that.

Same issue here. Don't have a clue. I'm trying to install Ubuntu-20.04 on Win 10 (2004, just updated from 1909 since i had this issue) for developing with docker wsl containers. But since windows can't access the linux filesystem event a docker image pull fails.

Unfortunately for me there has been no news on this issue. The only new piece of information from the discussion thus far has been that while I can't access \\wsl$\Ubuntu via explorer or command line it is possible to mount \\wsl$\Ubuntu as a network drive and access that.

I am having exactly the same issue.
I can mount \wsl$\Ubuntu-20.04 as a Network Drive but I cant get it to open on my IDE with just \wsl$....
This might be a thing on my works Laptop and maybe because the Ubuntu I am using isnt from the Windows Store.

Yes, sadly, there is still no progress as it seems :no_mouth:

Yup. Same problem. No fix.

I am now running Version 20H2 (OS Build 19042.662) and every single information in the original report is still unchanged. Would be nice to get some reaction or more hints on what to check.

I absolutely agree with @PhilG .
I would love to help troubleshooting this issue.

Yes I agree with @PhilG , Couldnt get it fixed after upgrading to 20H2(OS Build 19042.662).

Same issue, this makes WSL worthless for key cross platform user accessibility scenarios.  Currently on 20H20 and this issue is blocking.

Hello everyone,
I see everyone trying to access \\wsl$\Ubuntu but have to take a look on how your Distro is named?
I dont see very often where people have made the work of exporting wsl and import it again just to change the name of it.
Please look at how your Distro is named... With the command wsl -l -v you can see the name of it.
The most common is \\wsl$\Ubuntu-20.04.

@K2ouMais Most of us can see the distro name in \wsl$\ as seen here:

but are unable to actually open it.

@Kufat
Please open powershell and type wsl -l -v.
Please put the output here.

PS C:\Users\Kufat> wsl -l -v
  NAME      STATE           VERSION
* Ubuntu    Running         2

That looks good, but I am asking myself how did you got your WSL Distro name to only "Ubuntu".
When you install it, it is always the full distro name like "Ubuntu-18.04" or "Ubuntu-20.04".

This was the default. Perhaps you and I installed it in different ways. Looking through the various posts, both naming formats (just distro and distro-version) seem common.
In any event, I don't want to clutter this thread with redundant info.

I have some more questions...

Did you installed it through the Windows Store?
Did you installed it in Powershell?

I am asking because I have it on 3 PCs and on none of them my distro is only called "Ubuntu".
Just try this in Powershell:
Create a Folder where you have some space to save your distro. For example C:\WSL.

wsl --shutdown
wsl --export Ubuntu C:\WSL\Ubuntu-20.04.tar
wsl --unregister Ubuntu
wsl --import Ubuntu-20.04 C:\WSL C:\WSL\Ubuntu-20.04.tar

Maybe it has something to do where the your version was installed.
You can see on point 4 that it will be installed under C:\WSL.

The distribution name is correct, and as indicated by the wealth of information and previously attempted ideas in this thread not a simple misconception.

Anyway, I'm facing the same problem on a Debian distro, where there are no name variant.

Unfortunately that's not it either. Enabled firewall logging of disallowed connection attempts, tried to open \wsl$\Ubuntu, no traffic denied. (Also, not sure why you're mentioning Docker, but I'm not running it. Only thing I have running in terms of Hyper-V is the one WSL2 instance.)

Is there any event logging for the P9 subsystem? logman query providers doesn't show anything with "plan" or "p9" in the name. I created a trace log for everything with 'hyper' in the name; no interesting results.

Hi all,
I am facing the same issue.
Information that may be useful in debugging:
PS Microsoft.PowerShell.Core\FileSystem::\\wsl$\Ubuntu> wsl -l -v
  NAME      STATE           VERSION
* Ubuntu    Running         2

agrawpri@LAPTOP-NAME ~> dmesg | grep 9p
[    0.422581] 9p: Installing v9fs 9p2000 file system support
[    0.422591] FS-Cache: Netfs '9p' registered for caching
[    0.487510] 9pnet: Installing 9P2000 support

The things that don't work:

Accessing \\wsl$\Ubuntu from File Explorer
Mapping \\wsl$\Ubuntu to a Network Drive
Powershell/Ubuntu: explorer.exe . or explorer.exe /mnt/c (Opens up Documents)

The things that do work:

Ubuntu (from Microsoft Store) works perfectly fine
Powershell: cd \\wsl$\Ubuntu
Opening up Android Studio/VSCode projects by putting in \\wsl$\Ubuntu in their respective explorers (weird why File Explorer does not work when the IDE explorers do).

Any help will be hugely appreciated.
Regards,
Priyansh

Hi all,
I am facing the same issue. OS build 19042.685.
Successful installation of Ubuntu 20.04 from Microsoft Store on fresh Windows installation.
I'm a little sad about it. Everything has worked great on my previous computer but on my new computer I cannot access WSL filesystem from explorer.
I will be grateful for any help, I am a big fan of WSL expecially WSL 2 version.

Potential fix was found here. It worked for me. https://github.com/microsoft/WSL/issues/4260
Issue stems from lack of '/etc/wsl.conf` file. I did not have this file in my Debian install by default in a fresh install.

Edited wsl.conf as described above and in #4260 and rebooted. No change over here, unfortunately..
I also tried installing Debian to see if it behaved differently. Same error.

@whaaaley , Thanks for sharing, That did worked for me.
@Kufat , After making those changes to wsl.conf (/etc/wsl.conf)
step1:
Enable extra metadata options by default
[automount]
enabled = true
step2:
--> Run Powershell as 'Administrator'
PS C:\WINDOWS\system32> Restart-Service LxssManager
cmd+R -> \wsl$\Ubuntu-20.04\
worked like a charm! Thanks a lot guys

@kzos Yes, that's what I tried. (I rebooted rather than restarting LxssManager, just because I had some updates pending as well.) I'm unsure why you're telling me how to do something that I just said that I just did. :)

Its Strange to know why it is not working ,
Anyways, try to add/modify configs to wsl.conf file
as modifying that file helped fix the issue, I have a feeling like that file could help you in someway in fixing the problem that you are facing!.
fyr:
https://ridicurious.com/2019/07/25/setup-wsl-launch-configuration-wsl-conf/

@Kufat , also try passing your home folder path
cmd+r
'\wsl$\Ubuntu-20.04\home\kufat'
and check, as for few , this worked after making modifications to wsl.conf.

windows+r
\\wsl$\Ubuntu\home\kufat
"The specified path does not exist" even though
kufat@Phoenix:~$ pwd
/home/kufat

My .wslconfig in Windows User home directory:
[wsl2]
memory=2GB
processors=2
localhostForwarding=true
swap=0

Change LxssManager to autostart in regedit. Start LxssManager in services.msc.

Lets test.

Works.

If it doesn't work, try Network Reset, and restart computer.
From what I experienced, when there is a warning, that resource is unavailable, maybe you need more computer RAM, or try again later.

Potential fix was found here. It worked for me. #4260
Issue stems from lack of '/etc/wsl.conf` file. I did not have this file in my Debian install by default in a fresh install.
The bit that fixed it for me were these lines specifically. These settings are supposed to be default settings, but perhaps they're getting overwritten somehow. Who knows. I just know that I haven't had this issue since.
# Enable extra metadata options by default
[automount]
enabled = true

Did not work for me, no change in observed behaviour. The documentation also reads as if this option is about Windows drives being mounted into WSL, not the WSL VHD being exposed to windows.

I've tried to reinstall whole the WSL 2 ecosystem (disable and enable WSL, Hyper-V, update Linux kernell, turn off and on VirtualMachinePlatform…) and the problem still remains.
I can access \\wsl$ in explorer but I cannot access \\wsl$\Ubuntu-20.04.
If I run WSL as an administrator, I can start explorer with explorer.exe . If I run WSL as user account (even though I'm an administrator) the explorer.exe . does not work.
I also can't run WSL using Windows Terminal with proper configuration which is set in settins.json file of Windows Terminal. DefaultProfile is the only thing which works. If I try to set startingDirectory or tabTitle they are just ignored and WSL always start in my windows home directory /mnt/c/Users/<Username>.
All of these things worked properly on my previous computer but I don´t now how to make them work properly on my new computer. None of the above solutions did´t help. :-(
I was wondering if there could be a problem with the windows firewall settings or something like that?

As stated I was having and still have this issue (cannot access WSL2 filesystem from Windows through \wsl$\Ubuntu-20.04 - only mounting it as a network drive) on one of my PC.
Another PC was instead working fine up to yesterday when it started having the same exact issue. No changes on my side. Might have downloaded Windows update overnight.

Another PC was instead working fine up to yesterday when it started having the same exact issue. No changes on my side. Might have downloaded Windows update overnight.

Could you expore Events Viewer, looking for unusual errors, between the last time this PC was fully functionnal and the first time you noticed the issue ?
Also, do you notice something error-ish when executing sudo dmesg on your WSL distro ?

@florent-izypay I have been unable to find any interesting messages in either Event Veiwer or dmesg/Linux kernel logs.
Is there anyone who is experiencing this problem and who didn't upgrade to Windows 10 over an existing Windows install? In other words, is anyone experiencing this problem with a clean installation of Windows 10? For example, my installation was upgraded from Windows 7.

@florent-izypay I have been unable to find any interesting messages in either Event Veiwer or dmesg/Linux kernel logs.
Is there anyone who is experiencing this problem and who didn't upgrade to Windows 10 over an existing Windows install? In other words, is anyone experiencing this problem with a clean installation of Windows 10? For example, my installation was upgraded from Windows 7.

Thanks for your feedback.
I also suspect that this is related to old Registry values or legacy inherited edge cases that are out of the common tests cases scope.
My misbehaving Windows installation is also a long-living, multi-upgraded instance: Vista ->7 -> 8 -> 8.1 -> 10 + every updates from 10.

@florent-izypay definitively my case, very old Windows install upgraded a few times (Me -> Xp -> 7 -> 10)

Is there anyone who is experiencing this problem and who didn't upgrade to Windows 10 over an existing Windows install?

Yes. This happened to me on two fresh windows 10 installs.

Had the same issue and tried everything but in the end found the WSL inside the following folder:
C:\Users<user>\AppData\Local\Packages\CanonicalGroupLimited.Ubuntu18.04onWindows_79rhkp1fndgsc\LocalState\rootfs
Hope it helps.

i get the same thing:
$ sudo mount -t drvfs 'Y:' /mnt/foo
mount: /mnt/foo: wrong fs type, bad option, bad superblock on Y:, missing codepage or helper program, or other error.
<3>init: (676) ERROR: UtilCreateProcessAndWait:489: /bin/mount failed with status 0x2000
No error information

@Spongman That's a completely different issue. This is about being unable to access Linux files from Windows (using e.g. Explorer.) Your issue pertains to going in the opposite direction.

not quite. that Y: is mounted \\wsl$\ share.

for me the issue was solved when I added P9NP in registry HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder
ProviderOrder    REG_SZ    P9NP,RDPNP,LanmanWorkstation,webclient
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order
ProviderOrder    REG_SZ    P9NP,RDPNP,LanmanWorkstation,webclient
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\ProviderOrder
LanmanWorkstation    REG_DWORD    0x7d0
RDPNP    REG_DWORD    0x3e8
webclient    REG_DWORD    0xbb8
P9NP    REG_DWORD    0x1f4

for me the issue was solved when I added P9NP in registry HKLM\SYSTEM\CurrentControlSet\Control\NetworkProvider
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder
ProviderOrder REG_SZ P9NP,RDPNP,LanmanWorkstation,webclient
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order
ProviderOrder REG_SZ P9NP,RDPNP,LanmanWorkstation,webclient
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\ProviderOrder
LanmanWorkstation REG_DWORD 0x7d0
RDPNP REG_DWORD 0x3e8
webclient REG_DWORD 0xbb8
P9NP REG_DWORD 0x1f4

This is also what my system was missing this morning.

What does that P9NP key does?
I am trying to understand how this is a fix and how you found it?

When running the commands from additional information section I noticed that P9NP was absent from my output and was present in the sample output:

Then saw @a4ex had just forcibly updated those registry keys, so tried that.

@K2ouMais WSL dev explained it in https://github.com/microsoft/WSL/issues/4027#issuecomment-495812634 and subsequent posts.

As we're nearing the one year anniversary of this issue I'm going to update some information.

Your Windows build number: (Type ver at a Windows Command Prompt)
Microsoft Windows [Version 10.0.19042.985]
Additionally I have attached a wsl.wprp recorded log in zipped format. During the recording of this I first tried to access \\wsl$\Ubuntu in Windows Explorer directly. Right afterwards I (successfully) access the WSL2 filesystem via a mapped network drive which is mapped to the same path \\wsl$\Ubuntu. wsl.etl.zip
All registry query output from the original post remains completely unchanged.

I don't know if I can be any more clear on this, access to the distros filesystem from Windows doesn't work ever.

But calling explorer.exe . from bash does it work?

It does not work if the pwd is in the distros filesystem.

Found a workaround for this with an overlay mount, since calling windows executables when $PWD is on a mounted linux filesystem gives a invalid argument error.
So I do have a fstab like this
LABEL=wsl /mnt/home btrfs defaults 0 0

then at login I run a script with
sudo mkdir -p /mnt/home/.work /mnt/home/.lower /mnt/home/$USER

# mount home with overlay
sudo mount -t overlay overlay -o lowerdir=/mnt/home/.lower,upperdir=/mnt/home/$USER,workdir=/mnt/home/.work ~/

Now I can call windows executables if $PWD is under $HOME (or subfolders). From windows I can access the filesystem tree of the mounted directory (it doesn't give an invalid adress) but still opening files gives a permission error.

My workaround was to open powershell and create a symlink using the following command:
cmd /c mklink /d c:\wslshare \wsl$\Ubuntu-18.04

Interesting idea, but that doesn't work either for me.

Hold left shift key and while clicking shutdown in windows, this fixed this issue for me

That disables fast startup as far as I understand, which I don't have active in the first place. So this doesn't help me either.

This helped me: https://github.com/microsoft/WSL/issues/4027#issuecomment-495812634

This information is already included in my original report from over a year ago.

Ok sorry for that. I came here via google and had a hard time finding a solution to a very similar problem - then was happy to find one in your post (but as it seems a different one than you). I wanted to help future "google"-people, to have an easier way of finding a potential solution to their problem. However, I can see that I was totally misreading your initial post and apologize for that. If you want me to delete my post, please let me know.

Sorry for being harsh, that's understandable and will hopefully help someone who has the same problem. I am just pretty disheartened because since I made the original report there has been almost no news on what I can try or what further information I should provide.

stop here

This is my case, hope can help you .
It's OK when using win10, but after ugrade to win11, I met the same problem.

navigating to \wsl$ shows the expected Ubuntu folder
click Ubuntu folder , receive error alert Attempt to access invalid address

My solve is :
wsl --shutdown
and start wsl again.

Further, I found that it's the cause of a customise script. This script do some init of wsl when windows starts, If remove this script, everything is OK .
So If you meet the same problem, you may use your own script when wsl starts, remove it , shutdown wsl , and start again.

This is my case, hope can help you .
It's OK when using win10, but after ugrade to win11, I met the same problem.

navigating to \wsl$ shows the expected Ubuntu folder
click Ubuntu folder , receive error alert Attempt to access invalid address

My solve is :
wsl --shutdown
and start wsl again.

Further, I found that it's the cause of a customise script. This script do some init of wsl when windows starts, If remove this script, everything is OK .
So If you meet the same problem, you may use your own script when wsl starts, remove it , shutdown wsl , and start again.

I have a completely barebones WSL Ubuntu installation, there is no custom initialization of any kind. As previously described multiple times restarting the WSL engine does not change any apparent behaviour.

Strange.
Maybe try to build WSL2 kernel yourself, open 9p debug option (CONFIG_NET_9P_DEBUG ) and use dmesg command to see if some error info printed.

win 11 users have this bug widely, include me.

After updated to win 11 wsl --update solved

Strange.
Maybe try to build WSL2 kernel yourself, open 9p debug option (CONFIG_NET_9P_DEBUG ) and use dmesg command to see if some error info printed.

This was the best suggestion I'd seen in some time. I did so (booted kernel, ensured log level was set to debug) and unfortunately there was no information printed. What I'd like to do now is see if there's any way to get debug-level output from the Windows side. Any suggestions?

Further, I found that it's the cause of a customise script. This script do some init of wsl when windows starts, If remove this script, everything is OK .

Thanks @yaofahua! that did the trick, I have a taskmanager setup to run enable the cron at windows startup, I wonder if it's what caused my issue.

@Kufat Dunno if this undocumented option for wsl.conf could be of any help.

For the filed issue on my machine the output with the option mentioned by @onomatopellan results in this log file:
3.129120390: INFO:     Server started.
3.151616215: INFO:     Accepted connection.

Steps taken:

Edit wsl.conf
Run wsl --shutdown
Double click my network mount Z:\ pointing to \\wsl$\Ubuntu which starts the distro in WSL and I get access via this method
Manually type \\wsl$\Ubuntu in the Explorer address bar, receive previously described error
Run sudo cat /9p-logs.txt

I've had this issue since I upgraded to Win11, october 9th.
Yesterday I formatted my system disk och made a clean install, added feature Virtual Machine Platform, wsl --update, wsl --install ubuntu.
In that order.
Directly after install it opens ubuntu wsl automatically and I can open explorer.exe . from the prompt in my home directory, but after wsl --shutdown and opening wsl ubuntu yet again from windows terminal it's back to being denied. (Both through file explorer, and wsl)
If I start wsl from an elevated windows terminal prompt I get "Invalid argument" when I try explorer.exe . in the home directory.

Hold left shift key while clicking shutdown in windows, this fixed this issue for me

WSL filesystem became inaccessible today. No idea why. Above trick form @rajesh221b solved it....

After upgrading to Windows 11 this issue was solved for me. Under Windows 10 none of the suggestions on this page worked for me.

After an windows update from yesterday (KB5008353 and KB5009469) I had the same issue:
Windows Explorer could not reach "\wsl.localhost\Ubuntu-20.04"
This post helped me solving it:
https://github.com/microsoft/WSL/issues/4027#issuecomment-1028878237
Here is what I did to get it working again for me:
"/etc/wsl.conf" was not present on my system.
So I created it with
sudo vi /etc/wsl.conf
and inserted this values:
[automount]
enabled = true
mountFsTab = true

After that I restarted wsl with
wsl --shutdown
and it worked!
Addendum: This is probably not the solution for the creator of this entry (PhilG), but mentioned as help for other users facing the same issue after the windows update.

same issue. open \wsl$ in explore lists ubuntu-20.04 but double click it leading to explore freeze.  however, open ubuntu-20.04 in pre-defined remote driver like driver W: (the path is \wsl$\ubuntu-20.04), it works.

I had the same issue and the only thing that helped was exporting my distro, uninstalling all WSL-related stuff (I had installed both the Windows optional feature and the WSL app from the store + WSLg) and reinstalling again (just the store app) + importing back the distro. Now it works perfectly.

I had the same issue until a few days ago and the only thing that helped was exporting my distro, uninstalling all WSL-related stuff (I had installed both the Windows optional feature and the WSL app from the store + WSLg) and reinstalling again (just the store app) + importing back the distro. Now it works perfectly.

Have you tested it a few days already? I ask because that worked for us too for an hour or so before it stopped. Which means you need to reinstall everything a few times every day. This is wasting a couple of hours of work every day and even more than that from lost focus.
This was the same on all our Windows 11 machines (5 desktops and 4 notebooks) with vastly different hardware and profiles. We haven't been able to use WSL since the automatic upgrade in October 2021.
Since a few weeks back we've now switched to working directly in Linux since this project seems to have been abandoned or not made compatible with Windows 11 yet.

It's been about a week now and it still works. Even opening the distro through the File Explorer seems much faster now. Previously it was working only after a restart for a few minutes and then it was stopping, and even in the small period when it was working, it was taking a second or two to list the root directory, which now happens immediately as listing a windows path. Hopefully it remains working now. I will let you know if something goes wrong again. I'm on build 22000.527 if that matters.

I'm on build 22000.527 if that matters.

I've a clean install that I can reset on a laptop, it's always up to date with stable. Right now it's on 22000.493. I will check back on this in a few months to see if they've integrated the fixes you seem to have. Thanks for the feedback.

i also meet this quqestion.on windows 22000.527 and ubuntu 20.04

i also meet this quqestion，win10 19044.1741. The hint is “You may not have permission to use network resources”

I'm on build 22000.527 if that matters.

I've a clean install that I can reset on a laptop, it's always up to date with stable. Right now it's on 22000.493. I will check back on this in a few months to see if they've integrated the fixes you seem to have. Thanks for the feedback.

I'm now checking back, tried a new fresh install and update of Windows 11 on a new machine with build 22000.739 and WSL kernel version <IP_ADDRESS>
Still same error, There's still no way to run WSL on Windows 11 and have interactivity with Windows or networking.
WSL has been abandoned for very very long time now. Almost a year, and I really wish at some point soon it will be usable for us running Windows 11 and not just Windows 10.
It's an incredibly nice tool when working with Windows specific stuff in parallel, and would add value to the Windows 11 ecosystem.

I dont know maybe it will work for u guys but It helped me to enter the file system simply by typing in the start menu \wsl$ and then pressing the execute command, if it helped, I would be glad :)

I have had the same problem in my wsl2 environment, I fixed it by doing the following:

wsl --shutdown (from powershell with admin permissions
Disable and re-enable the wsl network adapter in the windows control panel
I restarted WSL from the terminal and it was solved by accessing explorer.exe. from the terminal

If it worked for you let me know :)

I'm trying to understand exactly what problems people are still having now, in the summer of 2022. The original statement is a bit stale (for example, nobody should have to install kernel updates before testing whether things work).
I am able to access files across the WSL/Windows boundaries in both Windows 10 and WIndows 11, as well as use networking on both, so if someone can summarize the current state of the problem, I can see if anything comes to mind that might be useful for you. Otherwise, it will at least leave other new readers with a better sense of the current nature of the problem. I'm a little hesitant to give any advice based on a problem description from 2020. The other posts have been helpful but have mostly been about things people have tried that sometimes have helped some people (but have not helped everybody) or information from folks saying they have similar issues, and so on, but it has been a while since anybody updated the actual problem statement. Does it present exactly the same symptoms as it did in 2020? If so, what are those symptoms, and do the original repro steps from the OP still cause those symptoms to appear? And what, specifically, does step viii of the repro mean? In other words, how is the user in step viii supposed to try to access \\wsl$\Ubuntu - from cmd.exe, from powershell.exe, from pwsh.exe, from Windows Explorer? What versions of Windows and cmd/PowerShell/pwsh cause the problems to occur? Are any versions of Windows exempt from the problem - if so, which one(s)? Does the problem only happen when trying to access a distribution root using the older "dollar-sign" syntax, as in \\wsl$\Ubuntu, or does it also appear if you try to view a path within that volume, as in \\wsl$\Ubuntu\home, or if you use the newer "localhost" syntax on Windows 11, such as \\wsl.localhost\Ubuntu or \\wsl.localhost\Ubuntu\home?
Those are the kinds of information that might be helpful to give us an idea of where to look and where not to look. Any takers? If I can get to where I can repro the issue, I might be able to find a fix for it, or at least an explanation.
Also, for what it's worth, while this must be extremely frustrating, I don't think that Microsoft has abandoned WSL. Not at all, in fact. We use it a lot at work, and it has become a key part of developer workflow around the world. Its ability to let people develop for Windows and Linux on a single workstation is really valuable, and the integrations in products like VS Code that let you do that seamlessly have become valuable enough in the dev community that Microsoft would have a high-priority problem on their hands if this were misbehaving for a large number of devs. The problem here is to figure out why it's misbehaving so badly for this group of people.

I'm not at work now, but this is what we tried last week.
There are at a minimum one reboot between each point.

Install windows 11 from iso
Make a full update, many restarts
Add the windows feature
Run 'wsl update'
Install Ubuntu with 'wsl install ubuntu' or whatever the list called it, maybe Ubuntu 22.04
Run 'wsl'
Start code from ~/
Run 'explorer.exe .', <¬ here's one error, "you can't access this network resource"

We can access \wsl$... in explorer, but can't run windows apps from wsl that opens a wsl path. I wish I remembered the path it uses from wsl, it's not \wsl but something like \wsl.localhost instead.
Also, using explorer.exe .  in wsl might work first time, we've had false moments of happiness when restarting wsl service and so on, it lasts for maybe a minute.

Thanks!
I'm not at work either. It is the weekend! We might have a cadence where you folks will post things during the week, and if (that's a big if) I have something to contribute, that might wait until the weekend.
So this is a clean Windows 11, fully patched. Then you run wsl --update, which means you are on the current WSL Linux kernel (my laptop says it is <IP_ADDRESS> in wsl, or <IP_ADDRESS>-microsoft-standard-WSL2 in uname).
If you could verify the Ubuntu version, that would help. I have all 20.04 currently on my own laptop. I will install 22.04 (Ubuntu 22.04.1 LTS) and see what happens.

I can confirm that it works the same with Ubuntu 20.04 and Debian, we've had this problem since windows 11 release when 22.04 wasn't released yet. I don't think the dist matters. Also,  yes code is vscode, but I don't need to run it for the problem to happen. It has been how we tested, but I've tried reinstalling without installing the remote vscode before the problem occurred. In my eyes it just looks like the rights to wsl.localhost doesn't work properly and should be wsl$ instead, but I've no idea how to force wsl to use another network path.

Thanks @TTSKarlsson. Currently, I am unable to repro. this. This is what I did. First I ran through the steps in WIndows 10, and then I did the same things in Windows 11.
The first thing I did was to install Ubuntu 22.04.1 LTS from the Windows Store on both laptops, as it was not installed on either.
For Windows 10, in addition to performing the steps that are in the large code block below, I also opened locations in Windows Explorer and from pwsh.exe that had the \\WSL$ "hostname" prefix. Remember, wsl.localhost "hostname" is not available until Windows 11 - or at least it's not available in my build of Windows 10, which is 21H2 / 19044.1826).
Installation successful!
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

Welcome to Ubuntu 22.04.1 LTS (GNU/Linux <IP_ADDRESS>-microsoft-standard-WSL2 x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage
/etc/update-motd.d/50-landscape-sysinfo: 17: cannot create /var/lib/landscape/landscape-sysinfo.cache: Permission denied
7 updates can be applied immediately.
To see these additional updates run: apt list --upgradable

This message is shown once a day. To disable it please create the
/home/cleonard/.hushlogin file.

cleonard@LTTC-74HJCK3:~$ # THIS IS ON WINDOWS 10

cleonard@LTTC-74HJCK3:~$ # we expect this to work:
cleonard@LTTC-74HJCK3:~$ ls -ald /mnt/c/Program*
drwxrwxrwx 1 cleonard cleonard 512 Aug 13 15:39  /mnt/c/ProgramData
dr-xr-xr-x 1 cleonard cleonard 512 Aug  5 08:50 '/mnt/c/Program Files'
dr-xr-xr-x 1 cleonard cleonard 512 Aug  2 11:30 '/mnt/c/Program Files (x86)'

cleonard@LTTC-74HJCK3:~$ # it appears that the following is currently working for me:
cleonard@LTTC-74HJCK3:~$ explorer.exe .
cleonard@LTTC-74HJCK3:~$ # ... and I have run it from / and other directories
cleonard@LTTC-74HJCK3:~$ # ... I'm not going to post screenshots b/c that would bloat the post,
cleonard@LTTC-74HJCK3:~$ # ...   but will be happy to post any you want to see

cleonard@LTTC-74HJCK3:~$ # let's see if some others work:
cleonard@LTTC-74HJCK3:~$ notepad.exe ./.bashrc
cleonard@LTTC-74HJCK3:~$ # that did work

cleonard@LTTC-74HJCK3:~$ # let's try something more interesting...
cleonard@LTTC-74HJCK3:~$ #   since beyond compare is a Windows program, I have to give it file
cleonard@LTTC-74HJCK3:~$ #   references it understands, so I'll use \\wsl$ references. since
cleonard@LTTC-74HJCK3:~$ #   backslash is an escape character in bash, I will have to escape
cleonard@LTTC-74HJCK3:~$ #   those by doubling them up. let's see if this works...
cleonard@LTTC-74HJCK3:~$ /mnt/c/Program\ Files/Beyond\ Compare\ 4/BCompare.exe \\\\wsl$\\Ubuntu-22.04\\home\\cleonard\\.bashrc \\\\wsl$\\Ubuntu-22.04\\home\\cleonard\\.bash_logout

cleonard@LTTC-74HJCK3:~$ # it took me three tries, but that worked. terrible typing experience, though.
cleonard@LTTC-74HJCK3:~$ # it seems like single-quoting the filenames would be easier:
cleonard@LTTC-74HJCK3:~$ /mnt/c/Program\ Files/Beyond\ Compare\ 4/BCompare.exe '\\wsl$\Ubuntu-22.04\home\cleonard\.bashrc' '\\wsl$\Ubuntu-22.04\home\cleonard\.bash_logout'
cleonard@LTTC-74HJCK3:~$ # that _was_ much easier, though still no tab completion. blech.

cleonard@LTTC-74HJCK3:~$ # this might be the easiest way to run that particular command. it comes down to personal preference, I suppose.
cleonard@LTTC-74HJCK3:~$ alias bcompare='/mnt/c/Program\ Files/Beyond\ Compare\ 4/BCompare.exe'
cleonard@LTTC-74HJCK3:~$ bcompare $(wslpath -w ~/.bashrc) $(wslpath -w ~/.bash_logout)
cleonard@LTTC-74HJCK3:~$ # that also worked, yay

On to WIndows 11, I did exactly the same steps, except that I also accessed folders from both WIndows Explorer and pwsh.exe using the wsl.localhost "hostname" prefix. The results are basically identical, but here's the code block for that.
Installation successful!
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

Welcome to Ubuntu 22.04.1 LTS (GNU/Linux <IP_ADDRESS>-microsoft-standard-WSL2 x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage
/etc/update-motd.d/50-landscape-sysinfo: 17: cannot create /var/lib/landscape/landscape-sysinfo.cache: Permission denied
7 updates can be applied immediately.
To see these additional updates run: apt list --upgradable

This message is shown once a day. To disable it please create the
/home/chris/.hushlogin file.

cleonard@caerdydd:~$ # THIS IS ON WINDOWS 11

chris@caerdydd:~$ # we expect this to work:
chris@caerdydd:~$ ls -ald /mnt/c/Program*
drwxrwxrwx 1 chris chris 512 Aug  9 15:55  /mnt/c/ProgramData
dr-xr-xr-x 1 chris chris 512 Jul 11 16:24 '/mnt/c/Program Files'
dr-xr-xr-x 1 chris chris 512 Jul 15 21:20 '/mnt/c/Program Files (x86)'

chris@caerdydd:~$ # it appears that the following is currently working for me:
chris@caerdydd:~$ explorer.exe .
chris@caerdydd:~$ # ... and I have run it from / and other directories
chris@caerdydd:~$ # ... I'm not going to post screenshots b/c that would bloat the post,
chris@caerdydd:~$ # ...   but will be happy to post any you want to see

chris@caerdydd:~$ # let's see if some others work:
chris@caerdydd:~$ notepad.exe ./.bashrc
chris@caerdydd:~$ # that worked, but took longer to load on Windows 11 than it did on Windows 10.
chris@caerdydd:~$ # that might or might not be a repeatable result - i'm not going to check things like that now.

chris@caerdydd:~$ # on to the Beyond Compare tests!
chris@caerdydd:~$ # these all worked just like they did on Windows 10.
chris@caerdydd:~$ /mnt/c/Program\ Files/Beyond\ Compare\ 4/BCompare.exe \\\\wsl$\\Ubuntu-22.04\\home\\cleonard\\.bashrc \\\\wsl$\\Ubuntu-22.04\\home\\cleonard\\.bash_logout
chris@caerdydd:~$ /mnt/c/Program\ Files/Beyond\ Compare\ 4/BCompare.exe \\\\wsl$\\Ubuntu-22.04\\home\\chris\\.bashrc \\\\wsl$\\Ubuntu-22.04\\home\\chris\\.bash_logout
chris@caerdydd:~$ /mnt/c/Program\ Files/Beyond\ Compare\ 4/BCompare.exe '\\wsl$\Ubuntu-22.04\home\chris\.bashrc' '\\wsl$\Ubuntu-22.04\home\chris\.bash_logout'

chris@caerdydd:~$ alias bcompare='/mnt/c/Program\ Files/Beyond\ Compare\ 4/BCompare.exe'
chris@caerdydd:~$ bcompare $(wslpath -w ~/.bashrc) $(wslpath -w ~/.bash_logout)

So for the time being, I am in the "it's working so far" group. I will try to get my dotfiles and git repos ported over to 22.04.1 in the next week or so in order to use it as my daily repo and see if it will break for me.
Let me know what I may have missed, misunderstood, or left out in trying to recreate the problem. Thanks!

I would say it works for you, at least if you let the wsl run for quite some time and it still worked.
I'll do the same, when I'm at my test setup, follow the same format and post results here. I personally really want this to work.

Ok, I'm in position. I didn't reinstall windows this time as it's newly installed anyway. I uninstalled previous Ubuntu before doing this.

I logged out from wsl for 1 minute here.

I can right now access \\wsl.localhost\Ubuntu from an open explorer window. And right now I can't run any executables from windows inside wsl, after wsl being (automatically) stopped one time. My experience is that \\wsl.localhost will keep working but \\wsl.localhost\Ubuntu will be denied access after a while, this hasn't happened yet here though.

For completeness I also installed 22.04 from the store with the graphical installer.

I suspect enough time has passed for \wsl.localhost to be denied access, so I'm going back to Ubuntu 20.04

And I get the same denied message.

In an open explorer window, I can access wsl.localhost

But not any of the wsl roots

Restarting the computer doesn't help, I've had success with restarting the entire service but this happens after a few minutes again.

My network setup to this machine is nothing weird, a normal router with normal dns on a 200/200 fiber connection. No proxies or vpns.

There are network shares on the network, like ssh and samba, but they shouldn't change this machines settings in any way.

@cleonard-godaddy , Do you need more info?

I've had the same issue, starting with today. Yesterday I still could access all network drives from different distributions, now they're all completely gone, restart doesn't help. I already tried some of the things offered here, but no success. I think about restoring a complete system backup from 4 weeks ago and not doing any updates from then on, but that's also quite risky.

@TTSKarlsson, thanks for the nudge. I don't think I need more info. My "problem" is that I still cannot reproduce the problem on Windows 10, with either Ubuntu 20.04 LTS or 22.04 LTS.
Actually, I do have one question: what Windows build were you on when you sent your last set of comments?
And @Ninili, what version and build of WIndows, WSL version(s), and Linux distribution versions are you running?
You probably know this, but just in case it helps you or someone else:

the Windows command winver is one way to find your WIndows build
running wsl -l -v from Powershell will show the WSL version of each of your distribution installations
running cat /etc/*release* inside each distribution is a nice portable hack to get lots of distro version information

And @Ninili, what version and build of WIndows, WSL version(s), and Linux distribution versions are you running?
You probably know this, but just in case it helps you or someone else:

the Windows command winver is one way to find your WIndows build
running wsl -l -v from Powershell will show the WSL version of each of your distribution installations
running cat /etc/*release* inside each distribution is a nice portable hack to get lots of distro version information

Actually I could resolve the issue by calling "explorer.exe ." from within the wsl, from my home path like @onomatopellan suggested! I didn't even know you could just call explorer.exe from within the WSL. But this kind of "broke the barrier".
That's why I also deleted my comment.  And it seems I have to do it again after every boot now. But it's a workaround I can live with.

Any updates or workarounds on this issue? Experiencing the same problem with WSL 2, Ubuntu 22.04.1 and Windows 11 22h2 (Build 22621.521)

PS C:\Windows\System32> wsl --version
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.42
MSRDC version: 1.2.3401
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.525

I tried this again with a new install, and now it works. I've revisited a couple of days to make sure it is stable and it keeps on working, which is a first since the launch of Win11 one year ago. I'll do the same on a couple other machines again now, and if it works there too I won't come back to this thread.

Working = No access denied to wsl.localhost and can run windows executables with wsl directories as arguments.

Could you solve the issue?

So far no good.

Unfortunately same here with wsl2.

Any updates or workarounds on this issue? Experiencing the same problem with WSL 2, Ubuntu 22.04.1 and Windows 11 22h2 (Build 22621.521)

Could you solve the issue?

I was able to resolve my issue by editing the registry entries HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order and HwOrder and making sure P9NP is at the start of those comma separated lists.
Source: https://github.com/microsoft/WSL/issues/4027#issuecomment-496628274

I am having this issue, but my HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\{Order,HwOrder}\ProviderOrder have the P9NP:
P9NP,RDPNP,LanmanWorkstation,webclient

You can also set the regex order directly in the windows interface so that it will persist after reboot: https://learn.microsoft.com/en-us/troubleshoot/windows-client/deployment/network-provider-settings-removed-in-place-upgrade


Add tape drive support to s2pdump

In order to help with replacing a real tape drive by s2p, a tool that converts all blocks and filemarks on a tape to the respective SIMH data and vice versa is needed. s2pdump shall be extended for this purpose.
Strategy to use:

There can be blocks of any size or filemarks.
Start with reading a block of an impossibly high length.
The drive will either report that the actual block length is different, and tells you the real size. Or there is no block but a filemark.
Remember the size as default size for subsequent read operations, in order to avoid unnecessary operations dealing with wrong block sizes.
In case of a filemark, create a SIMH tape mark and continue.
In case of a block, read it with its known size and create a SIMH data record of this size.
In case of a bad block, space back, retry and create the respective SIMH record.
Simulate bad blocks with s2ptool, this avoids the need for a real tape with bad blocks.

@pacjunk In the issue_113 branch there is an early version of this s2pdump extension. Restoring a tape is not yet supported, but converting a tape to a SIMH file works when running it against s2p like this:
s2ptool -s "-i 0 simh.tap" -c s2pdump -a "-i 0 -f /tmp/test.tap"

This will launch s2p with simh.tap as image file, and then run s2pdump against it. No Pi is required for this, because everything happens in memory. I will test with a real tape drive later, as good as this is possible with my drive.

Merged into issue_112 branch.

Must be doing something wrong...
pi@PiSCSI:~/scsi2pi/cpp/bin $ s2pdump -i 3 -f test.tap
----------------------------------------
Board (initiator) ID is 7
----------------------------------------
Checking SCSI target ID:LUN 3:0

INQUIRY product data:
Vendor:               'SONY    '
Product:              'SDT-5000        '
Revision:             '3.02'
Device Type:          Sequential Access
SCSI Level:           SCSI-2
Response Data Format: SCSI-2
Removable:            Yes
Error: Invalid device type for SCSI dump/restore, supported types are DIRECT ACCESS, CD-ROM/DVD/BD/DVD-RAM and OPTICAL MEMORY
Error: Can't get device information

As far as I can tell this is not the s2pdump from the issue_112 branch.

I'm on the 112 branch, git pull says nothing to do. make s2pdump says nothing to do.

This is what's in the issue_1122 branch:
        cerr << "Error: Invalid device type for SCSI dump/restore, supported types are DIRECT ACCESS,"
            << " CD-ROM/DVD/BD/DVD-RAM, OPTICAL MEMORY and SEQUENTIAL access" <<

I don't know what's wrong, but please re-build after a "make clean".

I did a make clean, also checked out develop, then back to issue_112. Rebuilt (with warnings), and same results.

Please re-check your commit ID. The current one for issue_112 is 21554289.

No thats the path to the executables.
How do I force it to re-download?

Re-download? I'm afraid I'm not sure what you mean. In your branch with the compiled sources, run ./cpp/bin/s2dump. Or ./bin/s2pdump, depending on which hiearchy you are.

Yes, I do all that. Something is wrong. I have done another "git clone" and started again.

The current issue_112 commit ID is 21554289.

No, same results. Too late now, I will try again tomorrow...

OK. Note that because issue #112 is closed I will switch back to the issue_111 branch and will update it later today. Tomorrow please check out/update the issue_111 branch.

My commend seems to have disappeared, so I will write it again...
I tried dumping the tape, but it only gets to the first file mark (dump file has contents up to this point). Log attached:
dump.txt

Is this with the current issue_111 sources? Please ensure that you are not using something older.

OK. I don't know yet what's wrong, I am going to investigate.

I guess this is a timeout issue, but this has not yet been logged. I have update issue_111 with better logging and a longer timeout. Please retry after updating and re-compiling.

That is a lot better, although I think there are still timing issues.
On Trace logging, the dump completed.
On info level logging, it died after about 5000 blocks with:
[error] [s2pdump] STATUS phase failed
Error: INFORMATION field is not valid

Is it possible to have some sort of progress indicator (e.g. a dot per block) rather than just no output until the end?
Also, if I do a Ctrl-C during the program nothing happens. Because there is no progress indication I don't know if its still going or hung. If I eject the tape, it still did not die.

Also the dump file is almost exactly double the size expected. When I list the tape in the OS, the files appear twice. The files look OK, but two copies!

Two copies? s2pdump definitely only reads the tape once. Is it possible that you ran s2pdump twice and data were appended? But even this I cannot reproduce. Can you reproduce it?
Everything else I will most likely address as part of https://github.com/uweseimet/scsi2pi/issues/115 later.  "STATUS phase failed" indicates that there is a bus signal issue. I may have to improve the logging to see more. Is this reproducable?
In order to help with #111, as far as required, the current state of s2pdump should be fine, though. This is why I would like to deal with #111 again, which is related to the core functionality.

I think I now what might have happened. I will rebuild my "master" tape.
The error message only occurs on the "info" log level, not "trace". I assume the extra logging on trace slows it down just enough to get through.

I have successfully dumped and restored tapes using s2pdump. I will hopefully get back to some of the testing tomorrow.


docs: Translate findDOMNode

Fixes #439 and closes #510
Description
This PR adds translation to findDOMNode page, continuing @afrianjunior's effort.
Translate the findDOMNode page.
Page URL:

🌍: https://react.dev/reference/react-dom/findDOMNode
🇮🇩: https://id.react.dev/reference/react-dom/findDOMNode

Hi @resir014 & @zainfathoni,
I have translated the findDOMNode page, can you please review this PR?
Please let me know if you have any questions or feedback. Thank you!

Hi @resir014,
I have patched this PR as requested, can you please review again? Thank you!

Hi @resir014,
I have updated the PR as requested, can you please review again?
Thank you!


handled all four histogram requests but not tested yet

NOTE: merges into add-data-adapter not main!
Following the newly updated API specs here: https://veupathdb.github.io/EdaDataService/api.html
I made adapter methods for all four histogram endpoints.
I don't think it's going to work in practice because the responses will not always have
data[].overlayVariableDetails or data[].facetVariableDetails in them, so the io-ts validator needs to be aware of that.
(and I just saw that the latter is an array - will fix this ASAP)

@bobular I pushed a commit that addresses the optional properties in HistogramResponseData.


Docker Store cloud-agent:  Remove 'runsvinit' from image

Per the Docker Store feedback/report, Docker do not approve of runsvinit.

Appears to use runsvinit (process manager utility).  The processes are spawned from the same binary within the image.  Please consider if there are architecture changes that could reduce this extra layer of indirection.

See also: https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/#/each-container-should-have-only-one-concern

To be clear, this is only a requirement for the Docker Store image. The normal Scope image still needs it (until we split the images if we do) since it runs both the app and probe processes.

This is s requirement of #2262

I don't think removal of runsvinit is a requirement. Not using it is. i.e. it should be ok to have it in the image as long as it's not being used.


Clarify interval

https://nuxt-security.vercel.app/documentation/middleware/rate-limiter#interval specifies a default of 300000. Are those milliseconds? It would be great if there was a better explanation on how to use this property :raised_hands:

Added in https://github.com/Baroshem/nuxt-security/pull/262/commits/f0f1357f08b4a5a765a3af64931fed0f1af3bf1d :)
Will be released next week with the upcoming 1.0.0-rc.3 version

Perfect, thanks! That was quick :fire:


[feature] Enhance Next.js README

When following along with the readme for the Next.js remote app, the instructions are missing the following:

where to call ModelManager.initializeAsync()
how to set up appropriate rewrites for /.model.json and /content/:path*
how to implement the AEMResponsiveGrid component

When comparing this to the aem-guides-wknd-graphql tutorial, I am able to get it close to working using Next.js, but within the AEM environment itself, I'm running into problems where:

I cannot drag and drop components in my responsive grid (I see nodes added to the jcr, but nothing renders on the screen).
running into issue with rewrites (possible infinite loop). I notice this model called over and over (http://localhost:4502/content/wknd-app/us/en/home/jcr:content/root/responsivegrid.model.json)
not properly initializing the model manager (I tried calling this in _app.tsx but it doesn't seem to work)

If we could get a working example of a Next.js implementation that would be great.
Here is my pages/_app.tsx file (assuming this is the right place to call the ModelManager)
import { ModelClient, ModelManager } from '@adobe/aem-spa-page-model-manager';
import type { AppProps } from 'next/app';

const modelClient = new ModelClient(process.env.NEXT_PUBLIC_AEM);

ModelManager.initializeAsync({
    modelClient
});

export default function MyApp({ Component, pageProps }: AppProps) {
    return (
        <Component { ...pageProps} />
    );
}

In my pages/index.tsx I am adding the AEMResponsiveGrid component like so:
export default function Home() {
    return (
        <AEMResponsiveGrid
            pagePath="/content/wknd-app/us/en/home"
            itemPath="root/responsivegrid" />
    )
}

NOTE: This produces the infinite loop I mentioned above.

Here are some screenshots of what I see in the console:

I am handling rewrites in my next.config.ts like so:
async rewrites() {
    return [
        {
            source: '/content/:path*',
            destination: '/api/proxy/:path*'
        },
        {
            source: '/.model.json',
            destination: '/api/proxy/.model.json'
        }
    ]
}

Produces the following error within the AEM environment
Uncaught (in promise) TypeError: Cannot read property 'includes' of undefined
    at resolveRewrites (resolve-rewrites.js?3fb8:7)
    at Router._callee$ (router.js?7a5c:132)
    at tryCatch (runtime.js?96cf:63)
    at Generator.invoke [as _invoke] (runtime.js?96cf:293)
    at Generator.eval [as next] (runtime.js?96cf:118)
    at asyncGeneratorStep (asyncToGenerator.js?a954:3)
    at _next (asyncToGenerator.js?a954:25)

I was able to get the images to pull from the DAM and use the next/image component with the rewrites.

@devongovett Would you be able to assist me with this?

@sharanyavinod Would you be able to assist me with this?

@Kinbaum Could you share your code package as well if possible, please?

I am just reusing the WKND app that has the remotenextpage. I created a new page under /content/wknd-app/us/en using that resource type. Then in my next app, I’ve satisfied all of the requirements like creating the /api/getNextProps endpoint and assets-manifest.
I’ve essentially shared all of my files from my next app. There is only a single page with a responsive grid component.  I’ll put together a zip so you can see.

@sharanyavinod Here is a stripped down version that shows the issue when connecting to AEM.
Code Sample.zip
Run yarn to install and yarn dev to run the app. Should load on localhost:3000
Once that is done, on the AEM side under the wknd-app folder (using the graphql tutorial) create a page, select the Next.js template and create the page:

After running through all of those steps, open up your developer tools and the open the page just created. You should immediately begin seeing errors like the following:

The one that specifically stands out to me is this one:
Uncaught Error: Edit context could not be fetch due to an error in the edit context servlet

@sharanyavinod have you had the chance to look; any thoughts?

@Kinbaum Regarding the query-

I cannot drag and drop components in my responsive grid (I see nodes added to the jcr, but nothing renders on the screen).

For container components, the child components need to be mapped in order for them to be rendered. I see that you have MapTo within the components itself - for eg: in the AEMText component. However, since this component isn't used, the mapping never gets executed. You could either have a common file which imports all components and performs the mappings and import them within the parent component OR just import/map possible child components within the container.
Some References:
https://github.com/adobe/aem-guides-wknd-graphql/blob/feature/spa-editor/react-app/src/App.js#L15
https://github.com/adobe/aem-guides-wknd-spa/blob/React/latest/ui.frontend/src/index.js#L30
Regarding the remaining errors, will take a closer look and get back to you. Thank you for the detailed descriptions and snippets!

Thanks @sharanyavinod importing the components in my _app.tax file allowed them to show up in/outside of AEM. However in AEM, I still cannot edit due to that error.
Also another thing I noticed is that SSR doesn’t seem to be working using these “MapTo” components. Any thoughts on that?

@Kinbaum Thank you for bringing this issue to our attention. Please use the newly released v1.3.8 of spa.project.core in your AEM project to resolve the issue.
For fetching the model.json you can use pass the AEM host to ModelClient during initialization as you've illustrated in the snippets above. The location of initialization is also as already done. I'll add this to the docs for future clarity.
Regarding SSR issues related to MapTo, if unrelated to the current issue, could you please create a separate issue with the corresponding details?

Thank you @sharanyavinod. I have created a new issue #40 to track the SSR problem.