[SOLVED] Unable to install Cumulative Updates since 2023-12 - Windows 10 22H2 (19045.3570)

Update time: (thanks both for your help so far, I admit I may have been in denial about the free space :ROFLMAO:)
I've ordered a 256GB replacement drive to sort out my space issue. However, I would like to try and get my current drive's install at least bootable again so I can get an in place upgrade going once the install has 100GB free space more to play with.

Using a boot CD over the past few days, I've fully repaired the EFI partition (eliminating the 0xc0000001 error I got too) and used DISM to massively repair the corruption (over 9000+!) by using a donor WinSxs file store from another laptop. Whilst my first pass took out 9000ish corruptions, there are 400+ files still remaining. Both of the other laptops I have access to are fully up to date, and lack some older files, so I'm unable to progress beyond this. I've tried hooking up to Windows Update, but it can't locate these older files.

I'm attaching the DISM log I just generated; if either of you are able to please zip these up for me so I can splice them into my donor Sxs setup, I would appreciate it very much.

Thanks again
 

Attachments

Hi,

Please attach the latest CBS logs, the DISM is not very helpful in cases like this.

Upload a copy of the CBS folder
  • Open Windows Explorer and browse to the C:\Windows\Logs folder.
  • Right-click on the CBS folder and choose Send to > Compressed (zipped) folder.
  • Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
  • Click on the Yes button here.
653a64385d891-618e949e09fef-CBS-Folder.png

  • Attach the file CBS.zip to your next reply. If the file is too large to attach, upload the CBS.zip file to www.wetransfer.com and post the link in your next reply.
 
Have no idea how useful this will be, as it's from the day it stopped booting. The boot USB I'm using (Hiren's Boot CD PE) doesn't generate any CBS logs on it's X:\ drive, only DISMs. Could only get the FilterList from that drive
 

Attachments

I would suggest to boot into Windows (normal mode) and then run DISM again, so when can take a look at the new CBS log to see which files are missing.
 
I still can’t boot into Windows or Safe Mode. Doing so doesn’t update the CBS logs for me I’m afraid
 
My bad, I’ll clarify;
A few times after the boot loop, I got the 0xc000001 error too. The EFI rebuild fixed that, but I still get the loop.

Thanks for checking for me
 
A number of the missing payload files are a part of (19041.3635) KB5033052, this update is not availabe in the Windows Update Catalog and I can't find a direct link either.
I've checked 8 VM's and 3 physical system as well, but on none of them I could find those files anymore. So I reloaded an older image and with succes, attached a copy of all the missing payload files.
 

Attachments

No luck. DISM completes successfully and SFC reports no errors now but Windows still won't boot. I tried disabling Automatic Repair but it doesn't help
 

Attachments

I would suggest to use the Hiren's boot CD again to free space on your current drive so you will have at least 15GB of free space. Then you can try the reset this pc option from the troubleshoot window.
 
Ok, I'll give that a shot (preferably when the new drive is here and I can image it over to get even more space).

One last idea; seeing as FRST was in the boot process just before it stopped booting (it was restarting after the Fixlist), is there any way of removing it from the boot process from within the boot CD environment? Was just thinking that in between the space problem and the update, it may be interfering in some way?
 
You can also use Macrium Reflect to create a full image of the system drive, with the option image this disk and save it on your D drive. I would suggest using a rescue USB-stick which is created with Macrium Reflect to do that rather than Hiren's Boot CD.
Code: 
Drive c: (Windows) (Fixed) (Total:118.01 GB) (Free:5.87 GB) (Model: SAMSUNG MZNTY128HDHP-000H1) NTFS
Drive d: (DATA) (Fixed) (Total:919.64 GB) (Free:440.72 GB) (Model: HGST HTS721010A9E630) NTFS
The EmptyTemp: directive will only set a reboot flag, but for some reason it couldn't complete. However, this is not a specific setting which can be removed since it is just a runonce task. So I don't think this is the issue or remnant which may conflict.

I am still sure that the lack of disk space is the core issue and caused the system crash. In the latest CBS log we could also see that there was something wrong with the BCD-template file. See post #39, so it's more likely that this file become corrupted (C:\Windows\System32\config\BCD-Template).
 
Ok thanks, was just checking.

I imaged the drive earlier using Macrium Reflect immediately after you sent the files and eliminated my DISM errors.

Two more questions:
1. Seeing as I fixed the EFI, I assume the BCD-Template is something different (i.e. part of the registry). I noticed before I ever ran it for the first time, FRST backed up the registry, including a BCD file. Is this the BCD-Template, and if so, can I replace it?
2. If I image the drive across to my new one (keeping the system/EFI the same whilst massively resizing the Windows partition) and ruled out the BCD-Template, would this give Windows the space it needs to sort itself out? I've set the RevertPendingActions flag in DISM to halt any pending update issues.
 
1. Can you please provide a copy of the BCD file from the folder C:\FRST\Hives to check the hash value below.
Code: 
2024-01-30 15:52:34, Info                  CSI    00009634 Hashes for file member [l:12]'BCD-Template' do not match.
 Expected: {l:32 ml:33 b:c6ea8c6596bf0b4e8b3b5acf8383a11113b00acb495866fdb5e45a537c4c37ec}.
 Actual: {l:32 b:e2dd5091d036bef962c4126d6df1722d1bc19496e97f3c95565fdcbae6e74051}.
2. When cloning your current drive to a new SSD you'll need to resize it manually, so far as I know Macrium Reflect will not automatically add the unassigned space to your system partition.

To give a more detailed answer, we could also take a look at this file C:\Windows\System32\Logfiles\Srt\SrtTrail.txt

Just to see which errors are reported..
 
Rich (BB code): 
Root cause found:
---------------------------
Unknown Bugcheck: Bugcheck ef. Parameters = 0xffffb3825d393280, 0x0, 0x0, 0x0.

Repair action: System files integrity check and repair
Result: Failed. Error code =  0x57
Time taken = 1219 ms

Please check if there are any recent *.dmp files in C:\Windows\Minidump
If so attach them in your next reply.
 
No files unfortunately, not even the folder.
Good news is that the drive should be here tomorrow (was told earlier that there was a stock issue with the 256GB, so I paid slightly extra and upgraded the order to the 512GB instead), so I'll report back once I've installed and imaged over.

A quick look at the 0x0, 0x0, 0x0 part online did seem to say it may be due to a lack of resources/space, so we'll see what happens
 
DM-TGG said:
No files unfortunately, not even the folder.
Click to expand...
That's what @x BlueRobot already expected that those *.dmp files not been generated due to the lack op space.

DM-TGG said:
Good news is that the drive should be here tomorrow (...) so I'll report back once I've installed and imaged over.
Click to expand...
Great, keep us posted...
 
Drive came, fitted it, imaged everything across and expanded the Windows partition, giving it several hundred GBs more to play with…


Still nothing, no minidumps, no DISM or SFC errors

Is there a setting in the registry I’m not aware of that triggers minidumps to be created? There’s no % on the BSOD screen, so doesn’t seem like it was trying and failing because of the space issue before
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top