If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Failure to update KB976749
I've never seen anything like this before. I get notified of the new XP
update for IE 8, the download starts, then nothing happens. When I check update history, I can see that it failed with error code 0x80246002. This now happened 3 times. What else can I do here? |
Ads |
#2
|
|||
|
|||
Failure to update KB976749
0x80246002 WU_E_DM_INCORRECTFILEHASH
A download manager operation could not be completed because the file digest was not recognized. Is KB974455 listed in Add/Remove Programs in the Control Panel ? KB976749 was released to address issues caused by the installation of KB974455. Since KB976749 was offered to the system, then apparently the detection logic of the Windows Update Agent is seeing KB974455 as IsInstalled. See what happens when you try to install it manually: Update for Internet Explorer 8 for Windows XP (KB976749) http://www.microsoft.com/downloads/d...displaylang=en Download and save it, do NOT run it. Close the browser and any other open programs. Install IE8-WindowsXP-KB976749-x86-ENU.exe. You should get a restart prompt if it installs successfully. If KB976749 still doesn't install, please post the KB976749.log located in WINDOWS. MowGreen =============== *-343-* FDNY Never Forgotten =============== banthecheck.com "Security updates should *never* have *non-security content* prechecked" JP wrote: I've never seen anything like this before. I get notified of the new XP update for IE 8, the download starts, then nothing happens. When I check update history, I can see that it failed with error code 0x80246002. This now happened 3 times. What else can I do here? |
#3
|
|||
|
|||
Failure to update KB976749
NB: KB976749 is NOT a critical security update but a hotfix to resolve
certain specific issues that can occur after you apply security update 974455 (MS09-054)! If you're not plague by the issues described in http://support.microsoft.com/kb/976749, you don't need to install it (IMHO). -- ~Robear Dyer (PA Bear) MS MVP-IE, Mail, Security, Windows Client - since 2002 www.banthecheck.com JP wrote: I've never seen anything like this before. I get notified of the new XP update for IE 8, the download starts, then nothing happens. When I check update history, I can see that it failed with error code 0x80246002. This now happened 3 times. What else can I do here? |
#4
|
|||
|
|||
Failure to update KB976749
"MowGreen" wrote in message
... 0x80246002 WU_E_DM_INCORRECTFILEHASH A download manager operation could not be completed because the file digest was not recognized. Is KB974455 listed in Add/Remove Programs in the Control Panel ? Yes, it was installed on oct.14. KB976749 was released to address issues caused by the installation of KB974455. Since KB976749 was offered to the system, then apparently the detection logic of the Windows Update Agent is seeing KB974455 as IsInstalled. See what happens when you try to install it manually: Update for Internet Explorer 8 for Windows XP (KB976749) http://www.microsoft.com/downloads/d...displaylang=en Download and save it, do NOT run it. Close the browser and any other open programs. Install IE8-WindowsXP-KB976749-x86-ENU.exe. You should get a restart prompt if it installs successfully. If KB976749 still doesn't install, please post the KB976749.log located in WINDOWS. Thanks for the tip. I did the manual install as you suggested and it seemed to finish OK, I even see it listed on the Add/Remove Programs list. However, when I look at the Update history with the web browser, I still only see the record of the 3 failed installs, not the last, apparently successful one. I also see the following 8 identical error lines in the WINDOWS\KB976749-IE8.log file in two instances, though with different number prefixes after the line: 13.800: FindFirstFile v:\windows\$hf_mig$\*.* 15.282: KB976749 Setup encountered an error: The update.ver file is not correct. 15.402: KB976749 Setup encountered an error: The update.ver file is not correct. 15.553: KB976749 Setup encountered an error: The update.ver file is not correct. 15.563: KB976749 Setup encountered an error: The update.ver file is not correct. 16.154: KB976749 Setup encountered an error: The update.ver file is not correct. 17.115: KB976749 Setup encountered an error: The update.ver file is not correct. 17.315: KB976749 Setup encountered an error: The update.ver file is not correct. 17.986: KB976749 Setup encountered an error: The update.ver file is not correct. So I am not 100% sure if the update is really OK even though I don't see that same update listed again as a critical one any more. |
#5
|
|||
|
|||
Failure to update KB976749
The KB976749 update deleted the partition table on my HDD. I chose
"Install Update and shutdown option" and after I started the system again the BIOS doesn't detecting none HDD (I've two of 500 GB in my PC). Anyone MS admin help me what I do! |
#6
|
|||
|
|||
Failure to update KB976749
On Nov 5, 11:26*am, TheBoy wrote:
The KB976749 update deleted the partition table on my HDD. I chose "Install Update and shutdown option" and after I started the system again the BIOS doesn't detecting none HDD (I've two of 500 GB in my PC). Anyone MS admin help me what I do! BTW I using Win XP SP3. |
#7
|
|||
|
|||
Failure to update KB976749
32 bit edition, IE8
|
#8
|
|||
|
|||
Failure to update KB976749
However, when I look at the Update history with the web browser, I still only see the record of the
3 failed installs, not the last, apparently successful one. Updates applied *manually* do not show on the Update's website history. The errors posted from the KB976749.log are not errors, there typical entries for the KB installation logs. As to why, who knows ? w To confirm the update has installed, you can check the file version of Mshtml.dll, as shown on the KB article: http://support.microsoft.com/kb/976749 Mshtml.dll is located in WINDOWS\system32 Right click it, choose Properties, click the Version tab. Under Item name:, click on File Version. The Version number will depend upon which branch of the file that installed (QFE or GDR). My XP SP3 system with IE 6SP1 installed shows: 6.00.2900.5890 (xpsp_sp3_gdr.091019-1504) Which means the branch was GDR. Compare and contrast the V of Mshtml.dll with the one on your system and the one on the KB. MowGreen =============== *-343-* FDNY Never Forgotten =============== banthecheck.com "Security updates should *never* have *non-security content* prechecked" JP wrote: "MowGreen" wrote in message ... 0x80246002 WU_E_DM_INCORRECTFILEHASH A download manager operation could not be completed because the file digest was not recognized. Is KB974455 listed in Add/Remove Programs in the Control Panel ? Yes, it was installed on oct.14. KB976749 was released to address issues caused by the installation of KB974455. Since KB976749 was offered to the system, then apparently the detection logic of the Windows Update Agent is seeing KB974455 as IsInstalled. See what happens when you try to install it manually: Update for Internet Explorer 8 for Windows XP (KB976749) http://www.microsoft.com/downloads/d...displaylang=en Download and save it, do NOT run it. Close the browser and any other open programs. Install IE8-WindowsXP-KB976749-x86-ENU.exe. You should get a restart prompt if it installs successfully. If KB976749 still doesn't install, please post the KB976749.log located in WINDOWS. Thanks for the tip. I did the manual install as you suggested and it seemed to finish OK, I even see it listed on the Add/Remove Programs list. However, when I look at the Update history with the web browser, I still only see the record of the 3 failed installs, not the last, apparently successful one. I also see the following 8 identical error lines in the WINDOWS\KB976749-IE8.log file in two instances, though with different number prefixes after the line: 13.800: FindFirstFile v:\windows\$hf_mig$\*.* 15.282: KB976749 Setup encountered an error: The update.ver file is not correct. 15.402: KB976749 Setup encountered an error: The update.ver file is not correct. 15.553: KB976749 Setup encountered an error: The update.ver file is not correct. 15.563: KB976749 Setup encountered an error: The update.ver file is not correct. 16.154: KB976749 Setup encountered an error: The update.ver file is not correct. 17.115: KB976749 Setup encountered an error: The update.ver file is not correct. 17.315: KB976749 Setup encountered an error: The update.ver file is not correct. 17.986: KB976749 Setup encountered an error: The update.ver file is not correct. So I am not 100% sure if the update is really OK even though I don't see that same update listed again as a critical one any more. |
#9
|
|||
|
|||
Failure to update KB976749
"MowGreen" wrote:
Updates applied *manually* do not show on the Update's website history. The errors posted from the KB976749.log are not errors, there typical entries for the KB installation logs. As to why, who knows ? w Thanks, that's reassuring. To confirm the update has installed, you can check the file version of Mshtml.dll, as shown on the KB article: http://support.microsoft.com/kb/976749 Mshtml.dll is located in WINDOWS\system32 Right click it, choose Properties, click the Version tab. Under Item name:, click on File Version. The Version number will depend upon which branch of the file that installed (QFE or GDR). My XP SP3 system with IE 6SP1 installed shows: 6.00.2900.5890 (xpsp_sp3_gdr.091019-1504) Which means the branch was GDR. Compare and contrast the V of Mshtml.dll with the one on your system and the one on the KB. OK, the version on my system is 8.00.6001.18852 which is identical to the one listed on your web link with service branch SP3GDR. What are those two svc branches for, anyway? (The other being SP3QFE) I also wonder about all those $NtUninstallKBxxxxxx$ subdirs in the WINDOWS directory. They just keep accummulating and wasting disk space. I guess they are needed to uninstall the formerly installed KBs, but after a while one is pretty sure about not needing those uninstalls, so can one just delete those older subdirs to free up disk space? Same goes for corresponding log files, of course. |
#10
|
|||
|
|||
Failure to update KB976749
OK, the version on my system is 8.00.6001.18852 which is identical to the one listed on your web link with service branch SP3GDR.
What are those two svc branches for, anyway? (The other being SP3QFE) Since you asked: http://support.microsoft.com/kb/824994 " When you install a security update, critical update, update, update rollup, driver, or feature pack, the package installer (Update.exe) checks to see if your existing files are from the original release version (RTM), SPx, or the GDR environment or hotfix environment. If all the files that are being updated on your computer are from the original release version, SPx, or GDR environment (you have not previously installed a hotfix to update one of the files since the last cardinal point was established) then Update.exe installs the files from the appropriate GDR folder to your computer. If any of the files that are being updated on your computer are from the hotfix environment (you have previously installed a hotfix to update one of the files since the last cardinal point was established), Update.exe installs the files from the appropriate QFE folder to your computer. " I also wonder about all those $NtUninstallKBxxxxxx$ subdirs in the WINDOWS directory. They just keep accummulating and wasting disk space. I guess they are needed to uninstall the formerly installed KBs, but after a while one is pretty sure about not needing those uninstalls, so can one just delete those older subdirs to free up disk space? Same goes for corresponding log files, of course. The $NtUninstallKBxxxxxx$ subfolders can be safely deleted once you determine that there are absolutely no issues being caused by installed updates. The amount of disk space used by the KBxxxxxx.logs are trivial compared to the $NtUninstallKBxxxxxx$ subfolders but, if there are no installation issues, they can be safely deleted, too. Before deleting the $NtUninstallKBxxxxxx$ subfolders, see: I want to Save Space and delete unnecessary files after installing a Windows Update patch or Service Pack. http://www3.telus.net/dandemar/wufix.htm MowGreen =============== *-343-* FDNY Never Forgotten =============== banthecheck.com "Security updates should *never* have *non-security content* prechecked" JP wrote: "MowGreen" wrote: Updates applied *manually* do not show on the Update's website history. The errors posted from the KB976749.log are not errors, there typical entries for the KB installation logs. As to why, who knows ? w Thanks, that's reassuring. To confirm the update has installed, you can check the file version of Mshtml.dll, as shown on the KB article: http://support.microsoft.com/kb/976749 Mshtml.dll is located in WINDOWS\system32 Right click it, choose Properties, click the Version tab. Under Item name:, click on File Version. The Version number will depend upon which branch of the file that installed (QFE or GDR). My XP SP3 system with IE 6SP1 installed shows: 6.00.2900.5890 (xpsp_sp3_gdr.091019-1504) Which means the branch was GDR. Compare and contrast the V of Mshtml.dll with the one on your system and the one on the KB. OK, the version on my system is 8.00.6001.18852 which is identical to the one listed on your web link with service branch SP3GDR. What are those two svc branches for, anyway? (The other being SP3QFE) I also wonder about all those $NtUninstallKBxxxxxx$ subdirs in the WINDOWS directory. They just keep accummulating and wasting disk space. I guess they are needed to uninstall the formerly installed KBs, but after a while one is pretty sure about not needing those uninstalls, so can one just delete those older subdirs to free up disk space? Same goes for corresponding log files, of course. |
#11
|
|||
|
|||
Failure to update KB976749
"MowGreen" wrote:
Since you asked: http://support.microsoft.com/kb/824994 " When you install a security update, critical update, update, update rollup, driver, or feature pack, the package installer (Update.exe) checks to see if your existing files are from the original release version (RTM), SPx, or the GDR environment or hotfix environment. If all the files that are being updated on your computer are from the original release version, SPx, or GDR environment (you have not previously installed a hotfix to update one of the files since the last cardinal point was established) then Update.exe installs the files from the appropriate GDR folder to your computer. If any of the files that are being updated on your computer are from the hotfix environment (you have previously installed a hotfix to update one of the files since the last cardinal point was established), Update.exe installs the files from the appropriate QFE folder to your computer. " Aha! Thanks. The $NtUninstallKBxxxxxx$ subfolders can be safely deleted once you determine that there are absolutely no issues being caused by installed updates. The amount of disk space used by the KBxxxxxx.logs are trivial compared to the $NtUninstallKBxxxxxx$ subfolders but, if there are no installation issues, they can be safely deleted, too. Before deleting the $NtUninstallKBxxxxxx$ subfolders, see: I want to Save Space and delete unnecessary files after installing a Windows Update patch or Service Pack. http://www3.telus.net/dandemar/wufix.htm Thanks again. I guess my XP is fine now. |
Thread Tools | |
Display Modes | |
|
|