by the way, Windows Update now shows error 0xc1900101 on the 23H2 repair version
Error Code 0x8007000d Windows 11 update to 23H2 or 24H2
Windows update always fails with 0x8007000d when trying to update to 23H2.
I also tried repair version, same error.
I also tried Windows 11 install assistant with downloading 24H2. It also fails with 0x8007000d
System info:
Edition Windows 11 Pro
Version 23H2
Installiert am 10.08.2024
Betriebssystembuild 22631.4037
Leistung Windows Feature Experience Pack 1000.22700.1027.0
I wanted to try the fix provided here, but the file seems not available anymore: https://answers.microsoft.com/en-us/windows/forum/all/error-code-0x8007000d-when-trying-to-download/38b4f762-073b-4c27-ae9e-1f95e5ca9e86
Kindly assist with help to upgrade to 24H2
Windows for home | Windows 11 | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
19 answers
Sort by: Most helpful
-
Anonymous
2024-12-23T12:16:38+00:00 -
Anonymous
2024-12-23T12:15:14+00:00 Loading registry hive from C:\Windows\System32\config\COMPONENTS
Parsing loaded hive, please wait...
Hive parsed successfully - found 127.744 keys and 160.131 values
Starting corruption scan
Performing regedit load test
Scanning CanonicalData\Catalog for corruptions
Scanning CanonicalData\Deployments for corruptions
Scanning DerivedData\Components for corruptions
Scanning VersionedIndex...\ComponentFamilies for corruptions
Checking WinSxS catalogs against CanonicalData\Catalogs
Checking WinSxS components against DerivedData\Components
Checking f! marks
Checking manifests
Checking for malformed Deployment keys
Checking CatalogThumbprints & c! marks
Generating report
The corruption scan completed after 4,99 seconds.
No corruptions were detected in the COMPONENTS hive.
ComponentsScanner Version 1.5.1.0 by sysnative.com
Windows Version: Windows 11 23H2 x64 (10.0.22631.4037)
Start time: 2024-12-23T13:14:31
Hive scanned: %windir%\System32\config\COMPONENTS
Number of keys: 127744
Number of values: 160131
==== Critical Errors ====
None
==== Corrupt Key Names ====
None
==== Corrupt Value Names ====
None
==== Corrupt Value Data Type ====
None
==== Corrupt Value Data ====
None
==== Repair Log ====
No possible repairs
==== Warnings ====
None
Storing 0KB in C:\Users\tobia\AppData\Local\Sysnative\ComponentsScanner
Finish Time: 2024-12-23T13:14:48. Corruption scan time: 4,9682891s
===========================EOF===========================
-
Ramesh Srinivasan 81,450 Reputation points Independent Advisor
2024-12-23T11:19:02+00:00 The CBS key is fine. The problem may be in the COMPONENTS registry hive. Please run ComponentsScanner (64-bit) and let it repair the COMPONENTS hive. See if it fixes anything.
https://www.sysnative.com/forums/threads/how-to...
Post the output here.
Standard Disclaimer: There is a link to a non-Microsoft website. The page appears to provide accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as PUPs (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.
-
Ramesh Srinivasan 81,450 Reputation points Independent Advisor
2024-12-23T10:42:28+00:00 Please run:
dism /online /cleanup-image /scanhealthOnce it completes, share the following files on OneDrive.
C:\Windows\logs\cbs\cbs.log
C:$WINDOWS.~BT\Sources\Panther\setupact.log