Help me Error 0x80071160

letitgo

letitgo

Member
Joined
Jan 31, 2020
Posts
11
Hye,i cannot update,always come with this error

2020-01 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 1909 for x64 (KB4534132) - Error 0x80071160

i tried sfc /scannow & sfcfix

PnTSBup.png


Window 10 pro 64-bit build 18363
 
Thanks.

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
i3yiUac.png


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.
 
softwaremaniac said:
Thanks.

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
i3yiUac.png


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.
Click to expand...
thank you

Logfile.zip (40.21MB) - SendSpace.com

for CBS.log do i need to upload again?if yes,i need to repeat any process?or just upload the previous CBS folder?
 
softwaremaniac said:
Yes, please repeat the process with the CBS.log.
Click to expand...
Sorry,just want to make sure i do it in correct way

1, Run PROCESS MONITOR
2, Update windows
3, Stop the process as soon as it fail
4, Save the log file

5, Run SFC scan
6, SURT/DISM scan
7, Run SFCfix


8, Upload CBS folder together with logfile from step 4


correct?
 
SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.



SFC Scan


  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 

Attachments

softwaremaniac said:
SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.



SFC Scan


  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
Click to expand...


[CODE]SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-02-04 13:50:29.409
Microsoft Windows 10 Build 18363 - amd64
Using .zip script file at C:\Users\fuchs\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\Defender.psd1
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpComputerStatus.cdxml
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpPreference.cdxml
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpScan.cdxml
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpSignature.cdxml
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpThreat.cdxml
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpThreatCatalog.cdxml
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpThreatDetection.cdxml
Successfully took permissions for file or folder C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpWDOScan.cdxml

Successfully copied file C:\Users\fuchs\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\Defender.psd1 to C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\Defender.psd1.
Successfully copied file C:\Users\fuchs\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpComputerStatus.cdxml to C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpComputerStatus.cdxml.
Successfully copied file C:\Users\fuchs\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpPreference.cdxml to C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpPreference.cdxml.
Successfully copied file C:\Users\fuchs\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpScan.cdxml to C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpScan.cdxml.
Successfully copied file C:\Users\fuchs\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpSignature.cdxml to C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpSignature.cdxml.
Successfully copied file C:\Users\fuchs\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpThreat.cdxml to C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpThreat.cdxml.
Successfully copied file C:\Users\fuchs\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpThreatCatalog.cdxml to C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpThreatCatalog.cdxml.
Successfully copied file C:\Users\fuchs\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpThreatDetection.cdxml to C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpThreatDetection.cdxml.
Successfully copied file C:\Users\fuchs\AppData\Local\niemiro\Archive\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpWDOScan.cdxml to C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpWDOScan.cdxml.

Successfully restored ownership for C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\Defender.psd1
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\Defender.psd1
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpComputerStatus.cdxml
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpComputerStatus.cdxml
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpPreference.cdxml
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpPreference.cdxml
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpScan.cdxml
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpScan.cdxml
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpSignature.cdxml
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpSignature.cdxml
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpThreat.cdxml
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpThreat.cdxml
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpThreatCatalog.cdxml
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpThreatCatalog.cdxml
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpThreatDetection.cdxml
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpThreatDetection.cdxml
Successfully restored ownership for C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpWDOScan.cdxml
Successfully restored permissions on C:\WINDOWS\winsxs\amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.449_none_399f5f2632e852c4\MSFT_MpWDOScan.cdxml
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 9 datablocks.
Finish time: 2020-02-04 13:50:36.081
Script hash: UZ8vN/CB7TdpY6gxVRwDhPVYVtViZrZLOVZanFW4sCg=
----------------------EOF-----------------------[/CODE]
 

Attachments

Step#1 - DISM /RestoreHealth Scan
Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Right-click on the Start button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
    Dism /Online /Cleanup-Image /RestoreHealth
  3. Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
    Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
softwaremaniac said:
Step#1 - DISM /RestoreHealth Scan
Warning:this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Right-click on the Start button and select Command Prompt (Admin)
  2. When command prompt opens, Copy (Ctrl+C) and Paste (Right-click > Paste) the following command into it, then press Enter
    Dism /Online /Cleanup-Image /RestoreHealth
  3. Once it finishes, copy and paste the following into the command-prompt window and press Enter. If prompted to overwrite the existing file go ahead.
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. Once this has completed please go to your Desktop and you will find CBS.txt => Please zip/upload to this thread.
    Please Note:: if the file is too big (over 7MB) to upload to your next post, please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
Click to expand...
 

Attachments

Step#1 - FRST Scan

1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Right-click FRST64.exe and click Run as Administrator to run it as administrator. When the tool opens, click Yes to disclaimer.
3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already checked).
4. Press Scan button.
5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop)
6. Please attach the log back here.
7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also attach that along with the FRST.txt in your reply.
 
softwaremaniac said:
Step#1 - FRST Scan

1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Right-click FRST64.exe and click Run as Administrator to run it as administrator. When the tool opens, click Yes to disclaimer.
3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already checked).
4. Press Scan button.
5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop)
6. Please attach the log back here.
7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also attach that along with the FRST.txt in your reply.
Click to expand...
 

Attachments

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