MullvadVPN 2025.3-beta1.exe installs, but will not show user interface whatsoever #7504
Comments
narration-sd
changed the title
|
Having the same issue as well. Installed 2025.2 and the UI shows up. I'm on W10 22H2 |
|
This is a known issue in Electron related to parsing some shortcuts. It will be fixed in an upcoming release. Note that it doesn't affect the system service, so you can use the CLI if you want. Otherwise, downgrading to stable is (unfortunately) your best option for now. |
|
I hate to say it, but same. The UI just isn't opening and the application isn't running (besides the daemon sorta). I can just barely catch it in the hidden icons, then double click fast and open a window, but then that window will disappear and mullvad will crash. |
|
Same here after installing |
|
@dlon, just a bit surprised that there wasn't Windows testing to show this up? We do depend on Mullvad for security, so testing per platform before releasing a beta seems indicated, no so? |
|
That is understandable. We test the app on Windows, were aware of the issue, and have fixed it in the upstream dependency. We partially use betas to assess how many people are affected by issues, as we often have no other way of knowing this. Note that far from all users experience this issue. This does not affect the security of the application, only the Electron frontend. For example, if you have auto-connect or lockdown mode enabled, these will operate normally without the GUI. |
|
Yes, I did check that the daemon running on a task was actually operating Mullvad and the VPN properly altering presented IP address via browser and whatismyip. But without the UX, you can't otherwise be sure -- and as if to highlight, somehow this morning the 'launch on Windows start' had gotten unchecked, this on the previous version, so that I had no VPN operating. I just wouldn't push things out on a beta with this level of risk. If you knew Electron caused a problem, not much gained by hearing how many it caused that for -- and if they report it, not so? That's a very complex and error-prone package, unless it has miraculously improved since working with it. We use it for its abilities, sure; very valuable, but it needs watching over, suspect you'd agree. And raising doesn't-work issues doesn't help your perception as dependable...! A nice weekend, regardless :) |
|
Same here after installing MullvadVPN-2025.3-beta1. Experiencing this on W10 22H2. |
|
Same here. So annoying. |
|
I have the same thing and not only that, I got absolutely no internet connection with the beta. According to Mullvad, I was online, but I couldn't open a single page. Nothing worked. So I uninstalled the beta again. |
|
I think if you disconnected before installing this beta, or uninstalled a version including its data, then you won't be 'silently' connected after install. You'll then either be locked out from the internet, or on it, but with no protection. One more reason not to promulgate a known flaw like this, no? |
|
Same, happening to me as well. Look forward to an update! |
Is it a bug?
I have checked if others have reported this already
Current Behavior
Expected Behavior
Mullvad UX should just have started from the checkbox on installer, or from the Windows menu
Steps to Reproduce
Failure Logs
Operating system version
Windows 11 24h2 very latest updated
Mullvad VPN app version
2025.3beta1
Additional Information
The text was updated successfully, but these errors were encountered: