Function keys for the Surface RT - how can I use the F2 key without holding down the "Fn" button?

Anonymous
2012-12-13T21:42:03+00:00

The keyboards that come with the Surface both lack a row of independent function keys, and while I know that I can hold the "Fn" key down and then press the "lower volume" button to get F2, there has to be a better way to do this. F2 and F4 are literally the most important keys in excel for me, and I don't want to hold down the "Fn" key every time I need to use the function keys.  Can I turn on function lock somehow or possibly create a shortcut such that the "lower volume" button works as F2?

If not, the Windows Surface seems pretty worthless for financial and consulting professionals.  I want the Surface to succeed - please tell me that Microsoft didn't overlook this issue.

Thanks

Surface | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2013-05-26T15:44:38+00:00

Sorry to revive an old thread, but the solution for this is to press "Fn + Caps Lock", which acts as a toggle between using the function keys as F# keys and the labelled action.

Was this answer helpful?

50+ people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2013-10-24T14:28:42+00:00

Fn+:

Up: Page Up

Down: Page Down

Left: Home

Right: End

Space: PrtScrn (only way to do a focused app shot using a blade is is Fn+Alt+Space)

Del: Bright Up

Backspace: Bright Down

CapsLock: FnLock

Woah! Sweet, thanks for the list! I had been using the snipping tool because I didn't know about the Fn + Space keyboard shortcut to get the Print Screen button. Awesome! :D

You'd think the brightness buttons on F1 F2 would be for the screen and the more obscure button combinations would be for the keyboard backlight...

Was this answer helpful?

10+ people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2015-03-30T17:22:33+00:00

Thank you.  I should have checked here long ago.  Works perfectly.

Was this answer helpful?

0 comments
Answer accepted by question author
Anonymous
2014-11-04T23:17:47+00:00

If you toggle the FnLock by hitting FnCaps, then the F1-F12 keys become F keys as their primary.

What you guessed is correct.  When FnLock is engaed, the old functions now become their Fn behavior.  Thus if you had FnLock engaged, and then hit Fn+F3, you would get Mute.

Was this answer helpful?

0 comments
Answer accepted by question author
Anonymous
2014-05-30T16:09:16+00:00

press Fn + Caps Lock to toggle between the Fn key being active/inactive. this should fix your problem.

Was this answer helpful?

0 comments
Answer accepted by question author
Anonymous
2013-09-13T02:52:30+00:00

Greetings Piaqt,

When you pressed Fn + CAPS, it enabled FN Lock which stays on. To disabled it, press and hold FN + CAPS for 2-3 seconds and it should disabled, and allow normal keys (mute) to work again.

Was this answer helpful?

0 comments
Answer accepted by question author
Anonymous
2013-06-18T14:38:18+00:00

Hi there Mr. Harry Potter.

Thanks for your post.  We appreciate the feedback and more importantly are glad to hear you are happy with the latest updates and improvements to Surface! Please let us know if you have any questions that we can help you with.

Kindest Regards.

Was this answer helpful?

0 comments

102 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2013-04-03T17:00:10+00:00

    Actually, in looking at my key mappings... I don't think it's possible to properly map these things for this reason:

    Say I was wanted to do Ctrl-F7: That means mapping LCtrl + LWin + F21 to F7, but I will loose my Ctrl modifier because LCtrl was already a part of the message sent by the "Devices" key. This means that it's flat out impossible to correctly re-map these keys! Aaarrg!

    I donno, from what I can tell, a driver modification may be the only solution... Which either needs to come from someone willing to spend a lot of time making a custom driver or hacking some hidden configuration. Or MS releasing a configuration app like they did for the trackpad. D:

    Edit: I've made a post on AutoHotkey in hopes that someone might help me out with making a script to fix this problem:

    *http://www.autohotkey.com/board/topic/92000-script-for-fixingremapping-fn-keys-on-surface-typetouch-cover/#entry580136*

    Feel free to post there to try and get some activity going on it. Thanks!

    Was this answer helpful?

    0 comments