May 13 Windows Update automatic repair loop

My comp was working great for since the new SSD installed windows 11. Then today, after it updated last night, I am stuck in the reboot loop.

My bios screen says scanning and repairing errors and it gets BAD_SYSTEM_CONFIG_INFO (0x74). It takes me to Windows repair and I am now stuck in the loop no matter what I've tried.

I've tried a reboot, still reboot loop.

I've tried to uninstall the latest quality update and it said "you have pending actions and we won't be able to install the latest quality update of windows. Try running startup repair instead." I tried to uninstall the latest feature update and it said "we ran into a problem and won't be able to uninstall the latest feature update. Try resetting your PC."

Then I tried system recover which I have for 5/13 5/12 and 5/10. Each of those I can only select the D (HDD) drives and not my C (SSD). D (system) says ready to restore under the "status" column but for each of those restore points I try it says "the disk D has errors

Windows has detected file system corruption. You must check the disk for errors before it can be restored." I then click check drive for errors and the next screen says "error checking C: we havent found any errors on this drive." I scan anyway and it says "error checking C. Windows found errors on this drive that needs to be repaired. Close this dialogue box and repair the drive." This is repeated for all 3 restore points. I go back to the system restore screen to choose which date and time, and I press "scan for affected programs" and it said "unexpected error. An I/O operation initiated by registry failed unrecoverably. Registry could not read in or write out or flush one of the files that contain the systems image of the registry (0x800703F8).

So now I went to reinstall windows 11 on the SSD. I can't even do that! It says "installation is not supported for the file system on the current partition. Bitlocker drive encryption is enabled on the selected partition. Suspend bitlocker in control panel and restart"

Does anyone have a resolution/workaround for this?