Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Ctrl-Alt-Shift-F is not working after windows 10 1903 update. #193

Closed
jaehyuck0103 opened this issue Sep 4, 2019 · 7 comments
Closed

Ctrl-Alt-Shift-F is not working after windows 10 1903 update. #193

jaehyuck0103 opened this issue Sep 4, 2019 · 7 comments
Labels
SEP (somebody else's problem) somebody else fixed it workaround available

Comments

@jaehyuck0103
Copy link

Ctrl-Alt-Shift-F (to exit from full-screen mode) is not working after Windows 10 1903 update.
https://superuser.com/questions/1445551/what-does-ctrlaltshiftf-key-combination-in-windows-10-pro-version-1903-do

The alternative method (Ctrl-Esc Esc and then right-click on the vncviewer taskbar icon) is also not working to me. (Maybe I don't know exactly how to use it.)

Please check the issue. Thank you.
@dcommander
Copy link
Member

Known issue:
https://www.mail-archive.com/[email protected]/msg00162.html
and unfortunately not one that can be fixed or even worked around by us, at least not without understanding why the issue is occurring. There is no documentation from Microsoft to indicate why Ctrl-Alt-Shift-F is now reserved. It just stopped working for no apparent reason, so it may very well be a bug. The workaround is to enable Alt-Enter as an alternate keystroke to enter/leave full-screen mode. I will expose that in the GUI in TurboVNC 3.0 (#182).

@jaehyuck0103
Copy link
Author

Thank for your support!

Here is a temporal solution on TurboVNC 2.2.2, for other people.

  1. Edit any ".vnc" file as fsaltenter=1
  2. Connect by running the ".vnc" file. Then Alt-Enter is now working.
  3. After the moment, even if you just run the vnc viewer without ".vnc" file, Alt-Enter is working. Maybe the viewer memorizes the previous config.

@dcommander
Copy link
Member

Yes, if -fsaltenter or -nofsaltenter is specified for any connection, that setting will be remembered for the connection. The same will be true for the Java viewer once #135 is implemented.

@dcommander
Copy link
Member

You don't necessarily need to create a .vnc file. You can just edit the Start Menu icon for the TurboVNC Viewer and add -fsaltenter as a command-line argument for vncviewer.exe.

dcommander added a commit that referenced this issue Apr 2, 2020
@dcommander
Viewer: Expose -FSAltEnter in Options dialog
0912305 
Since Windows 10 started eating Ctrl-Alt-Shift-F after Update 1903
(refer to #193), this will serve as a stopgap until we figure out why
Windows 10 is doing that.

Closes #182
@dcommander
Copy link
Member

The use of Alt-Enter as an alternate full-screen toggle hotkey can now be configured in the TurboVNC Viewer Options dialog, which at least makes this issue more straightforward to work around.

@mvalent3 mvalent3 mentioned this issue May 13, 2020
Open
@jsh-de
Copy link

jsh-de commented Feb 16, 2021

For the archives: I tripped on this bug with a software of mine today, I was still running Windows 10 1909 (not sure why Windows auto-update hadn't happened yet). I updated my Windows to 20H2 using the Update Assistant, and joyfully note: the bug seems to have been fixed by Microsoft: KeyDown-events for CTRL-ALT-SHIFT-F do occur again.

@dcommander
Copy link
Member

Confirmed fixed in 20H2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
SEP (somebody else's problem) somebody else fixed it workaround available
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dcommander @jaehyuck0103 @jsh-de