Need help choosing a computer

Thanks! I had seen the DeBloat scripts from GitHub mentioned in a couple YouTube videos, but it's good to hear from an actual real world person that they're worth using. I might just do it manually anyway cause I'm a control freak, but still good to know.

OK, so I've been fighting with this computer all day. I didn't realize how much I used the right control key, and there isn't one on this laptop. Instead, it was replaced with the CoPilot key. I kept activating it when i was intending to hit control. I tried several options to remap it. I tried a GitHub download called NoCoPilotKey, but it somehow interfered with the key hooks in a way that kept stealing capslock from NVDA, so I had to get rid of that one. I tried Power Toys, but it kept telling me that it couldn't activate the shorcut I was trying to do. I finally got it working, at least most of the time, with AutoHotKeys. There are certain screens where it's still activating CoPilot though. it does it in any of the NVDA screens and in a lot of dialogue boxes.
Has anyone else run into this issue? If so, did you remap the key, and how?
I'm afraid that if I can't get this working really consistently everywhere, I may have to return this laptop. that would really suck to have to return it because of that one key.
I appreciate any help.

For me, the CoPilot key is actually running a shortcut which is: Win+left shift+F23. I can remap it in settings to either search, CoPilot, or to open a list of specific apps that I guess they have preapproved. Unfortunately, none of that is what I want it to do. i want my right control key back.
@Maldalain, are you saying that any newer computer I got would have this key instead of right control? that is crazy, if so!
This is the kind of detail that drives me crazy as a blind person. This sort of thing is never listed in any description of the product, and there is no good way to find out except by having a sighted person look at it. Even then, my sister looked at this keyboard and assumed this key was the applications key. that still would have ended up being an issue for me and my muscle memory, but it wouldn't have been as bad as CoPilot.

Well... I refuse to let Microsoft dictate to me! As I said, I did manage to remap it to the right control key in most situations. If anyone else is struggling with this and wants the exact steps and the code to do it, let me know and I'll be happy to post it here.

Full disclosure. I used Gemini to help me write this.
1. Download and install AutoHotkey from autohotkey.com.
2. Right-click your desktop, select New > AutoHotkey Script. Paste the code block below into the file.
Note: I did this by opening the AutoHotkey program and selecting new script. You will be taken to a screen with an edit box to name your script, a browse button, then options for either "Empty; Desc: Clean slate 1 of 2" or "Minimal for v2; Desc: Just #Requires v2.0 2 of 2".
I chose the first one, which drops you into a choice of programs to use. i chose NotePad.
that choice dumps you into an empty NotePad document, where you will paste the script and then save it.
3. Then go to the AutoHotkey folder in your file explorer and hit enter on the name of the file you just created.
There should now be an icon in your system tray, the one you get to with NVDA+B. It may be in the hidden icons. If it's there, the script is running.  
Here's the script:
#Requires AutoHotkey v2.0

; Remap Copilot to Right Control
*<+<#f23::
{
Send("{Blind}{LShift up}{LWin up}{RControl down}")
}

*<+<#f23 up::
{
Send("{RControl up}")
}

And here's a description of why it works for anyone who's interested:
Since we already know background apps like NoCopilotKey crash NVDA, and SharpKeys leaves "ghost" modifiers, the only way to get a clean Control key for NVDA is a specific AutoHotkey script.
This script is designed to "strip" the Windows and Shift keys away the millisecond you touch the Copilot key, leaving only a pure Control signal for NVDA.
Why this works for NVDA:
1. #InstallKeybdHook : This is the most important line. it tells AutoHotkey to share the keyboard "queue" with NVDA instead of fighting it.
2. {LShift up}{LWin up} : This manually "lifts" the ghost keys. When you hold the Copilot key, NVDA will only "hear" the Control key being held down.
3. {Blind} : This ensures that if you are already holding another key (like a letter), the remap doesn't "blink" and lose that key.

I haven't been doing anything crazy with it yet, so I haven't put it through it's paces or anything. I do like the feeling of the keyboard, though it is a little louder than I would have liked, butt I also tend to hit the keys pretty hard, so there is that.
The other things that are aggravating me a little right now, I think are more NVDA things than issues with the computer itself. I'm just so used to JAWS. There are some ways that nVDA does things that I don't like, but it may be just what I'm used to. I will probably end up getting JAWS as well just so I can have the old familiar back, and I will be able to tell if it is a computer or software issue or if it is a screen reader thing that is bothering me.
I will also say that I thought I wouldn't care at all about having a touch screen, but it did help me out of a keyboard trap during the setup process. I am not super familiar with using Narrator, so someone who is may have been able to get out of it with a trick I'm not aware of, but the touch screen did keep me from having to get sighted assistance.
Any other specific questions, I'll be happy to answer.

I looked at the battery usage. Ihad it plugged in a bunch yesterday, but for the time I had it unplugged, it looks like I was losing about 10% of the battery every hour. I was downloading a bunch of programs and using Google Gemini a lot during that period. It also looks like the battery drained about 2% while it was sleeping overnight for about 6 hours.
As for the thermals, it was definitley getting warm and running the fan while I was downloading all of those programs. the keyboard never really got noticeably hot, but the underneath kind of did. I had it on my lap covered with a blanket, and it was fine to use, but I bet it wouldn't have been on bare skin. The fans weren't too loud though. they were nowhere near how loud my Dell Latitude at work is. that one sounds like an airplane is taking off, lol.
today, while I've just been browsing the internet and checking email, the fan hasn't come on at all and it has stayed cool, again using it on my lap covered by a blanket.
Hope that answers your questions.

Thanks again for your help. the first link you gave sounds like exactly what I'm currently doing. I didn't check the code to see how similar it was, but I might try that version to see if it works better than what Gemini gave me.
I'm pretty sure that the second link you just gave is the one I tried previously. it was causing some kind of issue where it was stealing some kind of key hook from NVDA, which was causing NVDA to lose it's hold on the capslock key. Meaning that capslock was no longer functioning as the NVDA key until I restarted NVDA. this happened every time I was hitting the windows key, I guess because it's a part of the CoPilot shortcut that script was trying to change. I don't claim to really understand this stuff. That's just what I took away from what Gemini said when I described the problem I was having.

Actually, I tried doing it with PowerToys. I was able to navigate it with a screen reader pretty well, but I kept getting an errror message that it couldn't remap the shortcut. No explanation. It just said it couldn't do it. I'll have to look around and see what I can find about that. Maybe I'll try that method again if I can figure out why I was getting that error.
I know exactly what they were thinking. They were trying to get people in the habit of defaulting to using CoPilot because it would just be a keystroke away at all times. Obviously, I disagree with their implimentation of it. They weren't thinking of what their customers needed.
I wouldn't want to give up my right alt key either though. I need my modifiers, so just keep your grubby hands off them Microsoft! Lol.

Huh, I hadn't even realized that. Yes, mine does do that. I also have the function+left arrow for home and function+right arrow for end. I use control+home or control+end quite a bit, so I was actually happy to see that this was the shortcut rather than having to reach up to the function row for home and end. That combination works as intended as long as you hit the control key first, so you hit control+function+left arrow to go to the top of the page. Have your friend try it, making sure that the first key pressed is control.