[SOLVED] Windows Update KB3000850 Code Error 8007370A

B

bigtoeknee

Member
Joined
Jun 15, 2015
Posts
10
Ok, read a few things on the forum and have tried numerous things to try and fix this issue, but most seem to be specific to that users problem. Here is some of the same information that they have provided.

SFCFix give this error:
Code: 
Welcome to SFCFix by niemiro and sysnative.com.

Checking for updates . . .
No new update is available at this time.


Processing directive 1 of 1 (AutoAnalysis::)
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.3.9600.17031


Image Version: 6.3.9600.17031


[==========================100.0%==========================]


Error: 14090


The value of an attribute in an identity is not within the legal range.


The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

And I provided a copy of my DISM log and CBS log. Please let me know if you need any further information.
 
Hi and welcome to Sysnative. Sorry for the delay. It appears that you have registry corruption. I need a copy of your Components hive to try and resolve. Please do the following.

Code: 
2015-06-15 18:49:41, Error                 CSI    00000890 (F) Unable to parse identity version: [l:28{14}]"6.3.900.17238"
[gle=0x80004005]
2015-06-15 18:49:41, Error                 CSI    00000891@2015/6/15:22:49:41.200 (F) base\wcp\identity\id_authority_helpers.cpp(1526): Error STATUS_SXS_INVALID_IDENTITY_ATTRIBUTE_VALUE originated in function Windows::Identity::Rtl::Implementation::id_AddBuiltinToBuiltinAttributes expression: fParsedOK
[gle=0x80004005]

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 SendSpace and just provide the link here.
 
BrianDrab said:
Hi and welcome to Sysnative. Sorry for the delay. It appears that you have registry corruption. I need a copy of your Components hive to try and resolve. Please do the following.

Code: 
2015-06-15 18:49:41, Error                 CSI    00000890 (F) Unable to parse identity version: [l:28{14}]"6.3.900.17238"
[gle=0x80004005]
2015-06-15 18:49:41, Error                 CSI    00000891@2015/6/15:22:49:41.200 (F) base\wcp\identity\id_authority_helpers.cpp(1526): Error STATUS_SXS_INVALID_IDENTITY_ATTRIBUTE_VALUE originated in function Windows::Identity::Rtl::Implementation::id_AddBuiltinToBuiltinAttributes expression: fParsedOK
[gle=0x80004005]

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 SendSpace and just provide the link here.
Click to expand...

Thanks for the response.

Here is the COMPONETS file.
 
Thank you. I believe I found the corruption for these errors in the log.

Code: 
2015-06-15 18:50:09, Error                 CSI    000008a4 (F) STATUS_SXS_INVALID_IDENTITY_ATTRIBUTE_VALUE #10095420# from Windows::Identity::Rtl::Implementation::CRtlIdentityAuthority::IRtlIdentityAuthority_Parse(flags = 0, string = [l:312{156}]"[COLOR=#ff0000][B]1dfa55b5fe904978c2602a6e7a83767a[/B][/COLOR], Culture=neutral, Version=[COLOR=#ff0000][B]6.3.900.17238[/B][/COLOR], PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS")
[gle=0xd0150016]
2015-06-15 18:50:09, Error                 CSI    000008a5 (F) HRESULT_FROM_WIN32(14090) #10095399# from Windows::ServicingAPI::CCSITransactionAnalysis_ICSIInventory::EnumComponentsDeployments(flags = (ICSIINVENTORY_ENUMCOMPONENTSDEPLOYMENTS_FLAG_INCLUDE_PINNED|ICSIINVENTORY_ENUMCOMPONENTSDEPLOYMENTS_FLAG_INCLUDE_INSTALLED|ICSIINVENTORY_ENUMCOMPONENTSDEPLOYMENTS_FLAG_ASSEMBLY_NOT_FOUND_RETURNS_NULL), cComponents = 1)
[gle=0x8007370a]

The data in the appid value of the following key appears to have been corrupted. In the screen shot below I have highlighted the issue. This should be Version=6.3.9600 and not Version=6.3.9.00
HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1dfa55b5fe9..a6e7a83767a_31bf3856ad364e35_6.3.9600.17238_5d6f20065284ad8e
Capture.JPG

The following should fix that.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt 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

Step#2 - SFC Scan
1. Right-click on the Start
w8start.png
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
 sfc /scannow

3. Once it finishes, copy and paste the following into the command-prompt window and press Enter.
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 upload CBS.txt to this thread

Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
Items for your next post
1. SFCFix.txt
2. CBS.txt
 

Attachments

BrianDrab said:
Thank you. I believe I found the corruption for these errors in the log.

