[SOLVED] Windows Update Error 800070490 From last 1 week for KB3003743 & KB2992611

BrianDrab said:
Thank you. Please do the following.

Step#1 - SFC Scan


  1. Click on the Start
    Start%20Orb.jpg
    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 zip and attach this to your next post.
Click to expand...
 

Attachments

Thank you. Can you check if the following update is installed on your machine and if it is, uninstall it?
KB3023562

To Check
1. Click the Start button and select Control Panel
2. Click on the Programs group.
3. Click on the View installed updates link
4. In the Search area at the top right, type in KB3023562
5. Uninstall if found

If you found it and uninstalled it go ahead and try installing KB2992611. Let me know the results. Thanks.
 
BrianDrab said:
Thank you. Can you check if the following update is installed on your machine and if it is, uninstall it?
KB3023562

To Check
1. Click the Start button and select Control Panel
2. Click on the Programs group.
3. Click on the View installed updates link
4. In the Search area at the top right, type in KB3023562
5. Uninstall if found

If you found it and uninstalled it go ahead and try installing KB2992611. Let me know the results. Thanks.
Click to expand...
 
OK, here's what we need to do. A little different this time.

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 KB2992611.
3. When it fails, Stop Process Monitor. 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.

Thank you.
 
BrianDrab said:
OK, here's what we need to do. A little different this time.

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 KB2992611.
3. When it fails, Stop Process Monitor. 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.

Thank you.
Click to expand...

View attachment 12010
 
Thanks for the information. I have myself all confused in the logs. Is the Date, Time & Time Zone correct on your machine? The minutes and seconds aren't matching up on your logs which has me confused. I understand the hour because of time zone differences but the minute and second have me confused.

Let me know about the Date, Time and TimeZone of your machine and also let me know what the exact time is where you are when you post. Thanks.
 
@BrianDrab

and i just got BSOD

IRQL_NOT_LESS_OR_EQUAL

i am not owner of this lappy

i asked some Question
he told he got malware infected by clicking some links and following on screen instruction
but computer was working after that he found that kaspersky licence expired he loaded trail version and removed some viruses and programs that he things was not there before get infected

i checked there tons of BSOD with all referring ntoskrnl.exe+process of kaspersky mostly all of them

attaching latest mini dump and whole folder.rar and 1 ss if you wish to help further

View attachment Minidump.rarkasper.jpg

Code: 
==================================================Dump File         : 050415-31247-01.dmp
Crash Time        : 04-05-2015 02:54:37 AM Devdatt
Bug Check String  : IRQL_NOT_LESS_OR_EQUAL
Bug Check Code    : 0x1000000a
Parameter 1       : 0xa6b26008
Parameter 2       : 0x00000002
Parameter 3       : 0x00000001
Parameter 4       : 0x820c27bd
Caused By Driver  : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+b07bd
File Description  : NT Kernel & System
Product Name      : Microsoft® Windows® Operating System
Company           : Microsoft Corporation
File Version      : 6.1.7601.18798 (win7sp1_gdr.150316-1654)
Processor         : 32-bit
Crash Address     : ntoskrnl.exe+b07bd
Stack Address 1   : ntoskrnl.exe+9f71c
Stack Address 2   : ntoskrnl.exe+9fdb2
Stack Address 3   : ntoskrnl.exe+9fa67
Computer Name     : 
Full Path         : C:\Windows\Minidump\050415-31247-01.dmp
Processors Count  : 4
Major Version     : 15
Minor Version     : 7601
Dump File Size    : 150,597
Dump File Time    : 04-05-2015 02:56:00 AM Devdatt
==================================================
 

Attachments

OK, what I suggest we do is the following. Let me check for malware and ensure the computer is clean, then we can continue here.

Please post a topic in our Security Forum. In the subject put "Windows Update - 13978 - For BrianDrab". In the body of the post please put a link to this topic and the following two logs. As soon as I see it I'll pick it up and assist.

Step#1 - FRST Logs
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 32-bit Version so please ensure you download that one.
2. Right click to run as administrator. When the tool opens click Yes to disclaimer.
3. Note: Ensure that the Addition.txt check box is checked at the bottom of the form within the Optional Scan area.
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 copy and paste log back here.
7. The first time the tool is run it generates another log (Addition.txt - also located in the same directory as FRST.exe). Please also paste that along with the FRST.txt into your reply.
 
Thanks for allowing me to get your machine cleaned up. Compounding problems are never good. Let's do the following again. Please also let me know what your local time is when you start process monitor and when you stop process monitor. It will help me greatly in the logs. Thanks.

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 KB2992611.
3. When it fails, Stop Process Monitor. 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.

Thank you.
 
Start 11:31:48
Stop 11:37:00
Saved 11:37:45
Method manual install

