Windows 11 Pro update error 0x80070005 for all LCU updates

[cybot]

I have an issue that does not seem to be able to be fixed through common means. the LCU (latest cumulative updates) for windows are refusing to install. windows downloads and installs and gets to 100% before giving an 0x80070005 error. I am aware that this is an access denied error, but am unable to determine exactly WHAT action is being denied. All i know for certain, is that when the issue occurs, tiworker.exe crashes with expecting module CBScore.dll with exception 0xc0000005, which is also an access denied error. as far as i can tell, the update is failing midway, placing the updated files, or at least setting up where they should go, but then never properly finishing. as a result, dism will occasionally remove the updated files or just not find any corruption. I have tried multiple times running SFC and DISM with out any errors being found. i have run windows setup to do a repair install multitple times, and the issue persists. in an effort to try and solve the issue, thinking maybe it was a bug in windows itself or something, I installed the release preview for win 11 24H2, but was unable to install the LCU to take it beyond 26100.1 when the ISO for 26100.1150 was released, i did a repair install using that, and while the build is now 26100.1150, the LCU for 26100.1270 fails to install with the same update error. even trying to run windows setup with dynamic updates is failing to solve the issue. the best way to begin troubleshooting windows update, the windows update troubleshooter has been transitioned to the gethelp app in 24h2, but when i attempt to run the update trouble shooter i get an error saying that the 'Windows update diagnostic has failed to run.' I don't know if this is because of the issue in my system, or because the feature has a bug. I did download a copy of the older version of the troubleshooter, but it was unable to detect or fix anything. i would really like to avoid a windows reset or factory restore i can. reinstalling all my stuff is a major pain in the ass, mostly because i have a low speed DSL connection. this issue started on win 11 22H2 and followed me too 23H2 and now 24H2. i have since read that it is unwise to perform an upgrade when there is an issue like this that isn't solved by a repair install. --- OOPS. It might be possible there is an issue with the Components Registry hive, but it is doubtful, as i can load and unload the hive from within windows using the reg /load command. if i could get help examining the components hive in order to rule that out, it would be a big help.

 

[cybot]

Seems my issue might be a failing nvme drive. The 256gb nvme is the original drive supplied by MSI with the unit. This is my first ssd, so i am not aware of the symptoms. I watched my file system breakdown before my eyes as my repair efforts continued. The tipping point seemed to occur after a failed windows repair install. At that point Windows was still running, even though setup had failed according to the logs I found, failure occured during the boot file transfer phase. I looked at my bcd file only to find it thoroughly trashed. I also found the efi partition had been assigned a drive letter that was accessable from the command prompt, but. It from with in windows. The issue seemed to go away after rebooting, but the bcd remained thrashed. Attempts at repairing it led me to boot to the recovery environmentl to rebuild the bcd.only problem was, because the bcd was thrashed, the RE variables were not present to boot to. To Microsoft's credit, I managed to get windows to boot to a basic recover mode. I tried rebuilding the bcd, but access was denied. Bootrec and so on could find my install, but not work on it. I tried booting back to windows, and things got even worse. Windows booted, and so did all my startup programs, but anytime i tried to open any file a strange file system error dialog I don't have the exact error but it was a parenthesis followed by a minus sign and a bunch of numbers.. at this point in decided to bite the bullet and perform a system restore. Thing looked like they went well, and the software said recovery and install of windows 10 was successful, but when a reboot was called for, nothing had changed, further more, the filesystem of c:\ was not touched. Thinking that had an issue, I dug out the flash drive I madevg it was maybe the recovery files on the system when it was powered on for the very first time. Surprisingly it did the exact same thing!. Just to rule out the recovery flash drive, I went over to a duplicate system (same model, same exact hardware and OS setup,) and made a fresh copy. I tried again with the same results. It seems like the drive is still able of to read the data present, but is no longer able to write any new data. Is this something normal when an nvme ssd fails? I have ordered a replacement drive already - along with a memory upgrade 16gb 2666 to 32gb 3200 (2x16gb) I will be installing the new drive - a wd_black sn850x which should be a signifigant upgrade for my systems storage. Any comments, questions or responses are welcome.