Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Hi!
I only see the CBS.log, not the LogFile.PML from ProcMon.
I only see the CBS.log, not the LogFile.PML from ProcMon.
[SOLVED] Error Code 0x80073712
- Thread starter bluezeus
- Start date
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
I see that you have uploaded the logfile. Unfortunately, when I try to extract it, I get the message that the archive is corrupt.
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Hi!
What's the currently installed -NET Framework version?
Please do the following:
Using the .NET Collect Utility
What's the currently installed -NET Framework version?
Please do the following:
Using the .NET Collect Utility
- Download collect.exe and save to your desktop.
- Go ahead and run the tool
- The utility creates a compressed cabinet of all the needed logs to %TEMP%\vslogs.cab.
- Please zip/attach to this post or if too large, send using a service such as SendSpace.
Hi,
<32Bit>
2.0.50727.8806
->C:\Windows\Microsoft.NET\Framework\v2.0.50727
4.7.3416.0
->C:\Windows\Microsoft.NET\Framework\v4.0.30319
<64Bit>
2.0.50727.8806
->C:\Windows\Microsoft.NET\Framework64\v2.0.50727
4.7.3416.0
->C:\Windows\Microsoft.NET\Framework64\v4.0.30319
< Installed .NET Frameworks >
.NET FW 2.0 SP 2 (CLR:2.0)
.NET FW 3.0 SP 2 (CLR:2.0)
.NET FW 3.5 SP 1 (CLR:2.0)
.NET FW 4.6.2 General release (CLR:4.0)
.NET FW 4.7 General release (CLR:4.0)
.NET FW 4.7.1 General release (CLR:4.0)
.NET FW 4.7.2 General release (CLR:4.0)
< Installed Updates >
Microsoft .NET Framework 4 Client Profile
KB2468871
KB2468871v2
KB2478063
KB2533523
KB2544514
KB2600211
KB2600217
Microsoft .NET Framework 4 Extended
KB2468871
KB2468871v2
KB2478063
KB2533523
KB2544514
KB2600211
KB2600217
KB2468871
KB2468871v2
KB2478063
KB2533523
KB2544514
KB2600211
KB2600217
Microsoft .NET Framework 4 Multi-Targeting Pack
KB2504637 Update for (KB2504637)
< Installed Languages 3.0>
English - United States
< Installed Languages 3.5.x>
English - United States
< Installed Languages 4.x>
English - United States
This is VSLog
<32Bit>
2.0.50727.8806
->C:\Windows\Microsoft.NET\Framework\v2.0.50727
4.7.3416.0
->C:\Windows\Microsoft.NET\Framework\v4.0.30319
<64Bit>
2.0.50727.8806
->C:\Windows\Microsoft.NET\Framework64\v2.0.50727
4.7.3416.0
->C:\Windows\Microsoft.NET\Framework64\v4.0.30319
< Installed .NET Frameworks >
.NET FW 2.0 SP 2 (CLR:2.0)
.NET FW 3.0 SP 2 (CLR:2.0)
.NET FW 3.5 SP 1 (CLR:2.0)
.NET FW 4.6.2 General release (CLR:4.0)
.NET FW 4.7 General release (CLR:4.0)
.NET FW 4.7.1 General release (CLR:4.0)
.NET FW 4.7.2 General release (CLR:4.0)
< Installed Updates >
Microsoft .NET Framework 4 Client Profile
KB2468871
KB2468871v2
KB2478063
KB2533523
KB2544514
KB2600211
KB2600217
Microsoft .NET Framework 4 Extended
KB2468871
KB2468871v2
KB2478063
KB2533523
KB2544514
KB2600211
KB2600217
KB2468871
KB2468871v2
KB2478063
KB2533523
KB2544514
KB2600211
KB2600217
Microsoft .NET Framework 4 Multi-Targeting Pack
KB2504637 Update for (KB2504637)
< Installed Languages 3.0>
English - United States
< Installed Languages 3.5.x>
English - United States
< Installed Languages 4.x>
English - United States
This is VSLog
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Please try the standalone installer for .NET Framework.
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Great!
Can you run Collect.exe now again and attach the output.
Can you run Collect.exe now again and attach the output.
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Please download the cleanup tool and then retry the setup. Download Microsoft .NET Framework Cleanup Tool - MajorGeeks
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Great!
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Excellent! We were happy to help!
Hello,
I reopen this post, because on the same server the same error occurred for the KB4534283 update, these are the results obtained:
Step #2 - Run SFC Scan
Windows Resource Protection did not find any integrity violations.
Step #3 – SURT/DISM Scan
C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 6.2.9200.22807
Image Version: 6.2.9200.22807
[==========================100.0%==========================]
Error: 0x800f0906
The source files could not be downloaded.
Use the "source" option to specify the location of the files that are required t
o restore the feature. For more information on specifying a source location, see
Configure a Windows Repair Source.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Step #4 - Run SFCFix
This is results without log file.
Checking store directories . . .
Checking CBS.log . . .
Checking CheckSUR.log . . .
Checking CheckSUR.persist.log . . .
Attempting repair . . .
Stage 1
Stage 2
Stage 3
Due to the nature of your corruptions, scan times have been extended by
approximately 15-20 minutes. Please be patient and allow the operation to
complete.
Deployment Image Servicing and Management tool
Version: 6.2.9200.22807
Image Version: 6.2.9200.22807
[==========================100.0%==========================]
Error: 0x800f0906
The source files could not be downloaded.
Use the "source" option to specify the location of the files that are required t
o restore the feature. For more information on specifying a source location, see
Configure a Windows Repair Source.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Step #5 – Export/Upload CBS folder
CBS.zip
I reopen this post, because on the same server the same error occurred for the KB4534283 update, these are the results obtained:
Step #2 - Run SFC Scan
Windows Resource Protection did not find any integrity violations.
Step #3 – SURT/DISM Scan
C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 6.2.9200.22807
Image Version: 6.2.9200.22807
[==========================100.0%==========================]
Error: 0x800f0906
The source files could not be downloaded.
Use the "source" option to specify the location of the files that are required t
o restore the feature. For more information on specifying a source location, see
Configure a Windows Repair Source.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Step #4 - Run SFCFix
This is results without log file.
Checking store directories . . .
Checking CBS.log . . .
Checking CheckSUR.log . . .
Checking CheckSUR.persist.log . . .
Attempting repair . . .
Stage 1
Stage 2
Stage 3
Due to the nature of your corruptions, scan times have been extended by
approximately 15-20 minutes. Please be patient and allow the operation to
complete.
Deployment Image Servicing and Management tool
Version: 6.2.9200.22807
Image Version: 6.2.9200.22807
[==========================100.0%==========================]
Error: 0x800f0906
The source files could not be downloaded.
Use the "source" option to specify the location of the files that are required t
o restore the feature. For more information on specifying a source location, see
Configure a Windows Repair Source.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Step #5 – Export/Upload CBS folder
CBS.zip
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Hi!
Please run DISM again and attach a fresh CBS.log after its run.
Please run DISM again and attach a fresh CBS.log after its run.
Hi,
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Windows>Dism /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 6.2.9200.22807
Image Version: 6.2.9200.22807
[==========================100.0%==========================]
Error: 0x800f0906
The source files could not be downloaded.
Use the "source" option to specify the location of the files that are required t
o restore the feature. For more information on specifying a source location, see
Configure a Windows Repair Source.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
This is log:
CBS.zip
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Windows>Dism /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 6.2.9200.22807
Image Version: 6.2.9200.22807
[==========================100.0%==========================]
Error: 0x800f0906
The source files could not be downloaded.
Use the "source" option to specify the location of the files that are required t
o restore the feature. For more information on specifying a source location, see
Configure a Windows Repair Source.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
This is log:
CBS.zip
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
I'm having issues accessing the files.
Can you open the CBS log and copy the part starting with: Checking System Update Readiness for me into a separate notepad document.
Thanks.
Can you open the CBS log and copy the part starting with: Checking System Update Readiness for me into a separate notepad document.
Thanks.
Checking System Update Readiness.
(p) CSI Manifest Corrupt wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_11.4.9600.19572_none_de8c6dad9da71a5e
Repair failed: Missing replacement manifest.
(p) CSI Payload Corrupt msil_system.xaml_b77a5c561934e089_4.0.9296.16627_none_49b98219c75fdfa4\System.Xaml.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt x86_netfx4-clrjit_dll_b03f5f7f11d50a3a_4.0.9296.16601_none_7fc481119c558a85\clrjit.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_netfx4-mscordacwks_dll_b03f5f7f11d50a3a_4.0.9296.16830_none_f9832e35073e35f4\mscordacwks.dll
Repair failed: Missing replacement payload.
Summary:
Operation: Detect and Repair
Operation result: 0x800f0906
Last Successful Step: Entire operation completes.
Total Detected Corruption: 4
CBS Manifest Corruption: 0
CBS Metadata Corruption: 0
CSI Manifest Corruption: 1
CSI Metadata Corruption: 0
CSI Payload Corruption: 3
Total Repaired Corruption: 0
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: True
Total Operation Time: 3566 seconds.
(p) CSI Manifest Corrupt wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_11.4.9600.19572_none_de8c6dad9da71a5e
Repair failed: Missing replacement manifest.
(p) CSI Payload Corrupt msil_system.xaml_b77a5c561934e089_4.0.9296.16627_none_49b98219c75fdfa4\System.Xaml.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt x86_netfx4-clrjit_dll_b03f5f7f11d50a3a_4.0.9296.16601_none_7fc481119c558a85\clrjit.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_netfx4-mscordacwks_dll_b03f5f7f11d50a3a_4.0.9296.16830_none_f9832e35073e35f4\mscordacwks.dll
Repair failed: Missing replacement payload.
Summary:
Operation: Detect and Repair
Operation result: 0x800f0906
Last Successful Step: Entire operation completes.
Total Detected Corruption: 4
CBS Manifest Corruption: 0
CBS Metadata Corruption: 0
CSI Manifest Corruption: 1
CSI Metadata Corruption: 0
CSI Payload Corruption: 3
Total Repaired Corruption: 0
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: True
Total Operation Time: 3566 seconds.
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. Please copy this file to your desktop.
Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
3. Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or SendSpace and then just provide the link in your reply.
Has Sysnative Forums helped you? Please consider donating to help us support the site!