[SOLVED] Can't install 24H2 Cumulative Updates, In-place repair fails and a lot of breakage

D

deleted0730202401

Member
Joined
Jul 10, 2024
Posts
13
Hello,
Sadly here I think I am a bit in a bad situation with my Windows 11 24H2, build 26100.994. As you will see this is not the latest build because I simply can't install it. Since I got on .994, things got really bad. I of course tried all the fixes I could with DISM, SFC and all the Windows Update known resets but this time nothing helped.

Whenever I try to install a Cumulative Patch in Windows Update I get 0x800f0805, no matter what I do. Sadly not even an in-place repair helped, cause I got:

Error: 0x8007001D-0x20006 The installation failed in the SAFE_OS phase with an error during REPLICATE_OCError: 0x8007001D-0x20006 The installation failed in the SAFE_OS phase with an error during REPLICATE_OC​


So apparently nothing is working and SFC and DISM are reporting all is okay while it's not. I can see there are a lot of things missing in CBS logs and a lot of errors. I will attach them here. I think I am in a bad situation and I hope someone will be able to help, thanks!
 

Attachments

Hi and welcome to Sysnative,

Some notes about using Insider Preview builds:
  • Insider builds of Windows are preview (beta) releases which may contain bugs.
  • If you experience problems with such builds, please use the Microsoft Feedback HUB to report them to Microsoft.
  • To resolve issues you can perform an in-place-upgrade using the latest ISO or an ISO which you can download from UUPdump.
  • Please also note that updates for Insider Builds are not available in the Windows Update catalog as stand-alone updates (MSU-packages).
  • Note of Microsoft: "When choosing a channel, you should keep in mind how stable you need your device to be, what level of issues you can handle on your device, how early in development you'd like to see features and changes, and whether or not you need Microsoft support."
  • Another important point is that issues with Insider Builds can be more complex or even completely unknown than regular problems with stable versions of Windows.
  • Some tools developed by Sysnative are not (fully) compatible with Insider Builds.
 
Hello and thanks for your answer, I was waiting for that so thanks for the support.
Sadly even the in-place upgrade has been failing and this is a very important build sadly. Could you please take a look at my CBS anyway? I am pretty sure this can be fixed... I am totally in your hands 🙏
Many thanks!
 
When this is an important system for daily use, I will never recommend to install (insider builds) which are unstable and/or pretty buggy in most cases.

Export CBS (Component Based Servicing) hive
  • Click on the Start button and type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator.
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
    Code: 
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (*.*).

    622dbef75cd3a-Export-CBS-hive.png

  • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send > Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
Maxstar said:
When this is an important system for daily use, I will never recommend to install (insider builds) which are unstable and/or pretty buggy in most cases.

Export CBS (Component Based Servicing) hive
  • Click on the Start button and type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator.
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
    Code: 
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (*.*).

    622dbef75cd3a-Export-CBS-hive.png

  • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send > Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
Click to expand...
Thanks again for your answer, yes I am very sorry for this situation, putting an insider build was a mistake and once this will be fixed I will make sure to move away from this and not make this mistake again. Sadly this is an important build and I should have considered this before. Thanks for your help.

Once this will be fixed I will strongly consider a donation based on what I have at this time.

I am attaching files as requested.
Cheers!
 

Attachments

As expected the CBS hive is damaged beyond repair, the subkeys (ComponentDetect / Packages) are completely empty. This means that we cannot fix it, so the only resolution would be a fresh install of Windows 11 23H2 (Stable)....

Sorry, but there's no other option since an repair install didn't work either.
 
Thanks, I understand and thanks for your effort. So there might be a chance I will be completely stuck on this build and absolutely nothing can be done? Well... that's seriously concerning, but if that's the only way...
 
Last edited by a moderator:
I also have some backups from 1 month ago, is there a way I could explore them and get the files needed from them (and in case send them here) without having to do a COMPLETE restore? (that would cost dozens of hours)
 
Last edited by a moderator:
Please don't quote my previous posts, that is not necessary!

