search

microsoft / WSL

Issues found on WSL
https://docs.microsoft.com/windows/wsl
MIT License
17.45k stars 822 forks source link

Can't access WSL P9 Network Linux Filesystem Share #5307

Closed phippg closed 5 months ago

phippg commented 4 years ago

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: 19112604462750000 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: 440795202120 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: 19112604462750000 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: dm-devel@redhat.com [ 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 (1590952004) [ 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 ```
K2ouMais commented 3 years ago

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.

Kufat commented 3 years ago

@K2ouMais Most of us can see the distro name in \wsl$\ as seen here: image but are unable to actually open it.

K2ouMais commented 3 years ago

@Kufat

Please open powershell and type wsl -l -v.

Please put the output here.

Kufat commented 3 years ago 
PS C:\Users\Kufat> wsl -l -v
  NAME      STATE           VERSION
* Ubuntu    Running         2
K2ouMais commented 3 years ago

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".

Kufat commented 3 years ago

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.

K2ouMais commented 3 years ago

I have some more questions...

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.

  1. wsl --shutdown
  2. wsl --export Ubuntu C:\WSL\Ubuntu-20.04.tar
  3. wsl --unregister Ubuntu
  4. 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.

phippg commented 3 years ago

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

EDIT As for your questions: Distro was installed from the Windows Store and it was installed via PowerShell.

florent-izypay commented 3 years ago

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

And as stated above, this problem does not seem to be related to the distro itself, since I encountered the same on a fresh Ubuntu distro as well.

Kufat commented 3 years ago

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.)

Kufat commented 3 years ago

Is there any event logging for the P9 subsystem/feature/service/whatever it is? 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.

Priyansh121096 commented 3 years ago

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:

The things that do work:

Any help will be hugely appreciated.

Regards, Priyansh

snizemic commented 3 years ago

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.

whaaaley commented 3 years ago

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.

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
Kufat commented 3 years ago

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.

kzos commented 3 years ago

@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

Kufat commented 3 years ago

@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. :)

kzos commented 3 years ago

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/

kzos commented 3 years ago

@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.

Kufat commented 3 years ago

windows+r \\wsl$\Ubuntu\home\kufat "The specified path does not exist" even though 

kufat@Phoenix:~$ pwd
/home/kufat
rescenic commented 3 years ago

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. a Lets test. b Works. c

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.

phippg commented 3 years ago

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.

snizemic commented 3 years ago

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 didn´t help. :-(

I was wondering if there could be a problem with the windows firewall settings or something like that?

manierim commented 3 years ago

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.

florent-izypay commented 3 years ago

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 ?

Kufat commented 3 years ago

@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 commented 3 years ago

@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 test cases scope. My misbehaving Windows installation is also a long-living, multi-upgraded instance: Vista ->7 -> 8 -> 8.1 -> 10 + every updates from 10.

michael-imbeault commented 3 years ago

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

whaaaley commented 3 years ago

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. Though, that isn't to say it's not something to do with a buggy registry.

Vpvladimirov commented 3 years ago

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

Hope it helps.

Spongman commented 3 years ago

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
Kufat commented 3 years ago

@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.

Spongman commented 3 years ago

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

a4ex commented 3 years ago

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

Christophoclese commented 3 years ago

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.

K2ouMais commented 3 years ago

What does that P9NP key does?

I am trying to understand how this is a fix and how you found it?

Christophoclese commented 3 years ago

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

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

onomatopellan commented 3 years ago

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

phippg commented 3 years ago

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

ghost commented 3 years ago

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.

aston3e commented 3 years ago

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

phippg commented 3 years ago

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

rajesh221b commented 3 years ago

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

phippg commented 3 years ago

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.

andnig commented 3 years ago

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

phippg commented 3 years ago

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

andnig commented 3 years 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.

phippg commented 3 years ago

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.

SunJun8 commented 2 years ago

image stop here

System Info:

Version Windows 11 Pro
Version 21H2
Installation date ‎2021/‎10/‎15
Operating system version 22000.348

.wslconfig

[wsl2]
kernel=C:\\Users\\win10\\Kernel\\bzImage
memory=6GB # Limits VM memory in WSL 2 to 4 GB%

wsl.conf

# Enable extra metadata options by default
[automount]
enabled = true
root = /mnt/
options = "metadata,umask=22,fmask=11"
mountFsTab = false

[interop]
appendWindowsPath = false
yaofahua commented 2 years ago

This is my case, hope can help you .

It's OK when using win10, but after ugrade to win11, I met the same problem.

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

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

1641014066(1)

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.