MSE making sys run so slow sry for late response
 

Attachments

ignore previous CBS as i copy pasted that CBS while it was in process

this new CBS is end of process output not sure which process
 

Attachments

Thanks for the information. 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


Then try installing the update KB2992611 again manually. If it fails, zip up and send the CBS.log only. Thanks.
 

Attachments

BrianDrab said:
Thanks for the information. 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


Then try installing the update KB2992611 again manually. If it fails, zip up and send the CBS.log only. Thanks.
Click to expand...

Thanks it worked

1. tried to manual install of KB2992611 it installed Successfully and it asked to restart
after restart

2. I try to update KB30003743 & KB2310138 (Optional) with update client both succeeded

THANK YOU SO MUCH :thumbsup2:
success.jpg

also attaching new CBS.log

I think everything is OK now right ?

Code: 
SFCFix version 2.4.3.0 by niemiro.
Start time: 2015-05-05 11:07:12.336
Microsoft Windows 7 Service Pack 1 - x86
Using .txt script file at C:\Users\Devdatt\Desktop\SFCScript.txt [0]


RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\01e895ace15..a7db3ebb628_31bf3856ad364e35_6.1.7601.22925_fabb68ff65c0a46b.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\01e895ace15..a7db3ebb628_31bf3856ad364e35_6.1.7601.22925_fabb68ff65c0a46b.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1ee69e91959..64c54047ddb_31bf3856ad364e35_6.1.7601.22925_e5f57aee8dfa09e9.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1ee69e91959..64c54047ddb_31bf3856ad364e35_6.1.7601.22925_e5f57aee8dfa09e9.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\3c7f23acf58..7778483a9f2_31bf3856ad364e35_6.1.7601.22925_2a91ef7a0031c0e2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\3c7f23acf58..7778483a9f2_31bf3856ad364e35_6.1.7601.22925_2a91ef7a0031c0e2.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\4c7eb4e26f4..467343971b3_31bf3856ad364e35_6.1.7601.22925_8066367b9b8bcf51.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\4c7eb4e26f4..467343971b3_31bf3856ad364e35_6.1.7601.22925_8066367b9b8bcf51.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\7079fa6efa9..f55b6898d68_31bf3856ad364e35_6.1.7601.18719_467bbf69c84764e9.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8d43dc4a5e1..186cb639bb0_31bf3856ad364e35_6.1.7601.18719_84a6c02417c3fba3.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\c86baea4ea1..8d784cf323b_31bf3856ad364e35_6.1.7601.22925_6449f08d5a806922.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\c86baea4ea1..8d784cf323b_31bf3856ad364e35_6.1.7601.22925_6449f08d5a806922.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\d5a1066d7fb..b40a32d1a1e_31bf3856ad364e35_6.1.7601.18606_c2f82c99800a6d30.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\e7839eb743d..558f7408a2b_31bf3856ad364e35_6.1.7601.18606_9b8631bf1ae4b9a1.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\01e895ace15..a7db3ebb628_31bf3856ad364e35_6.1.7601.22925_fabb68ff65c0a46b.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\01e895ace15..a7db3ebb628_31bf3856ad364e35_6.1.7601.22925_fabb68ff65c0a46b.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1ee69e91959..64c54047ddb_31bf3856ad364e35_6.1.7601.22925_e5f57aee8dfa09e9.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1ee69e91959..64c54047ddb_31bf3856ad364e35_6.1.7601.22925_e5f57aee8dfa09e9.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\3c7f23acf58..7778483a9f2_31bf3856ad364e35_6.1.7601.22925_2a91ef7a0031c0e2.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\3c7f23acf58..7778483a9f2_31bf3856ad364e35_6.1.7601.22925_2a91ef7a0031c0e2.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\4c7eb4e26f4..467343971b3_31bf3856ad364e35_6.1.7601.22925_8066367b9b8bcf51.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\4c7eb4e26f4..467343971b3_31bf3856ad364e35_6.1.7601.22925_8066367b9b8bcf51.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\7079fa6efa9..f55b6898d68_31bf3856ad364e35_6.1.7601.18719_467bbf69c84764e9.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8d43dc4a5e1..186cb639bb0_31bf3856ad364e35_6.1.7601.18719_84a6c02417c3fba3.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\c86baea4ea1..8d784cf323b_31bf3856ad364e35_6.1.7601.22925_6449f08d5a806922.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\c86baea4ea1..8d784cf323b_31bf3856ad364e35_6.1.7601.22925_6449f08d5a806922.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\d5a1066d7fb..b40a32d1a1e_31bf3856ad364e35_6.1.7601.18606_c2f82c99800a6d30.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\e7839eb743d..558f7408a2b_31bf3856ad364e35_6.1.7601.18606_9b8631bf1ae4b9a1.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\01e895ace15..a7db3ebb628_31bf3856ad364e35_6.1.7601.22925_fabb68ff65c0a46b.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\01e895ace15..a7db3ebb628_31bf3856ad364e35_6.1.7601.22925_fabb68ff65c0a46b.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1ee69e91959..64c54047ddb_31bf3856ad364e35_6.1.7601.22925_e5f57aee8dfa09e9.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\1ee69e91959..64c54047ddb_31bf3856ad364e35_6.1.7601.22925_e5f57aee8dfa09e9.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\3c7f23acf58..7778483a9f2_31bf3856ad364e35_6.1.7601.22925_2a91ef7a0031c0e2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\3c7f23acf58..7778483a9f2_31bf3856ad364e35_6.1.7601.22925_2a91ef7a0031c0e2.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\4c7eb4e26f4..467343971b3_31bf3856ad364e35_6.1.7601.22925_8066367b9b8bcf51.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\4c7eb4e26f4..467343971b3_31bf3856ad364e35_6.1.7601.22925_8066367b9b8bcf51.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\7079fa6efa9..f55b6898d68_31bf3856ad364e35_6.1.7601.18719_467bbf69c84764e9.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8d43dc4a5e1..186cb639bb0_31bf3856ad364e35_6.1.7601.18719_84a6c02417c3fba3.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\c86baea4ea1..8d784cf323b_31bf3856ad364e35_6.1.7601.22925_6449f08d5a806922.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\c86baea4ea1..8d784cf323b_31bf3856ad364e35_6.1.7601.22925_6449f08d5a806922.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\d5a1066d7fb..b40a32d1a1e_31bf3856ad364e35_6.1.7601.18606_c2f82c99800a6d30.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\e7839eb743d..558f7408a2b_31bf3856ad364e35_6.1.7601.18606_9b8631bf1ae4b9a1.
RegistryScript:: directive completed successfully.