If you have a recent backup when everything was working fine I would restore the system to that point, just to see if you can stop receiving Insider Preview builds.
 
Sorry also for that, I admit I am a bit shaking because this was a very important setup... Losing all of this and formatting this would be a huge hit I wouldn't know if I would be able to recover from.
Today it's not my lucky day. I just explored the backups from this month and I found out the C: drive was not backupped but just the D:, I feel very very bad now and I struggle even to just describe that.
What would be the consequences of keeping a system like this? (Apart from not being able to update of course).
Wouldn't want to bother since I know there are many people that need help here and the people that can help are very few, but if there's some way even a slight one or something I could try to recover from this, I have to try everything.

Thanks again for your time and I'm sorry if I made you lose some.
 
TheAccountOfTeo997 said:
What would be the consequences of keeping a system like this?
Click to expand...
1. All the Windows Insider builds have an expiration date, so if you can't update to the latest build you will receive (nag) screens / outdated build etc...
2. The Components Based Servicing hive is badly damaged, so this will result in issues installing new features etc...
3. You can wait for the official release (Feature Update) or the ISO of Windows 11 24HX and then perform an in-place-upgrade to see if it will resolve those issues.
 
I understand. Since I am in Release preview (so not properly "Heavy" Insider), this is the RTM build so it does not have an expiration date, so under that side I am okay.
I got an idea but I don't know how stupid that might be and if it can lead to bad consequences, but since your knowledge is awesome you might try to tell me. The only damage here are the ComponentDetect and Packages subkeys or there is other damage?

What would happen if I clean installed the EXACT same build on another machine and move those subkeys to mine? I've just read on a website that someone had this issue, was able to load the hive and then with an enormous amount of work, went through every package and eventually was able to restore. Do you think this might be doable? If so I will take charge of it so I won't make you waste time, just seeking an advice.

Many thanks again!
 
TheAccountOfTeo997 said:
I've just read on a website that someone had this issue, was able to load the hive and then with an enormous amount of work, went through every package and eventually was able to restore.
Click to expand...
With regular (stable) builds is it possible to restore a lot of things in the registry, but this does not apply to Insider Builds.

As stated earlier, the CBS hive is damaged beyond repair! And if you can't restore an full image, then there is nothing left than a fresh install.
 
Hi,

Then you'll need to import this subkey into the Software hive to see what happens.
 
Hello,
I am glad to announce, I just saved my 7 year old build where everyone told me to give up and that there was no possibility ;-)

I basically repopulated the Hive exporting keys from a working ISO, SAME build and then things as packages started to show up.

This morning I SUCCESSFULLY performed an in-place upgrade to the latest version! Now everything should be fresh and infact Windows Update does not complain anymore. Everything is installed and up-to date.

If there are some operations you still want to suggest me after what I did, please go ahead. However I think that after an in-place upgrade everything should be fresh and working.

Remember guys, NEVER lose hope and never give up if your build is very important.

Thanks you for helping me.

Just a quick note, even though 24H2 is still formerly considered Insider, this is basically stable build, as there ARE cumulative packages already on catalog. This is the RTM build

Have a wonderful day
 
Hi,

Glad you have managed to rebuild the corrupt CBS hive this way to perform the in-place-upgrade. I would suggest to make at least regular backups and since this is an important build, I would also suggest to unroll the insider builds. Just to avoid such issues in the future, insider builds as well as preview updates are (beta) releases which may contain bugs.

Personally, I never recommend running such builds on important systems and only in (virtual) testing environments...

Have a great day too... (y)
 
Hello,
Yes thanks. I regularly take backups, but apparently it wasn't my lucky day. I discovered that since the last month, my backup software RANDOMLY decided to exclude the C: partition, this happened in the exact time window where sadly this corruption happened, unlucky!

As for the insider builds I would probably unroll.

Just a last question, I have 3 language packs installed, Italian (main one), english and japanese.

Before the corruption i saw the packages keys also had packages for en-US and ja-JA, now they are missing. Would you advice me to reinstall those language packs?

Cheers
 
You must log in or register to reply here.
Back
Top