Hi Guys -

I just installed Enpass 6.11.12 (1997) and I can't get the Wi-Fi Sync to work between my Windows 11 desktop and my iPhone.  I went through every troubleshooting document I could find but nothing fixes the issue.

Here are the suggestions I tried, and more info about my configuration:

• I am running Windows 11.  When I try to find my Enpass Vault on my iPhone it cannot find the Windows 11 Vault.  When I scan the QR code it just spins and does nothing.  When I go to the Manual Setup I cannot see my Windows 11 Vault.  I rebooted and restarted the computer, iPhone, and router and cycled WiFi on all.  I completely uninstalled Enpass from both my Windows 11 desktop and my iPhone, and reinstalled both. Everything is on the same WiFi network and all the clocks are consistent.  I stopped and restarted the Wi-Fi Sync Server on the Server computer.  The Enpass WiFi Sync server appears to be running correctly – the Status says Running and the Server Name and Address look correct. It lists my Primary vault as being available for syncing through the server.
• I have Network Discovery turned on. File and Printer Sharing turned on. and Public Folder Sharing turned on. My network is set to Private. The Function Discovery Resource Publication, DNS Client, SSDP Discovery, and UPnP Device Host services are all running. SMB 1.0/CIFS File Sharing Support is on.  I also turned off the Windows Defender firewall for my private network and it still has the same problem -- it is not visible on my iPhone.
• I normally run, but disabled for testing, Norton 360 and NordVPN.  
• I have an old Windows 10 system.  It normally runs Linux, but I briefly rebooted it into Windows 10 and Enpass Wi-Fi sync works there -- when I try to find my Enpass Vault on my iPhone I can see the Vault on Windows 10 and sync to it.  So I know there is no problem with my router or network.

So, I don't know what is different between my two systems other than one is Windows 10 and the other is Windows 11.  I assume many people are successfully using Wi-Fi sync on Windows 11, so it must be possible to work correctly.

Does anyone have any suggestions on what might be causing the problem?

Thanks for your help!

Mike

 

Our technical team is informed and is currently investigating the issue. We’ll update you as soon as we receive an update from them.

#SI-4403

Hi Tarun -

It's been quite a long time since you told me your dev team is investigating the issue.  Do you have any suggestions for me?  

Again, where things now stand, is that my iPhone can successfully sync to the enpass server on my Windows 11 system.  But my Windows 11 laptop still does not work.  I am running Norton 360 and I verified that wifisyncserver_bin is listed as Allowed in their firewall.  I also temporarily disabled Norton and it still doesn't work.

When I install enpass on my Windows 11 laptop and select Wi-Fi Sync the application just spins and says "Looking up for servers..."  Both systems are on the same private network.  

And as I said in my original post I tried doing the same thing on an old WIndows 10 system and it works.  Wny would it work on Windows 10 but not on Windows 11?

Haven't a lot of other people also run into this issue before?  I don't think my environment is unusual -- I just have 2 Windows 11 systems.

Thanks,

Mike

 

 

 

We understand that this has been taking time, and we appreciate your continued patience.

Our team is still investigating the issue. Since Wi-Fi Sync works on your iPhone and Windows 10 system but not on the Windows 11 laptop, the issue may be related to certain system-level configurations specific to Windows 11.

We'll share an update as soon as we have more information.

Thanks, Amandeep, for your quick reply.

Here's some additional info for you.  I also have a Linux Mint system, and Enpass works fine on it, communicating with my Windows 11 Enpass server.  As does my iPhone.  But my 2 Windows 11 laptops just spin and are unable to find the Enpass server.  

So since Enpass on iOS and Linux successfully communicate with the server it seems that the server is set up and running properly, and the problem is with the Windows 11 laptops.  

Please advise.  Thanks.

Mike

Hello Amandeep and Tarun -

I've upgraded to the latest version of Enpass and this is still outstanding on my Windows 11 laptop.  Do you have any additional info?  This has been outstanding for a very long time.  

Here are the details of my setup and what I’ve tried:

• Server: Windows 11 desktop, Enpass Wi-Fi Sync Server running, network profile set to Private
• Client: Windows 11 laptop, same Wi-Fi network, network profile also set to Private
• VPN: NordVPN is disabled on both systems
• Firewall: Windows Defender Firewall disabled on both systems during testing
• Connectivity: Laptop can ping the desktop successfully
• Browser test: Entering https://192.168.1.100:58529 from my Windows 11 laptop prompts for username/password, confirming HTTPS server is reachable
  • I get a message saying my connection isn't private. Also I get a message warning about the security certificate. I think this is normal behavior for local services that aren’t backed by a public certificate
• Enpass behavior: Laptop client never discovers the server, does not offer QR code scan or manual IP entry

Additional steps taken:

• Ran Enpass as administrator on desktop
• Disabled all virtual network adapters
• Verified network discovery and file sharing are enabled
• Reinstalled Enpass on laptop and deleted residual data folders
• Confirmed sync works with other devices (iPhone and Linux Mint)

This Confirms

• The sync server is running
• It’s reachable over HTTPS
• The certificate is active, even if untrusted by browsers
• My laptop is not blocked by firewall, VPN, or network profile

This seems like a client-side bug or sync module failure.  Could you advise on any additional diagnostics or configuration steps to resolve this?

Thanks,

Mike

I’ve shared your detailed findings with our product team so they can review the client-side sync module behavior further.  We’ll update this thread once we have more insights. Thanks again for your patience and for helping us investigate this further.