# Shortcut key bug?

**URL:** <https://discourse.mcneel.com/t/shortcut-key-bug/154079>\
**Category:** Rhino for Windows\
**Tags:** windows\
**Created:** [January 31, 2023, 10:32am UTC](https://discourse.mcneel.com/t/shortcut-key-bug/154079 "2023-01-31T10:32:45Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![jack3](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/jack3/32/770827_2.png) [@jack3](https://discourse.mcneel.com/u/jack3)\
**Post date:** [January 31, 2023, 10:32am UTC](https://discourse.mcneel.com/t/shortcut-key-bug/154079/1 "2023-01-31T10:32:45Z")

</div>

Hello

The shortcut keys do not work since the OS was changed to Windows 11.  
For example, the one that does not work now is ctrl+alt+R for rendering, but it does not work.  
I have the keyboard set to this command.

> '\_SetDisplayMode \_Rendered

best

---

<div class="post-metadata">

**Author:** ![wim](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/wim/32/747482_2.png) [@wim](https://discourse.mcneel.com/u/wim)\
**Post date:** [January 31, 2023, 2:55pm UTC](https://discourse.mcneel.com/t/shortcut-key-bug/154079/2 "2023-01-31T14:55:29Z")

</div>

Hi Jack -

> [@jack3](#):
>
> […] since the OS was changed to Windows 11.

Have you tried a “Repair” of the Rhino installation in the Windows Control Panel?  
-wim

---

<div class="post-metadata">

**Author:** ![jack3](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/jack3/32/770827_2.png) [@jack3](https://discourse.mcneel.com/u/jack3)\
**Post date:** [January 31, 2023, 3:41pm UTC](https://discourse.mcneel.com/t/shortcut-key-bug/154079/3 "2023-01-31T15:41:25Z")

</div>

Hi @wim

I tried restoration, but the result was the same.  
Wireframe and shaded work.

---

<div class="post-metadata">

**Author:** ![jack3](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/jack3/32/770827_2.png) [@jack3](https://discourse.mcneel.com/u/jack3)\
**Post date:** [January 31, 2023, 3:49pm UTC](https://discourse.mcneel.com/t/shortcut-key-bug/154079/4 "2023-01-31T15:49:06Z")

</div>

If you select from here, it will render correctly, but shortcut keys do not seem to work well.

![render](https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/9/0/f/90fc19788997cac7f3df3407a88cfdbb858ec8c3.jpeg)

---

<div class="post-metadata">

**Author:** ![jack3](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/jack3/32/770827_2.png) [@jack3](https://discourse.mcneel.com/u/jack3)\
**Post date:** [January 31, 2023, 3:54pm UTC](https://discourse.mcneel.com/t/shortcut-key-bug/154079/5 "2023-01-31T15:54:46Z")

</div>

Apparently it was interfering with other software hotkeys.

---

<div class="post-metadata">

**Author:** ![莫智輝](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/%E8%8E%AB%E6%99%BA%E8%BC%9D/32/633315_2.png) [@莫智輝](https://discourse.mcneel.com/u/%E8%8E%AB%E6%99%BA%E8%BC%9D)\
**Post date:** [December 11, 2024, 2:56am UTC](https://discourse.mcneel.com/t/shortcut-key-bug/154079/6 "2024-12-11T02:56:41Z")

</div>

hi，I found the same problem… can you tell me how to solute it? THX

---

<div class="post-metadata">

**Author:** ![wim](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/wim/32/747482_2.png) [@wim](https://discourse.mcneel.com/u/wim)\
**Post date:** [December 11, 2024, 8:14am UTC](https://discourse.mcneel.com/t/shortcut-key-bug/154079/7 "2024-12-11T08:14:22Z")

</div>

Hi -

> [@莫智輝](#):
>
> I found the same problem…

Please describe the issue with some details.  
Also, run the Rhino `SystemInfo` command and copy-paste the output here.  
-wim

---

<div class="post-metadata">

**Author:** ![Aaron\_Borin](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/aaron_borin/32/480744_2.png) [@Aaron\_Borin](https://discourse.mcneel.com/u/Aaron_Borin)\
**Post date:** [February 18, 2025, 5:57pm UTC](https://discourse.mcneel.com/t/shortcut-key-bug/154079/8 "2025-02-18T17:57:03Z")

</div>

Hi.

Same problem after installing the new Nvidia App.  
Solved by disabling Nvidia Overlay inside the App (Settings → Features)