Windows 10: How to delete shortcut Ctrl + Shift?

I don't know how to delete his. Can you help me? Thank you!




***Modified title from: I don't know how to delete shortcut on keyboard ctrl + shift***

:)

 

Ctrl+Shift+Z shortcut unassignable

Here are the quick answers to your questions, and following, a more develop explanations.

1. Ctrl+Shift+Z is an already existing basic, known shortcut in all Adobe softwares for the "Redo" action. I am trying to use it and it’s not doing anything. Ctrl+Alt+V is a shortcut I am trying to assign to an action in the ebook conversion software Sigil.

2. Ctrl+Shift+Z for the already existing shortcut of the "Redo" action in Adobe softwares. Ctrl+Alt+V to a specific function in Sigil.

3. Ctrl+Shift+Z in all the Adobe Creative Suite, Ctrl+Alt+V in Sigil.

Actually the issue happened when I started my work on InDesign yesterday. As you must know, Ctrl+Shift+Z is a very common, basic shortcut for the "Redo" action. After that, I opened up Sigil and tried to assign Ctrl+Alt+V to a certain action, which is the
setting I put previously in my old laptop using Windows 8.

Then, when I noticed both didn’t work, I opened a software that makes me able to remap my keyboard and assign new keystrokes, key combinations, or even macro, to a single key (SteelSeries software going with my MSI gaming laptop), and tried different key
combinations. I saw that Ctrl+Shift+A was fully detected for exemple, but if I press Ctrl+Shift+Z or Ctrl+Alt+V, the software only detects Ctrl+Shift or Ctrl+Alt, and not the letter going to it.

Here is a screenshot of some tests I did in the SteelSeries software, testing key combinations. I tried Ctrl+Shift combined with respectively those letters, in this order: w / x / y / z

As you can see, the combinations with the W and with the Y are detected, but with the X and the Z, they aren’t. And if I tried to assigned as shortcut the combinations with the X and the Z in any software, they are also not detected.





Also, Ctrl+Alt+V is not detected anywhere as mentioned, but Shift+Ctrl+V is detected. Ctrl+Alt+Z and +X are also not detected. But any letter with only Ctrl, only Shift or only Alt are detected.

So the issue is happening in multiple softwares and seems to come from some letters not being detected when used in combination with Ctrl+Shift or Ctrl+Alt. Very weird.... I hope my explanations are clear.

 

Windows 10 File Explorer shortcuts Ctrl+Shift+'n' stopped working

Hi

The extremely useful shortcuts (Ctrl+Shift+'n') within File Explorer has suddenly stopped working.

There was an automatic Windows update a few days ago and I believe the last time I used the shortcuts was before this update. These shortcuts worked as follows...

Ctrl+Shift+1 Change View to Extra Large Icons

Ctrl+Shift+2 Change View to Large Icons

Ctrl+Shift+3 Change View to Medium Icons

Ctrl+Shift+4 Change View to Small Icons

Ctrl+Shift+5 Change View to List View

Ctrl+Shift+6 Change View to Details View

Elsewhere I have seen a couple of other Windows 10 users reporting the same issue but I have not yet tracked down a fix.

As far as I can tell all of my other keyboard shortcuts are working.

I am on a 9 month old Dell Inspiron 17 5770 Laptop.

Is there a setting I can apply to get the shortcuts back please?

Thanks in advance

Rick

 

"Shift + Ctrl + Numbers" thumbnail view shortcut in file explorer of windows 10 1511 not working

Hi Mohak,

Welcome to Microsoft Community.

I understand that the Shift + Ctrl + Number shortcut fails to work on Windows 10 after update. I will certainly help you.

As initial troubleshooting, I suggest you to check other keyboard shortcuts like
Shift + Caps Lock, Ctrl + P, Ctrl + Shift + Esc are working like it should.

Similarly check whether Shift + Ctrl + 3, 4,
5, 6, 7, 8 keyboard shortcuts which customizes the File Explorer view are working.

Follow the below steps and check if it resolves the issue.

Step 1:

1. Right click on Start, navigate to
Control Panel > File Explorer Options.

2. Click on General and View
tab and click on Restore Defaults > Apply >
OK.

Please post back with the status of the issue and we will be glad to assist you further.

Thank you.