WINDOWS UPDATE ERROR CODE 8007371B SERVER 2012

A

arish

Member
Joined
Jun 12, 2018
Posts
22
Hi Guys

I'm new to this forum and need some assistance with a VM that is just failing to run windows updates anymore.

I'm not sure what triggered this to happen but it did previously used to run updates.

I have followed the windows update forum posting instructions and have now arrived at step#6 to create topic.

I will be really grateful if an admin can assist me with this.

Please find CBS LOG FILES here

Much appreciated.
 
Hello and welcome!

Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Attempt to install updates just like you have in the past.
3. Stop Process Monitor as soon as Windows Update fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


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.
 
Hi Softwaremaniac

Thank you for your response.

Apologies, I was a little under the weather and away from work the last couple of days.

I will provide a response during the course of today.


softwaremaniac said:
Hello and welcome!

Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Attempt to install updates just like you have in the past.
3. Stop Process Monitor as soon as Windows Update fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


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.
Click to expand...
 
Hi Softwaremaniac

Please see log files and CBS files here

arish said:
Hi Softwaremaniac

Thank you for your response.

Apologies, I was a little under the weather and away from work the last couple of days.

I will provide a response during the course of today.


softwaremaniac said:
Hello and welcome!

Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Attempt to install updates just like you have in the past.
3. Stop Process Monitor as soon as Windows Update fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


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.
Click to expand...
Click to expand...
 
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 toa file sharing service and just provide the link here.

I will be traveling soon, so a colleague will likely take over.
 
Thanks for the update.

Please see components file zip here

softwaremaniac said:
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 toa file sharing service and just provide the link here.

I will be traveling soon, so a colleague will likely take over.
Click to expand...
 
Step#1 - Export SideBySide



  1. Click on the Start button and in the search box, type regedit
  2. When you see regedit on the list, right-click on it and select Run as administrator
  3. 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
  4. Once selected, click File > Export....
  5. Change the Save as type: to Registry Hive Files (*.*)
  6. Name this file SxS (with no file extension) and save it to your Desktop.
  7. Provide a copy in your next reply.
 
Ok. I think I might know what the issue is. The VM in question was actually used to clone two other VM's via HyperV import VM method. And I just realised that I didn't change the SID's on the two cloned VM's because this was a last minute onsite request to have these VM's spun up and I completely forgot about changing the SID's. Now, I am aware of sysprep and its ability to assist in this regard, however, both of these VM's have been loaded with software and are on the domain. The software and config of it is done by a 3rd party, and I am hoping to avoid having it removed via the sysprep method because the reinstallation of it will probably involve a cost with the 3rd party service provider.

Is there another way to change the SID on these two servers without having to reload the software on both?
 
I don't think SIDs would behave in this way. I have had a couple of SID issues here and these errors usually manifest in such a way that an update is reverted at a certain percentage + SID is logged in the CBS.log.
 
I hear you, but I just had a look at the other two cloned servers and their windows updates are not running either.

I do know that WSUS has an issue with two machines on the network with the same SID. Is it possible that this could be affecting the normal windows updates as well?

FYI, there is no WSUS in the environment that these VM's are on.
 
My thoughts exactly. So coming back to my earlier question, is there a method to change the SID's without having to remove user profiles and programs?

I have done some research, and I believe there was a tool called NewSID, but it is discontinued right now. I'm sure if looked hard enough, it would be able to be found somewhere on the internet. I don't know the effectiveness of the tool at all though, do you have any experience with it?
 
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