canonical
Native mounts do not work on Windows 11 with Hyper-V
To Reproduce Create some folder on disk, make sure your account is not explicitly listed - just be part of one of the allowed accounts that have full access privilege, then try to mount it into a VM using Powershell terminal with commands such as
multipass mount -t native "D:\Code" kub-control-01`:/home/ubuntu/test
Getting error:
mount failed: The following errors occurred:
error mounting "/home/ubuntu/test": cannot access "D:\Code"
Now add your account to the list of allowed users explicitly, make sure you have full access privilege checkbox checked in the Windows Explorer folder permissions dialog.
Now it will ask for password, then error:
Please enter your user password to allow Windows mounts:
mount failed: The following errors occurred:
error mounting "/home/ubuntu/test": Error: mount error: could not resolve address for desktop: Unknown error
Attached the events.
Expected behavior What did you expect to happen?
I want Multipass to be able to mount folders into the VM, as documented.
Logs
In the Event Log before adding myself to allowed users explicitly,
I can see Multipass issues Powershell command (Get-Acl 'D:\Code').Access | ?{($_.IdentityReference -match 'roman') -and ($_.FileSystemRights -eq 'FullControl')}
I am the administrator, but my login name is not explicitly listed in the ACL, instead the access is via group. I am also the owner of that folder.
So it seems like the command does not return my login, and Multipass believes I don't have access to that folder.
Then after I add myself explicitly, there's a bunch of events related to smb share, which I attached here.
Additional info
- OS: Windows 11 Pro 24H2, OS Build 26100.4351
- CPU architecture or model: 64bit, Intel Core i9-13900K
- multipass 1.15.1+win, multipassd 1.15.1+win
-
Name: kub-control-01 State: Running Snapshots: 0 IPv4: 172.27.94.147 Release: Ubuntu 24.10 Image hash: 8446856f1903 (Ubuntu 24.10) CPU(s): 4 Load: 0.00 0.03 0.02 Disk usage: 1.9GiB out of 9.6GiB Memory usage: 346.1MiB out of 2.8GiB Mounts: --
Name: kub-control-lb State: Running Snapshots: 0 IPv4: 172.27.91.27 Release: Ubuntu 24.10 Image hash: 8446856f1903 (Ubuntu 24.10) CPU(s): 2 Load: 0.00 0.00 0.00 Disk usage: 1.9GiB out of 4.8GiB Memory usage: 184.4MiB out of 380.0MiB Mounts: --
- ```
multipass get local.driver
hyperv
Additional context Looks like two piles of issues here,
- the logic to verify file access is not documented, and doesn't look correct either
- problems with mounting the folder
One more issue here,
since Multipass does not allow supplying that password from the command line, it basically makes non-interactive scripting of the mounts on Windows impossible. I can't bring up a family of VMs on my workstation in unattended mode, have to constantly monitor interactive console for password prompts.
Few more bits of info: the VMs are not attached to the bridged network, and I also didn't turn off my firewall, neither did I change the public/private setting on my networks. SSHFS ("classic"?) mounts work just fine.
I don't use bridged network to avoid any interference with changing WiFi, VPN etc. That helped on Mac, where I already have this 7-machine cluster automated using Multipass and the same set of Powershell scripts.
Instead of turning Windows firewall off or switching public/private designation, I created two rules, for multipass and multipassd, allowing all inbound traffic from the VM address range.
Just FYI, because it does not look relevant to the "could not resolve address" problem.
Hi @romanpolunin,
Thank you for reporting these issues. I was able to recreate the user permission issue but I'm unable to recreate the address revolution issue. Can you shell into the instance after the failure and run sudo dmesg? It may contain more detailed logs of why the mounting failed.
@Sploder12 I don't see anything specific in dmesg, but you might also be interested in the output of journalctl, I copied the relevant lines. Still no obvious errors though.
@Sploder12 and obviously, ping desktop from a multipass shell fails to resolve. However ping 172.20.80.1 works just fine. This is definitely Multipass-specific IP of the host, not available from WSL2. ip addr show gives this:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 52:54:00:ed:db:14 brd ff:ff:ff:ff:ff:ff
inet 172.20.91.224/20 metric 100 brd 172.20.95.255 scope global dynamic eth0
valid_lft 85192sec preferred_lft 85192sec
inet6 fe80::5054:ff:feed:db14/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
@Sploder12 also FYI, this is the network modification script I applied on this VM
# 1. Update system
cat <<MODS | sudo tee /etc/modules-load.d/otherstuff.conf
overlay
MODS
sudo modprobe overlay
# Sysctl params for networking
cat <<SYSCTL | sudo tee /etc/sysctl.d/otherstuff.conf
net.bridge.bridge-nf-call-iptables = 1
net.bridge.bridge-nf-call-ip6tables = 1
net.ipv4.ip_forward = 1
SYSCTL
sudo sysctl --system
# 3. Configure network with static IP
echo 'options ipv6 disable=1' | sudo tee /etc/modprobe.d/disable-ipv6.conf
sudo sysctl -p
NETWORK_CONFIG="
network:
version: 2
renderer: networkd
ethernets:
default:
set-name: eth0
"
echo "$NETWORK_CONFIG" | sudo tee /etc/netplan/99-custom-network.yaml
sudo chmod 600 /etc/netplan/99-custom-network.yaml
sudo chown root:root /etc/netplan/99-custom-network.yaml
@Sploder12 and here's what I get for 'ping desktop.lan' from multipass box, note IP address is picked up from my WiFi interface on the host. This is probably irrelevant, so just an FYI.
PING desktop.lan (192.168.1.179) 56(84) bytes of data.
64 bytes from host.docker.internal (192.168.1.179): icmp_seq=1 ttl=127 time=0.215 ms
64 bytes from host.docker.internal (192.168.1.179): icmp_seq=2 ttl=127 time=0.195 ms
64 bytes from host.docker.internal (192.168.1.179): icmp_seq=3 ttl=127 time=0.814 ms
64 bytes from host.docker.internal (192.168.1.179): icmp_seq=4 ttl=127 time=0.211 ms
Hi @Sploder12, how else could we follow this up? I would like to understand if there is actually a Multipass issue involved beyond #4224.
Hi @romanpolunin, I am sorry to hear that. Are you having the same output as you mentioned before?
Please enter your user password to allow Windows mounts: mount failed: The following errors occurred: error mounting "/home/ubuntu/test": Error: mount error: could not resolve address for desktop: Unknown error
Or a different one?
If the error is the same, it looks like bad hostname resolution. You cannot ping your hostname from inside the multipass shell, but I was able to do so. Could you try to run echo "172.20.80.1 desktop" | sudo tee -a /etc/hosts within the VM (or echo "172.20.80.1 desktop" | sudo tee -a /etc/cloud/templates/hosts.debian.tmpl) and see if the error persists? Alternatively you could also share how /etc/hosts looks like in your multipass VM. Although the mount succeeded (according to journalctl), not being able to resolve the hostname is odd. You can also try nslookup desktop instead of pinging to check for resolution.
It is also possible that disabling ipv6 in networking interferes with hostname resolution. In your script you also mention that you are setting a static IP, which is not shown in the script. If you are indeed setting said IP, make sure to check /etc/netplan/99-custom-network.yaml has the proper DNS settings or that /etc/resolv.conf is correct.
I have managed to use native mounts (after running the mount command twice), so I have not observed desktop address problem. From additional research, since the mount within the VM succeeds according to the journalctl.txt you shared, the bad hostname resolution could have happened on the windows side. Could you check your NetBIOS, SMB ports (445, 139) in the firewall and Hyper-V switch type?
NetBIOS:
Get-NetAdapter | Get-NetAdapterBinding | Where-Object {$_.ComponentID -like "*netbios*"}
Hyper-V switch type:
Get-VMNetworkAdapter -VMName "kub-control-01" | Select-Object Name, SwitchName, MacAddress
Get-VMSwitch | Select-Object Name, SwitchType, NetAdapterInterfaceDescription
Firewall/SMB:
Get-NetFirewallRule | Where-Object {$_.DisplayName -like "*File and Printer Sharing*"} | Select-Object DisplayName, Enabled, Profile, Direction
Test-NetConnection -ComputerName localhost -Port 445
Test-NetConnection -ComputerName localhost -Port 139
If you are observing the earliest error you reported, there is currently a Hyper-V refactor in progress that should fix the error.
Before I add myself to the ACL list on that folder explicitly (I am an Administrator, but don't have explicit permissions): same error as before for that case, it says 'cannot access xxxyyyzzz'
And it still asks for password in that first case - I need it to accept the password from the command line, or somehow integrate the current process auth context.
After I add myself to ACL explicitly, the error is new:
After executing echo "172.20.80.1 desktop" | sudo tee -a /etc/hosts within the VM, the error is the same, timeout.
/tmp/.smb_credentials does not exist on the VM
dmesg returns the following:
[ 4.298729] EXT4-fs (sda1): resized filesystem to 1048315
[ 5.220079] loop0: detected capacity change from 0 to 8
[ 5.358305] kauditd_printk_skb: 111 callbacks suppressed
[ 5.358308] audit: type=1400 audit(1763486894.956:122): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/snapd/snap-confine" pid=1029 comm="apparmor_parser"
[ 5.361197] audit: type=1400 audit(1763486894.959:123): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=1029 comm="apparmor_parser"
[ 6.623010] TCP: eth0: Driver has suspect GRO implementation, TCP performance may be compromised.
[ 49.134491] hv_balloon: Max. dynamic memory size: 1024 MB
[ 388.493871] netfs: FS-Cache loaded
[ 388.518419] Key type cifs.spnego registered
[ 388.518429] Key type cifs.idmap registered
[ 388.518988] CIFS: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 (or even SMB3 or SMB2.1) specify vers=1.0 on mount.
[ 388.518989] CIFS: enabling forceuid mount option implicitly because uid= option is specified
[ 388.518990] CIFS: enabling forcegid mount option implicitly because gid= option is specified
[ 388.518990] CIFS: Attempting to mount //desktop/c53aa34d-5166-3461-b34a-f12291786b35_prodigious-pony:/home/ubuntu/test
[ 398.845688] CIFS: VFS: Error connecting to socket. Aborting operation.
[ 398.846105] CIFS: VFS: cifs_mount failed w/return code = -115
[ 706.069996] CIFS: enabling forceuid mount option implicitly because uid= option is specified
[ 706.069999] CIFS: enabling forcegid mount option implicitly because gid= option is specified
[ 706.070000] CIFS: Attempting to mount //desktop/c53aa34d-5166-3461-b34a-f12291786b35_prodigious-pony:/home/ubuntu/test
[ 716.282677] CIFS: VFS: Error connecting to socket. Aborting operation.
[ 716.282890] CIFS: VFS: cifs_mount failed w/return code = -115
[ 772.415823] CIFS: enabling forceuid mount option implicitly because uid= option is specified
[ 772.415826] CIFS: enabling forcegid mount option implicitly because gid= option is specified
[ 772.415827] CIFS: Attempting to mount //desktop/c53aa34d-5166-3461-b34a-f12291786b35_prodigious-pony:/home/ubuntu/test
[ 782.842204] CIFS: VFS: Error connecting to socket. Aborting operation.
[ 782.842426] CIFS: VFS: cifs_mount failed w/return code = -115
I ran my tests on 24.10 originally. By default it's not available anymore, so I ran additional test on 24.04 LTS. Here's the outcome
Without modifying the 'desktop' in hosts, it resolves differently from before, and now it also fails to ping (ping used to work).
ubuntu@prodigious-pony:~$ ping desktop
PING desktop.mshome.net (172.21.160.1) 56(84) bytes of data.
^C
--- desktop.mshome.net ping statistics ---
72 packets transmitted, 0 received, 100% packet loss, time 72724ms
ubuntu@prodigious-pony:~$ ping desktop.lan
PING desktop.lan (192.168.1.179) 56(84) bytes of data.
^C
--- desktop.lan ping statistics ---
8 packets transmitted, 0 received, 100% packet loss, time 7196ms
Now, having launched 24.10 to have the same guest as in the original test, the errors are different (I still have myself explicitly added to that folder's ACL with full control)
PS C:\Users\roman> multipass mount -t native "D:\temp" prodigious-pony`:/home/ubuntu/test
mount failed: The following errors occurred:
error mounting "/home/ubuntu/test": Failed to install cifs-utils
PS C:\Users\roman> multipass mount -t native "D:\temp" prodigious-pony`:/home/ubuntu/test
mount failed: The following errors occurred:
error mounting "/home/ubuntu/test": Failed to install cifs-utils
****** NOTE HOW ADDING '-v' CHANGES THE OUTPUT
PS C:\Users\roman> multipass mount -t native -v "D:\temp" prodigious-pony`:/home/ubuntu/test
[2025-11-18T09:51:20.661] [warning] [smb-mount-handler] Failed to install 'cifs-utils', error message: 'E: The repository 'http://security.ubuntu.com/ubuntu oracular-security Release' no longer has a Release file.
E: The repository 'http://archive.ubuntu.com/ubuntu oracular Release' no longer has a Release file.
E: The repository 'http://archive.ubuntu.com/ubuntu oracular-updates Release' no longer has a Release file.
E: The repository 'http://archive.ubuntu.com/ubuntu oracular-backports Release' does not have a Release file.'
mount failed: The following errors occurred:
error mounting "/home/ubuntu/test": Failed to install cifs-utils
Thank you for the quick feedback and logs. The first problem should be dealt with in the mentioned Hyper-V PR (#4080).
Now it seems like DNS resolution works properly (you get desktop.mshome.net and the IP), but it cannot connect. Can you show the ip addr show in this new VM? From the failure to install cifs-utils I think that your VM does not have access to any networking, are you applying the same changes as before to their networking (the script you shared earlier)?
Aside from the networking error, it seems that we are getting closer to the root of the problem:
[ 388.518988] CIFS: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 (or even SMB3 or SMB2.1) specify vers=1.0 on mount.
Although it should not happen, since mounts do work when tested in windows, I will give it another look soon.
PD: -v increases verbosity, you can go as far as -vvvv. Also, when specifying the mountpoint I noticed that you did vmname`:mountpoint every time. Is this some sort of typo or is it in the name of the vm? From our docs it seems like
Thank you again.
Having run the same on 25.10, the issues are similar to 24.04, just slightly different:
PS C:\Users\roman> multipass launch --name prodigious-pony --cpus 4 --memory 3G --disk 10G 25.10
Launched: prodigious-pony
PS C:\Users\roman> multipass mount -t native -v "D:\temp" prodigious-pony`:/home/ubuntu/test
[2025-11-18T09:56:34.079] [warning] [smb-mount-handler] Failed to decrypt credentials from file: failed to open file 'D:/HyperV/Multipass/data/vault/instances/prodigious-pony/35ec09ee-c2d6-32cd-a1f6-c68d79406dcd.cifs': No such file or directory(2)
Please enter your user password to allow Windows mounts:
mount failed: The following errors occurred:
error mounting "/home/ubuntu/test": failed to obtain exit status for remote process 'sudo mount -t cifs //desktop/c53aa34d-5166-3461-b34a-f12291786b35_prodigious-pony:/home/ubuntu/test /home/ubuntu/test -o credentials=/tmp/.smb_credentials,uid=$(id -u),gid=$(id -g)': timed out after 5000 ms
dmesg says:
[ 1.855730] audit: type=1400 audit(1763488562.023:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="buildah" pid=620 comm="apparmor_parser"
[ 2.258676] ISO 9660 Extensions: Microsoft Joliet Level 3
[ 2.258791] ISOFS: changing to secondary root
[ 2.580905] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 2.581035] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 2.581102] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[ 2.968114] EXT4-fs (sda1): resizing filesystem from 626939 to 2330875 blocks
[ 2.991592] EXT4-fs (sda1): resized filesystem to 2330875
[ 3.446951] NET: Registered PF_QIPCRTR protocol family
[ 3.458264] loop0: detected capacity change from 0 to 8
[ 4.297425] TCP: eth0: Driver has suspect GRO implementation, TCP performance may be compromised.
[ 48.799343] netfs: FS-Cache loaded
[ 48.859058] Key type cifs.spnego registered
[ 48.859066] Key type cifs.idmap registered
[ 48.859263] CIFS: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 (or even SMB3 or SMB2.1) specify vers=1.0 on mount.
[ 48.859264] CIFS: enabling forceuid mount option implicitly because uid= option is specified
[ 48.859264] CIFS: enabling forcegid mount option implicitly because gid= option is specified
[ 48.859265] CIFS: Attempting to mount //desktop/c53aa34d-5166-3461-b34a-f12291786b35_prodigious-pony:/home/ubuntu/test
[ 49.011548] hv_balloon: Max. dynamic memory size: 3072 MB
[ 59.399006] CIFS: VFS: Error connecting to socket. Aborting operation.
[ 59.399082] CIFS: VFS: cifs_mount failed w/return code = -115
Ping desktop times out,
ubuntu@prodigious-pony:~$ ping desktop
PING desktop.mshome.net (172.21.160.1) 56(84) bytes of data.
^C
--- desktop.mshome.net ping statistics ---
43 packets transmitted, 0 received, 100% packet loss, time 42994ms
ubuntu@prodigious-pony:~$ ping desktop.lan
PING desktop.lan (192.168.1.179) 56(84) bytes of data.
^C
--- desktop.lan ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4113ms
Network interfaces on the VM:
ubuntu@prodigious-pony:~$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 52:54:00:12:5a:f0 brd ff:ff:ff:ff:ff:ff
altname enx525400125af0
Ping to internet sites works:
ubuntu@prodigious-pony:~$ ping google.com
PING google.com (142.251.32.46) 56(84) bytes of data.
64 bytes from sfo03s26-in-f14.1e100.net (142.251.32.46): icmp_seq=1 ttl=112 time=7.61 ms
64 bytes from sfo03s26-in-f14.1e100.net (142.251.32.46): icmp_seq=2 ttl=112 time=7.19 ms
64 bytes from sfo03s26-in-f14.1e100.net (142.251.32.46): icmp_seq=3 ttl=112 time=7.49 ms
64 bytes from sfo03s26-in-f14.1e100.net (142.251.32.46): icmp_seq=4 ttl=112 time=7.06 ms
^C
--- google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3816ms
rtt min/avg/max/mdev = 7.055/7.336/7.608/0.222 ms
From your subsequent tests it is apparent that the issue is mainly based on networking, particularly on the firewall side. Could you answer the following?
- Did you access the VMs via multipass shell? If not could you try to do so?
- Could you print the
ip addr showadditionally from ip link? - Could you check the firewall rules? I suspect that the TCP port may be blocked, as well as the ICMP
SMB mounts are TCP-based, and seeing that you do not have internet problems otherwise (except in the first test), I am inclined to think it is firewall related. 24.10 is not a supported Ubuntu version, since it is not an LTS, which is probably why the VM could not install the cifs-utils the usual way. This is something we may need to look into additionally.
After enabling default bridged network in Multipass UI, and enabling it on the same VM 25.10 instance,
Network interfaces:
ubuntu@prodigious-pony:~$ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 52:54:00:12:5a:f0 brd ff:ff:ff:ff:ff:ff
altname enx525400125af0
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
link/ether 52:54:00:6a:ca:fa brd ff:ff:ff:ff:ff:ff
altname enx5254006acafa
But all the errors are the same (pinging desktop, dmesg etc.).
Did you access the VMs via multipass shell? If not could you try to do so?
- these commands are via Multipass UI shell window, but running them via multipass shell in terminal produces the same results
Could you print the ip addr show additionally from ip link?
ubuntu@prodigious-pony:~$ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 52:54:00:12:5a:f0 brd ff:ff:ff:ff:ff:ff
altname enx525400125af0
inet 172.21.175.62/20 metric 100 brd 172.21.175.255 scope global dynamic eth0
valid_lft 86012sec preferred_lft 86012sec
inet6 fe80::5054:ff:fe12:5af0/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 52:54:00:6a:ca:fa brd ff:ff:ff:ff:ff:ff
altname enx5254006acafa
inet 172.21.163.209/20 metric 200 brd 172.21.175.255 scope global dynamic eth1
valid_lft 86012sec preferred_lft 86012sec
inet6 fe80::5054:ff:fe6a:cafa/64 scope link proto kernel_ll
valid_lft forever preferred_lft forever
Could you check the firewall rules? I suspect that the TCP port may be blocked, as well as the ICMP
- disabling the firewall on PUBLIC network resolves the ping issue
- mount now gives a new error
PS C:\Users\roman> multipass mount -t native -v "D:\temp" prodigious-pony`:/home/ubuntu/test
mount failed: The following errors occurred:
error mounting "/home/ubuntu/test": Error: mount error(2): No such file or directory
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
That is great, could you check if the test folder exists?
Also, disabling the firewall is a bit extreme, only some ports need to be opened, but for diagnosing it is good enough. Just make sure to turn it back on.
Having deleted the /home/ubuntu/test that was probably established in some previous commands, I now get a new error when mounting
PS C:\Users\roman> multipass mount -t native -v "D:\temp" prodigious-pony`:/home/ubuntu/test
[2025-11-18T10:22:08.032] [warning] [smb-mount-handler] Failed to decrypt credentials from file: failed to open file 'D:/HyperV/Multipass/data/vault/instances/prodigious-pony/35ec09ee-c2d6-32cd-a1f6-c68d79406dcd.cifs': No such file or directory(2)
Please enter your user password to allow Windows mounts:
mount failed: The following errors occurred:
error mounting "/home/ubuntu/test": Error: mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
Here's dmesg:
[ 173.241303] CIFS: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 (or even SMB3 or SMB2.1) specify vers=1.0 on mount.
[ 173.241304] CIFS: enabling forceuid mount option implicitly because uid= option is specified
[ 173.241305] CIFS: enabling forcegid mount option implicitly because gid= option is specified
[ 173.241306] CIFS: Attempting to mount //desktop/c53aa34d-5166-3461-b34a-f12291786b35_prodigious-pony:/home/ubuntu/test
[ 183.814269] CIFS: VFS: Error connecting to socket. Aborting operation.
[ 183.814334] CIFS: VFS: cifs_mount failed w/return code = -115
[ 554.269431] CIFS: enabling forceuid mount option implicitly because uid= option is specified
[ 554.269434] CIFS: enabling forcegid mount option implicitly because gid= option is specified
[ 554.269435] CIFS: Attempting to mount //desktop/c53aa34d-5166-3461-b34a-f12291786b35_prodigious-pony:/home/ubuntu/test
[ 554.290045] CIFS: VFS: BAD_NETWORK_NAME: \\desktop\c53aa34d-5166-3461-b34a-f12291786b35_prodigious-pony:
[ 554.290247] CIFS: VFS: cifs_mount failed w/return code = -2
[ 659.957903] CIFS: enabling forceuid mount option implicitly because uid= option is specified
[ 659.957906] CIFS: enabling forcegid mount option implicitly because gid= option is specified
[ 659.957907] CIFS: Attempting to mount //desktop/c53aa34d-5166-3461-b34a-f12291786b35_prodigious-pony:/home/ubuntu/test
[ 662.065250] CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
[ 662.065260] CIFS: VFS: \\desktop Send error in SessSetup = -13
[ 662.065371] CIFS: VFS: cifs_mount failed w/return code = -13
Thank you for the quick response, we are getting close. Could you try not using the ` character after the VM name? It may be ignored or not a problem, but we should check just in case.
EDIT: It may also be that the authentication failure is due to a incorrect password, although it could be something else as well.
It's Powershell command line, so should be escaping that colon. Here's what I get when I remove the backtick:
PS C:\Users\roman> multipass mount -t native -v "D:\temp" prodigious-pony:/home/ubuntu/test
[2025-11-18T10:28:56.746] [warning] [smb-mount-handler] Failed to decrypt credentials from file: failed to open file 'D:/HyperV/Multipass/data/vault/instances/prodigious-pony/35ec09ee-c2d6-32cd-a1f6-c68d79406dcd.cifs': No such file or directory(2)
Please enter your user password to allow Windows mounts:
mount failed: The following errors occurred:
error mounting "/home/ubuntu/test": Error: mount error(2): No such file or directory
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
By the way now all my attempts don't say LOGON_FAILURE, and instead say no such file as last time. See more recent messages in dmesg are different:
[ 173.241303] CIFS: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 (or even SMB3 or SMB2.1) specify vers=1.0 on mount.
[ 173.241304] CIFS: enabling forceuid mount option implicitly because uid= option is specified
[ 173.241305] CIFS: enabling forcegid mount option implicitly because gid= option is specified
[ 173.241306] CIFS: Attempting to mount //desktop/c53aa34d-5166-3461-b34a-f12291786b35_prodigious-pony:/home/ubuntu/test
[ 183.814269] CIFS: VFS: Error connecting to socket. Aborting operation.
[ 183.814334] CIFS: VFS: cifs_mount failed w/return code = -115
[ 554.269431] CIFS: enabling forceuid mount option implicitly because uid= option is specified
[ 554.269434] CIFS: enabling forcegid mount option implicitly because gid= option is specified
[ 554.269435] CIFS: Attempting to mount //desktop/c53aa34d-5166-3461-b34a-f12291786b35_prodigious-pony:/home/ubuntu/test
[ 554.290045] CIFS: VFS: BAD_NETWORK_NAME: \\desktop\c53aa34d-5166-3461-b34a-f12291786b35_prodigious-pony:
[ 554.290247] CIFS: VFS: cifs_mount failed w/return code = -2
[ 659.957903] CIFS: enabling forceuid mount option implicitly because uid= option is specified
[ 659.957906] CIFS: enabling forcegid mount option implicitly because gid= option is specified
[ 659.957907] CIFS: Attempting to mount //desktop/c53aa34d-5166-3461-b34a-f12291786b35_prodigious-pony:/home/ubuntu/test
[ 662.065250] CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
[ 662.065260] CIFS: VFS: \\desktop Send error in SessSetup = -13
[ 662.065371] CIFS: VFS: cifs_mount failed w/return code = -13
[ 1066.567350] CIFS: enabling forceuid mount option implicitly because uid= option is specified
[ 1066.567353] CIFS: enabling forcegid mount option implicitly because gid= option is specified
[ 1066.567353] CIFS: Attempting to mount //desktop/c53aa34d-5166-3461-b34a-f12291786b35_prodigious-pony:/home/ubuntu/test
[ 1066.569236] CIFS: VFS: cifs_mount failed w/return code = -2
[ 1211.596027] CIFS: enabling forceuid mount option implicitly because uid= option is specified
[ 1211.596031] CIFS: enabling forcegid mount option implicitly because gid= option is specified
[ 1211.596031] CIFS: Attempting to mount //desktop/c53aa34d-5166-3461-b34a-f12291786b35_prodigious-pony:/home/ubuntu/test
[ 1211.597937] CIFS: VFS: cifs_mount failed w/return code = -2
[ 1227.579662] CIFS: enabling forceuid mount option implicitly because uid= option is specified
[ 1227.579665] CIFS: enabling forcegid mount option implicitly because gid= option is specified
[ 1227.579665] CIFS: Attempting to mount //desktop/c53aa34d-5166-3461-b34a-f12291786b35_prodigious-pony:/home/ubuntu/test
[ 1227.581332] CIFS: VFS: cifs_mount failed w/return code = -2
[ 1257.495708] CIFS: enabling forceuid mount option implicitly because uid= option is specified
[ 1257.495711] CIFS: enabling forcegid mount option implicitly because gid= option is specified
[ 1257.495711] CIFS: Attempting to mount //desktop/c53aa34d-5166-3461-b34a-f12291786b35_prodigious-pony:/home/ubuntu/test
[ 1257.497522] CIFS: VFS: cifs_mount failed w/return code = -2
Very well, we are closer. It could be that the problem is the SMB server. Could you open the Services application and see what is the status of "Server"? Restart it if you are able and try the mount again. That should discard that possibility.
Okay, I had to re-do a few things to get closer to my initial setup. First, I started using the same scripts for the Kubernetes cluster again, instead of the ad-hoc launch commands. My Windows service 'Service' was running, but I restarted it as you requested above. Host IP address is actually different now, so I adjusted it in my scripts that configure networking settings.
When I attempt to attach a folder now, still erroring out.
Host:
PS C:\Users\roman> multipass mount -t native -v "D:\temp" kub-control-lb`:/home/ubuntu/test
[2025-11-18T11:19:04.217] [warning] [smb-mount-handler] Failed to decrypt credentials from file: failed to open file 'D:/HyperV/Multipass/data/vault/instances/kub-control-lb/35ec09ee-c2d6-32cd-a1f6-c68d79406dcd.cifs': No such file or directory(2)
Please enter your user password to allow Windows mounts:
mount failed: The following errors occurred:
error mounting "/home/ubuntu/test": Error: mount error(2): No such file or directory
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
dmesg on guest:
[ 49.075436] hv_balloon: Max. dynamic memory size: 1024 MB
[ 93.820657] CIFS: enabling forceuid mount option implicitly because uid= option is specified
[ 93.820661] CIFS: enabling forcegid mount option implicitly because gid= option is specified
[ 93.820662] CIFS: Attempting to mount //desktop/c53aa34d-5166-3461-b34a-f12291786b35_kub-control-lb:/home/ubuntu/test
[ 93.823863] CIFS: VFS: cifs_mount failed w/return code = -2
By the way, I re-enabled the firewall and added a rule to allow inbound from '172.21.160.1/20', this seems to be sufficient to let pings to through. ipconfig for this interface shows the following:
Ethernet adapter vEthernet (Default Switch):
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::9f08:3f5d:b776:d2cc%31
IPv4 Address. . . . . . . . . . . : 172.21.160.1
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . :
I also tried mounting with an intentionally wrong password, and it says permission denied. So in my other attempts, password must have been correct.
PS C:\Users\roman> multipass mount -t native -v "D:\temp" kub-control-lb`:/home/ubuntu/test
[2025-11-18T11:37:00.489] [warning] [smb-mount-handler] Failed to decrypt credentials from file: failed to open file 'D:/HyperV/Multipass/data/vault/instances/kub-control-lb/35ec09ee-c2d6-32cd-a1f6-c68d79406dcd.cifs': No such file or directory(2)
Please enter your user password to allow Windows mounts:
mount failed: The following errors occurred:
error mounting "/home/ubuntu/test": Error: mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
dmesg:
[ 1165.408979] CIFS: enabling forceuid mount option implicitly because uid= option is specified
[ 1165.408982] CIFS: enabling forcegid mount option implicitly because gid= option is specified
[ 1165.408983] CIFS: Attempting to mount //desktop/c53aa34d-5166-3461-b34a-f12291786b35_kub-control-lb:/home/ubuntu/test
[ 1167.524880] CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
[ 1167.524892] CIFS: VFS: \\desktop Send error in SessSetup = -13
[ 1167.524972] CIFS: VFS: cifs_mount failed w/return code = -13
Overall, it looks like on 1.16.1 native mounts still don't work on Windows, but they fail for somewhat different reason.
- On the host, CLI still fails to notice that I have full control over the mounted folder via Administrators group I am member of, and requires me to add myself to ACL explicitly.
- On the host, CLI still asks for the user password, no way to supply password and use that in a background script.
- When mounting, no more of the old 'could not resolve address for desktop: Unknown error', and instead it fails with something new, 'CIFS: VFS: cifs_mount failed w/return code = -2'.