microsoft.windows.shellexperiencehost not installed correctly

I deleted Chrome off the old SSD and I haven't had any issues since. The SSD wasn't going bad-I'd used CACLS to disable read/write access to Chrome's software_reporter_tool.exe and for whatever reason it was hard locking my computer.

If I boot into the Windows installation on the old SSD, everything loads fine so it's absolutely something with the new Windows installation and not a hardware issue. I'd rather keep that option disabled entirely, but it has turned startup into a 45 second process, so I'm at a loss with what to do. Going to Windows settings and enabling that sign-in option 'fixes' the issue and it starts loading applications at the sign-in screen again. The keyboard itself has four different programming modes, one of which is used so you can enter the BIOS without loading any special drivers, but the issue persists even if it's set to that mode. That gets me video but I still need to use the on-screen keyboard with the mouse to login, where my keyboard finally operates normally. To continue, I have to unplug both of the keyboard's USB cables, power cycle the monitor, and plug the keyboard back in. I'm left with a black screen (although the monitor LED is blue instead of orange, indicating it is receiving a video signal) and a keyboard that isn't responsive. Unfortunately, when that setting is disabled, both my monitor (XB271HU) and keyboard (Corsair K65) refuse to work when I turn the computer on. I disabled that option for three reasons: it wasn't enabled previously, I only have a couple non-Windows programs at startup on an SSD, making the speed boost pointless, and I'm paranoid there's a glaring security issue with applications loading prior to signing in. By default on new WIn10 installations, Settings > Accounts > Sign-in Options has 'Use my sign-in info to automatically finish setting up my device and reopen my apps after an update or restart' checked by default. There is one thing driving me up the wall, though, and I'd appreciate any advice. After doing some weird stuff that wasn't ever necessary previously (creating a Microsoft account and then linking said account to create USB installation media, for example), I got Windows 10 installed on the new SSD without many issues. My SSD from 2013 started giving me issues a few weeks back and would hard lock the computer 30-45 sec after getting to the desktop, so I went out and bought a new 1TB SSD. Some modifier key stuck being held down for some reason maybe? Won't somebody think of the starving hamsters in China?

Microsoft.windows.shellexperiencehost not installed correctly