Hi, Portland. I used Method 1 as described in this article.
Repair Windows 10 or 11 Using Command Prompt (5 Ways) (ubackup.com)
It took a long time to scan/repair, but it worked. You can also watch people doing it on YouTube, but I like the stills better for following along.
I should say that the idea was prompted when I did a Norton scan and it told me it found 198 broken registry items and wanted me to buy an add-on service to repair them for me. I went on a Google search, figuring there must be something built into the system to do this, and it turned out I was right! And just to be very clear, this was on a computer where I had not messed with any registry edits. Apparently it can happen from anything from malware attempts to old programs removed but leaving stuff behind.
Once that scan was done, I did do Method 2 for good measure. It took even longer but came up clean in the end. I ran Method 1 on my Surface Pro and it took a fraction of the time it had on my old desktop and came up clean, no registry errors. Which is nice, given that I had done the big, scary registry edit to block Windows 11.