Successfully processed all directives.
SFCFix version 2.4.3.0 by niemiro has completed.
Currently storing 9 datablocks.
Finish time: 2015-05-05 11:07:16.345
Script hash: pgZHIkEIysoyJbtLvFiY04eWV5Tyihyl7oVLcrVQIfI=
----------------------EOF-----------------------
 

Attachments

Great news. There is still an error in your log however if things are working now I'll leave it up to you whether you want to try and resolve this issue.
Code: 
2015-05-05 11:19:19, Error                 CBS    Failed to check whether package is partially installed, package: Windows7SP1-KB976933~31bf3856ad364e35~x86~~6.1.1.17514 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2015-05-05 11:19:19, Info                  CBS    Failed to evaluate external applicability for package update: 976933-0_neutral_PACKAGE [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2015-05-05 11:19:19, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB976932~31bf3856ad364e35~x86~~6.1.1.17514, Update: 976933-0_neutral_PACKAGE [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
 
BrianDrab said:
Great news. There is still an error in your log however if things are working now I'll leave it up to you whether you want to try and resolve this issue.
Code: 
2015-05-05 11:19:19, Error                 CBS    Failed to check whether package is partially installed, package: Windows7SP1-KB976933~31bf3856ad364e35~x86~~6.1.1.17514 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2015-05-05 11:19:19, Info                  CBS    Failed to evaluate external applicability for package update: 976933-0_neutral_PACKAGE [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2015-05-05 11:19:19, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB976932~31bf3856ad364e35~x86~~6.1.1.17514, Update: 976933-0_neutral_PACKAGE [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
Click to expand...

as you found it I will love to try your fix for this

for testing windows update stability I tried to uninstall and reinstall those two updates and I succeeded
 
I'm reviewing your log now. Please reboot and then let me know if you still get the same error as shown above. I'll be back shortly.
 
After you have rebooted and verified if the above error happens, please do the following.

Step#1 - FRST Registry Search
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 32-bit Version so please ensure you download that one.
2. Right click to run as administrator. When the tool opens click Yes to disclaimer.
3. Copy and paste the following Windows7SP1-KB976933~31bf3856ad364e35~x86~~6.1.1.17514 into the Search box and click the Search Registry button.
Search.JPG


4. When the scan is complete a notepad window will open with the results. Please copy and paste the contents in your next reply. If for some reason notepad doesn't open the file should be
saved on your desktop named Search.txt.

Step#2 - FRST Dump Key Contents
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. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
2. Run FRST by Right-Clicking on the file and choosing Run as administrator.
3. 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.
4. When finished FRST will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
Items for your next post
1. Did reboot help with that error you were getting?
2. Registry Search log contents
3. Fixlog contents
 

Attachments

I checked it in 4 restarts

it sometimes able to find updates I just updated 3 updates

BUT most of times it shows error
 

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