A AimarPL Contributor Joined Nov 15, 2018 Posts 97 Feb 7, 2019 #1 Hi, I'm having an issue with WU that fails with update error code 8007371B; Already did dism repair which has repaired store corruption successfully, but then sfc /scannow says it is still corrupted and can't fix what's needed. Under following link you can find CBS logs thank you for any hints!
Hi, I'm having an issue with WU that fails with update error code 8007371B; Already did dism repair which has repaired store corruption successfully, but then sfc /scannow says it is still corrupted and can't fix what's needed. Under following link you can find CBS logs thank you for any hints!
A AimarPL Contributor Joined Nov 15, 2018 Posts 97 Feb 7, 2019 #2 Here's also components file from win/sys32/config: components
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 8, 2019 #3 Hello! I'll start working on a fix and get back to you.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 8, 2019 #5 Step#1 - Export SideBySide Click on the Start button and in the search box, type regedit When you see regedit on the list, right-click on it and select Run as administrator When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide Once selected, click File > Export.... Change the Save as type: to Registry Hive Files (*.*) Name this file SxS (with no file extension) and save it to your Desktop. Once done please upload this file via Dropbox or One Drive or SendSpace. Step#2 - Capture Process Monitor Trace 1. Download and run Process Monitor. Leave this running while you perform the next steps. 2. Try installing the update 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. 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 attach the LogFile.PML file as well as your CBS.log
Step#1 - Export SideBySide Click on the Start button and in the search box, type regedit When you see regedit on the list, right-click on it and select Run as administrator When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide Once selected, click File > Export.... Change the Save as type: to Registry Hive Files (*.*) Name this file SxS (with no file extension) and save it to your Desktop. Once done please upload this file via Dropbox or One Drive or SendSpace. Step#2 - Capture Process Monitor Trace 1. Download and run Process Monitor. Leave this running while you perform the next steps. 2. Try installing the update 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. 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 attach the LogFile.PML file as well as your CBS.log
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 8, 2019 #7 I'm getting an error that the download limit has been reached when trying to access the logs.
A AimarPL Contributor Joined Nov 15, 2018 Posts 97 Feb 9, 2019 #8 My fault, sorry; Here's fixed link: ShareFile
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 11, 2019 #9 Thanks. Will have a look soon. We've upgraded our site and been working on that thus far. Apologies for the delay.
Thanks. Will have a look soon. We've upgraded our site and been working on that thus far. Apologies for the delay.
A AimarPL Contributor Joined Nov 15, 2018 Posts 97 Feb 15, 2019 #10 Hi! do you maybe have any update?
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 15, 2019 #11 Hi! I'm baffled by the ProcMon log, because if it really was run during the update attempt when you go the error, ProcMon did not seem to record that for some reason.
Hi! I'm baffled by the ProcMon log, because if it really was run during the update attempt when you go the error, ProcMon did not seem to record that for some reason.
A AimarPL Contributor Joined Nov 15, 2018 Posts 97 Feb 16, 2019 #12 just repeated this procedure, got new procmon capture for you :) ShareFile Additionally in attached image you can see which updates failed to install. Thank you in advance! Attachments 2019-02-16 21_46_25.png 50.9 KB · Views: 3
just repeated this procedure, got new procmon capture for you :) ShareFile Additionally in attached image you can see which updates failed to install. Thank you in advance!
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 16, 2019 #13 Thank you for the screenshot. It says pending restart. Does the update fail on restarting/configuring and not the actual installation?
Thank you for the screenshot. It says pending restart. Does the update fail on restarting/configuring and not the actual installation?
A AimarPL Contributor Joined Nov 15, 2018 Posts 97 Feb 16, 2019 #14 Yes, it will rollback, unconfigure, half an hour later it will be up again (and update state will be displayed as failed as with the ones with old date in same screenshot) Although, windows cumulative update is already marked as failed while two others need an reboot
Yes, it will rollback, unconfigure, half an hour later it will be up again (and update state will be displayed as failed as with the ones with old date in same screenshot) Although, windows cumulative update is already marked as failed while two others need an reboot
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 16, 2019 #15 Okay, I need to see CBS.log and C:\Windows\Inf\setupapi.dev.log. The reverting explains the lack of data in ProcMon.log.
Okay, I need to see CBS.log and C:\Windows\Inf\setupapi.dev.log. The reverting explains the lack of data in ProcMon.log.
A AimarPL Contributor Joined Nov 15, 2018 Posts 97 Feb 17, 2019 #16 I see; Files are uploaded here: ShareFile
A AimarPL Contributor Joined Nov 15, 2018 Posts 97 Feb 19, 2019 #17 did you manage to find anything in this file?
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 20, 2019 #19 Hmmm... Let's see if this gets us somewhere: 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. Right-click on the Start button and select Command Prompt (Admin) 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 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" 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.
Hmmm... Let's see if this gets us somewhere: 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. Right-click on the Start button and select Command Prompt (Admin) 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 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" 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.
A AimarPL Contributor Joined Nov 15, 2018 Posts 97 Feb 23, 2019 #20 Hello, I have followed steps mentioned, got same WU error at the end. Below you can find screenshots + CBS log attached. CBS Log: ShareFile
Hello, I have followed steps mentioned, got same WU error at the end. Below you can find screenshots + CBS log attached. CBS Log: ShareFile