M5 Macbook Air, Windows 11 ARM: Coherence won't work nor bridged networking

Discussion in 'Parallels Desktop on a Mac with Apple silicon' started by BillR15, Mar 16, 2026.

  1. RaymondD6

    RaymondD6 Bit poster

    Messages:
    3
    Good Luck. Here is my setup on my Win11 VM

    upload_2026-4-29_20-25-16.png

    Here is my local Host M5 Network Settings that the VM resides on
     

    Attached Files:

  2. RaymondD6

    RaymondD6 Bit poster

    Messages:
    3
    ooops...wrong screenshot: Here is my local Host M5 Network Settings that the VM resides on
    upload_2026-4-29_20-30-43.png
     
  3. FrancescoO1

    FrancescoO1 Bit poster

    Messages:
    9
    I just tried, I set the beta update channel and updated to 2.6.5 beta, but the problem remains, this thing is causing me a lot of problems at work, I hope they can solve it soon
     
  4. FrancescoO1

    FrancescoO1 Bit poster

    Messages:
    9
    ust updated Parallels Desktop to version 26.3.2 (57398) on MacOS 26.4.1 but the bridge interface still doesn't work. Is it possible that Parallels can't solve this problem?
     
  5. FrancescoO1

    FrancescoO1 Bit poster

    Messages:
    9
    I just ran some tests, disabling the WiFi interface, and using a wired USB network adapter, the bridge interface works perfectly, so the problem is related to the WiFi interface.
     
  6. SvenT7

    SvenT7 Bit poster

    Messages:
    2
    Hi,
    A friend and I were testing yesterday, but were not able to get it to work via WiFi.
    We have seen some posts on other Forums, that, introduced with macOS 26.4, apple implemented a new security measure for WiFi.
    As far as I was able to understand this (let me know if i'm wrong), in the bridged mode, the Wifi adapters from the PC has its mac address and the bridged network adapter also has its own mac address, but it works thru the mac adapter. As a security measure, Apple/macOS26.4 restricts WiFi adapters to only one mac address. Therefore we can not get connections over WiFi in Bridged mode.
    This security measure is not implemented for wired connections, therefore allowing this as a workaround until Parallels can figure out a way to work around this issue.
    The wired connection still needs to be configured for a manual iP address in the IPv4 settings.
    I hope this helps
     

Share This Page