[SOLVED] Error 8007370A

B

bluezeus

Well-known member
Joined
Jul 18, 2018
Posts
68
Hi on a Server 2012 standard, configured as not DC, I have four updates that I can not install.
I have already tried to restore Windows update, but without success.
I ultimately run DISM with the following result:Deployment Image Servicing and Management tool
Version: 6.2.9200.16384
Image Version: 6.2.9200.16384
[==========================100.0%==========================]
Error: 14090
The value of an attribute in an identity is not within the legal
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
In the CBS log this is the error:
2018-02-08 13:28:41, Error CBS Failed to call external evaluate applicability on package: Package_for_KB3072306~31bf3856ad364e35~amd64~~6.2.1.2, Update: 3072306-47_neutral_PACKAGE [HRESULT = 0x8007370a - ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_VALUE]
These are the updates that have problems: KB4055265, KB4033345, KB3048071, KB4057271
I think the problem is the package Package_for_KB3072306 ~ 31bf3856ad364e35 ~ AMD64 ~ ~ 6.2.1.2 which I also tried to uninstall but also here without succeeding.
The error I get in WU is 8007370A, I have already tried to rename the SoftwareDistribution folder, but I have not solved the problem, as well as disabling the updates and then reactivating them.
In the Event Viewer I have these messages:

  • Package KB3048071 failed to be changed to the installed state. Status: 0x8007370a.
  • System store corruption detection and repair has completed. Status: 0x0, total instances of corruption found: 0, total instances of corruption repaired: 0.
  • Installation Failure: Windows failed to install the following update with error 0x8007370A: 2018-01 Security and Quality Rollup for .net Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1 on Windows Server 2012 for x64 (KB4055265).
  • Installation Failure: Windows failed to install the following update with error 0x8007370A: Security update for Microsoft .net Framework 3.5 on Windows 8 and Windows Server 2012 for x64-based Systems (KB3048071).
​
 
Hello there,
Please run DISM again, then zip and attach C:\Windows\Logs\CBS\CBS.log
 
Hi,
Sorry for the delay in the answer, but I did not get the alert. As required I am attaching the file.
 

Attachments

Hello, as zcomputerwiz is away, I'll be assisting you with your issue.

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 and just provide the link here.
 
Thank you!

Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
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. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
6. Try updates and if any fail, attach CBS.log.
 

Attachments

Before I proceed with more fixes, please do the following:

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.
 
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:
    tags around the log to break up the text.
 

Attachments

This is the result:

Code: 
SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-10-02 09:40:47.385
Microsoft Windows Server 2012  - amd64
Using .zip script file at D:\Profilo\Administrator\Desktop\SFCFix.zip [0]


PowerCopy::
Successfully took permissions for file or folder C:\Windows\Servicing\Packages\package_831_for_kb4338830~31bf3856ad364e35~amd64~~6.2.1.6.cat
Successfully took permissions for file or folder C:\Windows\Servicing\Packages\package_831_for_kb4338830~31bf3856ad364e35~amd64~~6.2.1.6.mum
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\Packages\package_831_for_kb4338830~31bf3856ad364e35~amd64~~6.2.1.6.cat to C:\Windows\Servicing\Packages\package_831_for_kb4338830~31bf3856ad364e35~amd64~~6.2.1.6.cat.
Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\Packages\package_831_for_kb4338830~31bf3856ad364e35~amd64~~6.2.1.6.mum to C:\Windows\Servicing\Packages\package_831_for_kb4338830~31bf3856ad364e35~amd64~~6.2.1.6.mum.
Successfully restored ownership for C:\Windows\Servicing\Packages\package_831_for_kb4338830~31bf3856ad364e35~amd64~~6.2.1.6.cat
Successfully restored permissions on C:\Windows\Servicing\Packages\package_831_for_kb4338830~31bf3856ad364e35~amd64~~6.2.1.6.cat
Successfully restored ownership for C:\Windows\Servicing\Packages\package_831_for_kb4338830~31bf3856ad364e35~amd64~~6.2.1.6.mum
Successfully restored permissions on C:\Windows\Servicing\Packages\package_831_for_kb4338830~31bf3856ad364e35~amd64~~6.2.1.6.mum
PowerCopy:: directive completed successfully.


RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_1133_for_KB4103725~31bf3856ad364e35~amd64~~6.3.1.4.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_1133_for_KB4103725~31bf3856ad364e35~amd64~~6.3.1.4.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_1133_for_KB4103725~31bf3856ad364e35~amd64~~6.3.1.4\Owners.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_1133_for_KB4103725~31bf3856ad364e35~amd64~~6.3.1.4.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_1133_for_KB4103725~31bf3856ad364e35~amd64~~6.3.1.4\Owners.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_1133_for_KB4103725~31bf3856ad364e35~amd64~~6.3.1.4.
RegistryScript:: directive completed successfully.


Successfully processed all directives.

Failed to generate a complete zip file. Upload aborted.

SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 5 datablocks.
Finish time: 2018-10-02 11:00:40.853
Script hash: JA5xiXuGF6m6KFaKYgiEkri13JMNfYBPwzSDshFOdDk=
----------------------EOF-----------------------
 
Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
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. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
6. Try updates and if any fail, attach CBS.log.
 

Attachments

Thank you.
Also the last update was installed without problem.
It seems that everything has been solved.
 
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