Code: 
2015-06-15 18:50:09, Error                 CSI    000008a4 (F) STATUS_SXS_INVALID_IDENTITY_ATTRIBUTE_VALUE #10095420# from Windows::Identity::Rtl::Implementation::CRtlIdentityAuthority::IRtlIdentityAuthority_Parse(flags = 0, string = [l:312{156}]"[COLOR=#ff0000][B]1dfa55b5fe904978c2602a6e7a83767a[/B][/COLOR], Culture=neutral, Version=[COLOR=#ff0000][B]6.3.900.17238[/B][/COLOR], PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS")
[gle=0xd0150016]
2015-06-15 18:50:09, Error                 CSI    000008a5 (F) HRESULT_FROM_WIN32(14090) #10095399# from Windows::ServicingAPI::CCSITransactionAnalysis_ICSIInventory::EnumComponentsDeployments(flags = (ICSIINVENTORY_ENUMCOMPONENTSDEPLOYMENTS_FLAG_INCLUDE_PINNED|ICSIINVENTORY_ENUMCOMPONENTSDEPLOYMENTS_FLAG_INCLUDE_INSTALLED|ICSIINVENTORY_ENUMCOMPONENTSDEPLOYMENTS_FLAG_ASSEMBLY_NOT_FOUND_RETURNS_NULL), cComponents = 1)
[gle=0x8007370a]

The data in the appid value of the following key appears to have been corrupted. In the screen shot below I have highlighted the issue. This should be Version=6.3.9600 and not Version=6.3.9.00
HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1dfa55b5fe9..a6e7a83767a_31bf3856ad364e35_6.3.9600.17238_5d6f20065284ad8e
View attachment 13437

The following should fix that.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt 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

Step#2 - SFC Scan
1. Right-click on the Start
w8start.png
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
 sfc /scannow

3. Once it finishes, copy and paste the following into the command-prompt window and press Enter.
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 upload CBS.txt to this thread

Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
Items for your next post
1. SFCFix.txt
2. CBS.txt
Click to expand...
SFCFix Data
Code: 
SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-06-20 21:46:37.471
Microsoft Windows 8.1 Update 3 - amd64
Using .txt script file at C:\Users\Tony\Desktop\SFCScript.txt [1]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1dfa55b5fe9..a6e7a83767a_31bf3856ad364e35_6.3.9600.17238_5d6f20065284ad8e.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1dfa55b5fe9..a6e7a83767a_31bf3856ad364e35_6.3.9600.17238_5d6f20065284ad8e.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1dfa55b5fe9..a6e7a83767a_31bf3856ad364e35_6.3.9600.17238_5d6f20065284ad8e.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2015-06-20 21:46:37.541
Script hash: 9+RcgWtdHiSfKyLi/XJBAPow9D/myBuZBlfCQtT/bz8=
----------------------EOF-----------------------
CBS Log
 
Perfect. Now 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
    w8start.png
    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.
 
BrianDrab said:
Perfect. Now 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
    w8start.png
    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...

DISM Error:
Code: 
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]

Error: 0x800f081f

The source files could not be found.
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
 http://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

C:\WINDOWS\system32>

CBS Log

By the way I appreciate all the help.
 
No problem at all.

Thank you for the info. Let's do the following.

Step#1 - Manually download/install the update.
Please manually download the update and try installing.
http://www.microsoft.com/en-us/download/details.aspx?id=44977

If this doesn't work then go on to Step#2.

Step#2 - Create Missing Folders
Are you comfortable with creating folders and copying files around? If not let me know and I'll automate this more for you.

Please create the following two folders in bold. Please copy/paste the name so it's exact.

C:\Windows\System32\DriverStore\FileRepository\wiaek002.inf_amd64_57f9361b96ceea4b
C:\Windows\System32\DriverStore\FileRepository\prnekcl2.inf_amd64_59438dc7ce792b20

Copy wiaek002.inf from C:\Windows\Inf and paste into the 1st folder you created above.
Copy prnekcl2.inf from C:\Windows\Inf and paste into the 2nd folder you created above.

Now try installing the update. Please use the one that was manually downloaded.
 
BrianDrab said:
No problem at all.

Thank you for the info. Let's do the following.

Step#1 - Manually download/install the update.
Please manually download the update and try installing.
http://www.microsoft.com/en-us/download/details.aspx?id=44977

If this doesn't work then go on to Step#2.

Step#2 - Create Missing Folders
Are you comfortable with creating folders and copying files around? If not let me know and I'll automate this more for you.

Please create the following two folders in bold. Please copy/paste the name so it's exact.

C:\Windows\System32\DriverStore\FileRepository\wiaek002.inf_amd64_57f9361b96ceea4b
C:\Windows\System32\DriverStore\FileRepository\prnekcl2.inf_amd64_59438dc7ce792b20

