Why did VS 2022 change how Control-Shift-End works??????????????????

Question

So, I just started a new ASP.NET Core API project. It generated the boilerplate code for the

the weather forecast. I wanted to get rid of that code. The cursor is at the end of a line. I press the Home key. The cursor disappeared, but I hadn't realized that it disappeared. It went God only knows where. Thinking that VS is behaving the way it should behave, after pressing the Home button, and because I had thought it was at the beginning of the line, and I want to remove all the code from there to the end of Program.cs, I hold down the Control-Shift-End keys. Expecting it to select everything from the line I've selected to the end of Program.cs.

But, NO!! Instead, it goes to a different tab in VS 2022?????????????????????????????????????

Why did it do that? How did it get into whatever mode it is in? Even putting the cursor in any line at all in Program.cs, then using the arrow key, any arrow key does God only knows what, because the cursor disappeared?????????????????????????????????????????????????????

What the heck is going on?

Answer 1

Hi @Rod At Work , 

Welcome to Microsoft Q&A! 

I tested on my side, the cursor, and the Ctrl+Shift+End shortcut are working normally.

You can have a try with the following workarounds:

1. Launch your Visual Studio 2022 in Safe Mode (run devenv /SafeMode in Developer Command Prompt for VS 2022). And check if it works normally.
2. Update your VS2022 with Visual Studio Installer.
3. Reset keyboard mapping scheme by going to Tools > Options > Environment > Keyboard > click on ‘Reset’ > OK.
4. Reset the settings by going to Tools > Import and Export settings > Reset all settings. 

Sincerely,

Anna

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.