Ctrl+Enter not working anymore

Discussion in 'Windows Virtual Machine' started by JFF, Mar 18, 2024.

  1. JFF

    JFF Bit poster

    Messages:
    2
    Very strange behaviour since the upgrade to 19.3.
    I have used a W11 virtual machine for months and uses Outlook in that VM extensively. I use the Ctrl+Enter shortcut to send emails.
    Since the update, this is not working directly, and to have it working, I need first to press Ctrl+Option+Enter, keep Ctrl pressed and then press Enter.
    I tried:
    • Playing with the setting in Outlook -> No impact
    • Switching in and out of Coherence -> No impact
    • Adding the Ctrl+Enter combination to the shortcut of the VM -> No Impact
    • Mapping the Cmd+Enter to send Ctrl+Enter to the VM -> Cmd+Enter does trigger the email sending, but Ctrl+Enter remains ineffective.
    Any idea what would be happening?
     
    KirillO1 likes this.
  2. KirillO1

    KirillO1 Bit poster

    Messages:
    5
    Best Answer
    I fixed it, I went to Parallels Desktop Preferences -> Shortcuts and added Ctrl+Enter to the list of shortcuts to map.

    upload_2024-3-18_10-42-51.png
     
    MaxR12, KevinB38, JoeB22 and 3 others like this.
  3. Avinash Bundhoo

    Avinash Bundhoo Staff Member

    Messages:
    538
    Hello,

    We are sorry about your experience.
    We have created a ticket to assist you with this issue and will contact you at je********f*****@g****.com with further updates.

    Thanks

    Best regards.
     
  4. KirillO1

    KirillO1 Bit poster

    Messages:
    5
    Can confirm, the latest update breaks Ctrl+Enter.
     
    MagdalenaB1 likes this.
  5. KirillO1

    KirillO1 Bit poster

    Messages:
    5
    Best Answer
    I fixed it, I went to Parallels Desktop Preferences -> Shortcuts and added Ctrl+Enter to the list of shortcuts to map.

    upload_2024-3-18_10-42-51.png
     
    MaxR12, KevinB38, JoeB22 and 3 others like this.
  6. mcinf

    mcinf Bit poster

    Messages:
    4
    Ctrl+enter stopped working for me after upading Macos to 14.4 (I'm using parallels 18.3 with Ubuntu 22.04)
    A workaround for me is to press ctrl+command+enter
     
  7. RussellK3

    RussellK3 Bit poster

    Messages:
    5
    This works. Nice!
     
  8. lucasuylings

    lucasuylings Bit poster

    Messages:
    1
    Works for me too. Great, thanks.
     
  9. JFF

    JFF Bit poster

    Messages:
    2
    It works for me too. However a colleague of mine installed the last version from scratch and Ctrl+Enter works direct without that workaround.
     
    Adeboye Adeotan likes this.
  10. missa1

    missa1 Bit poster

    Messages:
    6
    Unfortunately, this doesn't work for me.
     
  11. AskarB1

    AskarB1 Junior Member

    Messages:
    10
    Works for me, many thanks. Is this a feature of the last Parallels update? Can someone explain why this works--is it possible that ^Enter on macOS is not sent as Ctrl+Enter on Win anymore, and for this we create a new binding?
     
  12. KevinB38

    KevinB38 Bit poster

    Messages:
    1
    Thank you, KirrilO1!
     
  13. RobertS52

    RobertS52

    Messages:
    1
    I've been having the same issue. I was told by support to add this as a shortcut but it didn't work.

    There is also an issues with using Ctrl+Tab key when you want to tab within a table cell in word. This functionality has been lost with the current upgrade.
    Any suggestions as to the keys to use to create tabs within a table cell?
     
  14. GiovannaG

    GiovannaG

    Messages:
    1
    It doesn't work for me either, and Parallels support wasn't able to solve the problem. Any new idea?
     
  15. StefanS53

    StefanS53

    Messages:
    1
    It is still an issue, the same happens to me.
    Ctrl + Enter shortcut is simply eaten and ignored.

    One has to manually add this shortcut to as suggested above.
    Parallels, please fix, so don't have to do workaround for a long month.
     
  16. Adeboye Adeotan

    Adeboye Adeotan Staff Member

    Messages:
    416
    Hello Stefan,

    Please be informed that our Development Team are aware of this issue and are working on a long-term solution.
     

Share This Page