Copy wiaek002.inf from C:\Windows\Inf and paste into the 1st folder you created above.
Copy prnekcl2.inf from C:\Windows\Inf and paste into the 2nd folder you created above.

Now try installing the update. Please use the one that was manually downloaded.
Click to expand...
Ok ran the process in step 1. Installed fine and restarted my computer booted windows said now processing updates and then restarted again this time it said windows update failed uninstalling updates. Restarted in to windows after that fine but updated was not installed.

Step 2. Completed that process fine installed the standalone update like in step one. Prompted to restart my computer and started to install updated on restart as the first. On reboot computer booted into windows loading screen and it hangs on a bsod with no progress in the percentage. Stuck at 0%, restarted multiple times same bsod. Ntfs.sys


Booted back into windows normally after I let it sit for a few seconds with a hard shutdown.
 

Attachments

  • image.jpg
    image.jpg
    289 KB · Views: 4
That's what I suspected from the logs. Please do the following.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt 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
 

Attachments

BrianDrab said:
That's what I suspected from the logs. Please do the following.

Step#1 - 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. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt 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
Click to expand...

SFC Fix
Code: 
SFCFix version 2.4.5.0 by niemiro.
Start time: 2015-06-21 16:16:21.751
Microsoft Windows 8.1 Update 3 - amd64
Using .txt script file at C:\Users\Tony\Desktop\SFCScript.txt [0]




FileScan::
[0: 1] C:\WINDOWS\Inf\wiaek002.inf
File is untraceable.
 Found: NlV5hfp1wOUEBedp8LABFUDEHAIXSzFJCsq/QhBC+8o=
 Version number not available.
Trace not available.



[1: 1] C:\WINDOWS\WinSxS\amd64_prnekcl2.inf_31bf3856ad364e35_6.3.9600.17415_none_7f485080c7a1ea5e\prnekcl2.inf
File is untraceable.
 Found: kIhfK+DAWQLTtxFrFgUKwM1HPb13MBi8RQGYIpAGh/M=
 Version number not available.
Trace not available.



[2: 1] C:\WINDOWS\WinSxS\amd64_wiaek002.inf_31bf3856ad364e35_6.3.9600.17415_none_1837b39412cd1eca\wiaek002.inf
File is untraceable.
 Found: tGxLsE4Qqm35sHWtB+6xvnSJSSvumTSYFN2mQkR+ESk=
 Version number not available.
Trace not available.



[3: 1] C:\WINDOWS\WinSxS\amd64_prnekcl2.inf_31bf3856ad364e35_6.3.9600.16384_none_7efbb5a4c7db7dd6\prnekcl2.inf
File is untraceable.
 Found: SsQwhj24DUWgP6hss0iVNlYPeVRTXoRc4SdYZlprjZQ=
 Version number not available.
Trace not available.



[4: 1] C:\WINDOWS\Inf\prnekcl2.inf
File is untraceable.
 Found: SsQwhj24DUWgP6hss0iVNlYPeVRTXoRc4SdYZlprjZQ=
 Version number not available.
Trace not available.



[5: 1] C:\WINDOWS\WinSxS\amd64_wiaek002.inf_31bf3856ad364e35_6.3.9600.16384_none_17eb18b81306b242\wiaek002.inf
File is untraceable.
 Found: NlV5hfp1wOUEBedp8LABFUDEHAIXSzFJCsq/QhBC+8o=
 Version number not available.
Trace not available.



[6: 1] C:\WINDOWS\System32\DriverStore\FileRepository\wiaek002.inf_amd64_57f9361b96ceea4b\wiaek002.inf
File is untraceable.
 Found: NlV5hfp1wOUEBedp8LABFUDEHAIXSzFJCsq/QhBC+8o=
 Version number not available.
Trace not available.
FileScan:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2015-06-21 16:16:26.361
Script hash: htB2/Thqm8aDnfd9vEoxqfrvVcW5nPXQsJJ8ovqkrhI=
----------------------EOF-----------------------
 
It doesn't appear that you created the following folder:
C:\Windows\System32\DriverStore\FileRepository\prnekcl2.inf_amd64_59438dc7ce792b20

You need to ensure that you create this folder and copy prnekcl2.inf from C:\Windows\Inf into this folder before trying the update again.
 
Both folders and files are still there. Here is the screen capture of prnekcl2.inf_amd64_59438dc7ce792b20 prnekcl2file.PNGprnekcl2folder.jpg
 
Success!

Standalone installer didn't work tho. It went through the install process fine and restarted fine but didn't install the package when I went into control panel>windows update>View Installed updates it didn't show as installed. I actually used Windows Update to install and worked fine. Hung on bio boot for some reason but hard boot fixed that issue.

Thank you very much you have been a great help!
 
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