-
Notifications
You must be signed in to change notification settings - Fork 654
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot install/run multipass on Windows 10 unable to set driver to hyperv #3763
Comments
Failed to set driver. Will try again in 1 second. Please use 'multipass authenticate' before proceeding. Failed to set driver. Will try again in 1 second. Attempting to set driver to hyperv[2K [OA [OEset failed: The client is not authenticated with the... Please use 'multipass authenticate' before proceeding. Failed to set driver. Will try again in 1 second. Attempting to set driver to 'hyperv'[2K [OA [OEset failed: The client is not authenticated with the. Please use 'multipass authenticate' before proceeding. Failed to set driver. Will try again in 1 second. |
This appears during installation |
I wonder why |
Hi @2021400278zzc , this appears to be a different issue than the OP, please make a new issue and follow the issue template so that we can help you better with this! |
Hi @brucejo75 , would you be able to access the logs on your Windows machine and send them here as files? Additionally, can you provide us with more information on your Windows 10 installation, such as whether it is Home/Pro/Enterprise? |
Hi @levkropp, I am running Windows 10 Pro Version 22H2 (OS Build 19045.5073) To reproduce a 1st install I did these steps:
Install completes, but the installer never resolved an error connecting the multipass service. At this point the To generate GUI logs, I started the Multipass App, which sits in an infinite loop "Waiting for daemon". This does produce a log in the Hope this helps! PS: I repeated steps 1-3 as admin and got the same results with these logs: |
Hi @brucejo75, I couldn't find anything wrong in your daemon logs. It could be that, for some reason, it just takes a long time to initialize and doesn't come up on time for the client to reach it from the installer. What's puzzling to me is the port numbers you report: 40041 (CLI, I believe) and 58403, 58405... (GUI). I don't suppose you have One thing you could try is this package, to see if you observe the same thing. We're changing our Windows packaging to MSI and hopefully the problem does not occur there. |
Describe the bug
Multipass cannot connect to the
multipassd.exe
socket.Suspect that latest version of Windows 10 may have changed something.
To Reproduce
multipassd.exe
is running.It finally stopped attempting but the program is not running and I keep getting socket connection errors.
I tried this on versions:
1.10.1
,1.10.1
,1.13.1
&1.14.1
Expected behavior
expected Multipass to install without errors.
Logs
Tried to run the install that had errors, captured logs.
Multipass Logs
Additional info
multipass version:
1.14.1+winmultipass info
: "info failed: cannot connect to the multipass socket"multipass get local.driver
: "get failed: cannot connect to the multipass socket"Additional context
multipassd.exe
to the allowed apps list for the Windows Firewall. Both Private and Public. Noticed that all ports were already openedmultipass.exe
&multipassd.exe
.multipassd.exe
is runningMultipass Service
is runningThe text was updated successfully, but these errors were encountered: