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

Rich (BB code): 
2024-01-30 15:52:48, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80070070 - ERROR_DISK_FULL]

How many free disk space is available? It seems you're system drive has a lack of free space.

Download the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link
  • Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
  • Right-click to run the tool as administrator. When the tool opens click Yes to disclaimer.
  • Note: Ensure that the Addition.txt check box is checked at the bottom of the form within the Optional Scan area.
  • Press the Scan button.
  • Please wait for the tool to finish. It will produce two logfiles called FRST.txt and Addition.txt in the same directory the tool is run from (which should be the desktop)
  • Post the logfiles FRST.txt and Addition.txt as attachment in your next reply.
 
Rich (BB code): 
Drive c: (Windows) (Fixed) (Total:118.01 GB) (Free:5.87 GB) (Model: SAMSUNG MZNTY128HDHP-000H1) NTFS

This is definitely the problem for now, so I would suggest to do the following which will cleanup the system.

Start the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool again.

Warning: This script was written specifically for this system. Do not run this script on another system.
  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST.exe and select "Run as administrator".
  • Press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.

Please let me know how many free space is available after running this fix and the reboot.
 

Attachments

The fix completed but now my laptop won’t start, it just goes into the “Preparing Automatic Repair” boot loop
 
Strange, this fix did nothing special rather than removing some remnants and cleaning up temp folders.

However, this problem is related to the following error (before cleaning up the system) and has to due with the lack of free space on this system.
Rich (BB 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}.

Do you have a recent backup to restore?
 
Just a generic message about Windows failing to start; if I try Startup Repair it fails. No specific code is given
 
Yes, restarting or going to Advanced Options to run Startup Repair also does nothing
 
Under Advanced Options do you have the option Troubleshoot > Reset this PC...
 
Then I would suggest to backup all your personal data first from this system with e.g. an Linux USB-stick. And then perform a reset with the Keep My Files option.

When a system has a severe lack of free disk space (like this case) it may cause a lot of issues.

Code: 
Drive c: (Windows) (Fixed) (Total:118.01 GB) (Free:5.87 GB) (Model: SAMSUNG MZNTY128HDHP-000H1) NTFS

If this this system is up-and-running again, I would suggest to upgrade this SSD. Or to be sure there's always some free space amount of 15 ~ 20GB.
 
Question; as this is space related (even though I’ve never had this specific issue before), if I were to buy a new SSD (it’s an old spec so would only cost me £30 or so for a 256GB) and them image the drive across with Macrium Reflect, would Windows then boot?
 
It is certainly a problem with free space, and cloning is not an option to resolve this issue. I would suggest to backup your data (free up some space) and then perform a repair install first to see if you can boot normally.
 
What registry entries, files and folders did your fix file delete? I’ve played around with both the Windows 10 install USB and Ubuntu, as well as the repair tools; from what I can tell from the log files, my issues are nothing to do with my drive’s free space. Whatever was in the fix file has caused some form of system file corruption; even Safe Mode fails with a BSOD CRITICAL PROCESS DIED error…
 
DM-TGG said:
(...) my issues are nothing to do with my drive’s free space.
Click to expand...

The problems have absolutely to do with this, this is also the reason why the CBS.zip was corrupted in the previous posts. See also the error below, due to the lack of free disk space such corruptions may occur.

Rich (BB code): 
2024-01-30 15:52:48, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80070070 - ERROR_DISK_FULL]
 
I understand that. However, I've never had any issues in the 7 years of having the laptop with Windows failing to boot despite having 7GB free. I've checked via Ubuntu and I still have this 7GB as remaining space. The error you are referring to was a one off in the CBS logs where another program I had running yesterday crashed in the background and dumped a large crash report causing my drive to suddenly fill up and stop that update install; every other failure has been file related. From what I gather online, the Startup Repair message has nothing to do with space and everything to do with something FRST did yesterday
 
Rich (BB 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}.
2024-01-30 15:52:35, Info                  CSI    00009635 Unable to delete directory \??\C:\WINDOWS\SystemApps\Microsoft.MicrosoftEdge_8wekyb3d8bbwe; file microsoft.system.package.metadata exists

2024-01-30 15:52:35, Info                  CSI    00009636 Unable to delete directory \??\C:\WINDOWS\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy; file AccountsService.dll exists

2024-01-30 15:52:35, Info                  CSI    00009637 Warning: Overlap: 61 directory duplicate ownerships detected.
2024-01-30 15:52:35, Info                  CSI    00009638 CSIPERF - FilePI Commit 11521ms
2024-01-30 15:52:46, Error                 CSI    00009639@2024/1/30:15:52:46.073 (F) onecore\base\wcp\sil\ntsystem.cpp(3044): Error STATUS_DISK_FULL originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
[gle=0x80004005]
2024-01-30 15:52:46, Error                 CSI    0000963a (F) STATUS_DISK_FULL #29191537# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = 0, handle = {provider=NULL, handle=0, name= ("null")}, da = (FILE_GENERIC_WRITE), oa = @0x4fee67b5b0->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[188]'\SystemRoot\WinSxS\Temp\PendingRenames\f4e8265e9453da0140f10000902f3432.amd64_microsoft-windows-directui_31bf3856ad364e35_10.0.19041.3930_none_2b6da35ca4022db6_windows.ui.xaml.dll_9c9d9ec9'; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0x4fee67b6[gle=0xd000007f]
2024-01-30 15:52:46, Error                 CSI    78, as = 17533440, fa = (FILE_ATTRIBUTE_NORMAL), sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN_IF, co = (FILE_NON_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
[gle=0xd000007f]
2024-01-30 15:52:46, Error                 CSI    0000963b (F) STATUS_DISK_FULL #29191523# from Windows::Rtl::SystemImplementation::CSystemIsolationLayer_IRtlSystemIsolationLayerTearoff::TransferFileEx(flags = (ReplaceIfExists|MissingFileIsOk), op = 'Copy', odir = NULL, oname = [l:126]'\SystemRoot\WinSxS\amd64_microsoft-windows-directui_31bf3856ad364e35_10.0.19041.3930_none_2b6da35ca4022db6\Windows.UI.Xaml.dll', ndir = NULL, nname = [l:142]'\SystemRoot\WinSxS\Backup\amd64_microsoft-windows-directui_31bf3856ad364e35_10.0.19041.3930_none_2b6da35ca4022db6_wi[gle=0xd000007f]
2024-01-30 15:52:46, Error                 CSI    ndows.ui.xaml.dll_9c9d9ec9', disp = (null))
[gle=0xd000007f]
2024-01-30 15:52:46, Error                 CSI    0000963c (F) STATUS_DISK_FULL #28948975# from PrimitiveInstaller::CCoordinator::FinalizeChanges(...)[gle=0xd000007f]
2024-01-30 15:52:46, Info                  CSI    0000963d SMI Primitive Installer [done]

2024-01-30 15:52:46, Error                 CSI    0000963e (F) STATUS_DISK_FULL #18205054# from CCSDirectTransaction::PerformChangeAnalysis(...)[gle=0xd000007f]
2024-01-30 15:52:46, Error                 CSI    0000963f (F) STATUS_DISK_FULL #18205053# from CCSDirectTransaction::PrepareForCommit(...)[gle=0xd000007f]
2024-01-30 15:52:46, Error                 CSI    00009640 (F) STATUS_DISK_FULL #18205052# from CCSDirectTransaction::ExamineTransaction(...)[gle=0xd000007f]
2024-01-30 15:52:46, Error                 CSI    00009641 (F) STATUS_DISK_FULL #18205051# from CCSDirectTransaction_IRtlTransaction::ExamineTransaction(...)[gle=0xd000007f]
2024-01-30 15:52:46, Error                 CSI    00009642 (F) HRESULT_FROM_WIN32(ERROR_DISK_FULL) #18024634# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Analyze(...)[gle=0x80070070]
2024-01-30 15:52:46, Info                  CSI    00009643 Direct SIL provider: Number of files opened: 117.
2024-01-30 15:52:47, Error                 CSI    00009644 (F) HRESULT_FROM_WIN32(ERROR_DISK_FULL) #17930135# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_Commit(Flags = 47, pSink = NULL, disp = 0)[gle=0x80070070]
2024-01-30 15:52:47, Error                 CSI    00009645 (F) HRESULT_FROM_WIN32(ERROR_DISK_FULL) #17930134# 109484674 us from Windows::ServicingAPI::CCSITransaction_ICSITransaction::Commit(flags = 0x0000002f, pSink = NULL, disp = 0)
[gle=0x80070070]

No, it has nothing to do with the fix with FRST. As I've said several times, the problem is the lack of free space. It is recommended to have at least 15 ~ 20 GB of free space to avoid issues. With only 5GB of free space, it is impossible to update without any issues! This because a regular *MSU package, when unpacked could be > 5 GB in size.

Running out of free space can lead to several issues, like:
- File and registry corruptions while writing data from memory to local disk or even worse data loss.
- System crashes and limited functionality, as you can see in the earlier logfiles; System Restore was already disabled! ATTENTION: System Restore is disabled (Total:118.01 GB) (Free:5.7 GB) (5%)

If you don't believe me that the lack of free space is the issue in here, maybe you will believe a second opinion of @x BlueRobot?
 
DM-TGG said:
from what I can tell from the log files, my issues are nothing to do with my drive’s free space.
Click to expand...
They are, many of the files in the component store are compressed so will need to be decompressed on demand. You've been lucky to run Windows for so long with such little space.

DM-TGG said:
From what I gather online, the Startup Repair message has nothing to do with space and everything to do with something FRST did yesterday
Click to expand...
That FRST script just did some simple clean up operations which certainly wouldn't have left your disk in an unbootable state.

DM-TGG said:
even Safe Mode fails with a BSOD CRITICAL PROCESS DIED error…
Click to expand...
I would have asked for the dump file but doubt that even got generated because of such little disk space. It would/should be saved to %systemroot%\Minidump.
 
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