Mim0

The File-Checker (HFSLIPFC) for HFSLIP

1,617 posts in this topic

URGENT: IE8 Cumm update KB2744842, automatic updates is asking for it. It seems M$ released this silently...

New version reqd., mimo.

0

Share this post


Link to post
Share on other sites

URGENT: IE8 Cumm update KB2744842, automatic updates is asking for it. It seems M$ released this silently...

Microsoft does release some security updates that are not in Patch Tuesday. But only if the update is urgent as you said.

2744842 | MS12-063 | IE security | download (IE6):34735 download (IE8):34731 | replaces (MS12-052) KB2722913

Edited by Explorer09
0

Share this post


Link to post
Share on other sites

Yep, we need a new version, to address the bugs I found and to support the latest IE cumm. update.

mimo? :rolleyes:

0

Share this post


Link to post
Share on other sites

Hi, there! :)

There's an error on your homepage, Mim0. Windows XP > Changelog section tells me correctly about removed update package, KB2695962.

Windows XP > Update section, however, show me that KB2736233 replaces KB2618451 which was come out at Dec. 2011.

It should be like this, "The security advisory KB2736233 replaces the security update KB2695962."

Thank you for your effort. :)

0

Share this post


Link to post
Share on other sites

I already found a bug, though. When 2736233 is missing, the script asks for BOTH 2618451 AND 2726233 (both are Ax killbits). This is not right. It should only ask for the latest, which is 2736233.

There's an error on your homepage, Mim0. Windows XP > Changelog section tells me correctly about removed update package, KB2695962.

Windows XP > Update section, however, show me that KB2736233 replaces KB2618451 which was come out at Dec. 2011.

It should be like this, "The security advisory KB2736233 replaces the security update KB2695962."

It's not an error. Because you can decide in the INI whether you want to have (S)ecutiry update and/or (A)dvisories I left the old Killbits from december still in the list (latest security update for Killbits). And if the file-checker will find KB2736233 it will not ask for KB2618451. But KB2736233 is missing, it will be reported as missing. But also KB2618451.

If you put both updates to HF and run the file-checker again, KB2618451 will be reported as obsolete. I know, it's not perfect. Probably I find the time to extend the main-script of the file-checker.

Oh, another bug, the script expects MRT v 4.11.6601 instead of v4.12.6601

Oh sh*t, thank you!!!

New file-checker for XP:

2012-09-22
- Added: KB2744842 (MS12-063: Internet Explorer)
- Removed: KB2722913 (MS12-052: Internet Explorer, replace by KB2744842)
- Fixed: version of Malicious Software Removal Tool v4.12

Download: HFSLIPFC v.2012/05/04 with WindowsXP-update-list v.2012/09/22

Edited by Mim0
0

Share this post


Link to post
Share on other sites

It's not an error. Because you can decide in the INI whether you want to have (S)ecutiry update and/or (A)dvisories I left the old Killbits from december still in the list (latest security update for Killbits). And if the file-checker will find KB2736233 it will not ask for KB2618451. But KB2736233 is missing, it will be reported as missing. But also KB2618451.

If you put both updates to HF and run the file-checker again, KB2618451 will be reported as obsolete. I know, it's not perfect. Probably I find the time to extend the main-script of the file-checker.

New file-checker for XP:

2012-09-22
- Added: KB2744842 (MS12-063: Internet Explorer)
- Removed: KB2722913 (MS12-052: Internet Explorer, replace by KB2744842)
- Fixed: version of Malicious Software Removal Tool v4.12

Download: HFSLIPFC v.2012/05/04 with WindowsXP-update-list v.2012/09/22

OK, I see. Thank you, fast update. :)

0

Share this post


Link to post
Share on other sites

Thanx, mimo. I still think the Ax killbits thingie is not right. Why on earth would the script ask for TWO updates, when one superseeds the other? It should only ask for the latest. It's just wrong.

Your logic is wrong: IF 2736233 is not present, then it asks for both, BUT if BOTH are present, then one is flagged as unneeded??? That makes absolutely no sense at all! You can't have it both ways...

thanx, anyway!

0

Share this post


Link to post
Share on other sites

Thanx, mimo. I still think the Ax killbits thingie is not right. Why on earth would the script ask for TWO updates, when one superseeds the other? It should only ask for the latest. It's just wrong.

Your logic is wrong: IF 2736233 is not present, then it asks for both, BUT if BOTH are present, then one is flagged as unneeded??? That makes absolutely no sense at all! You can't have it both ways...

I'll make a simple table of what should have done:

                     | I have KB2618451 | Don't have KB2618451
I have KB2736233 | Outcome A | Outcome B
Don't have KB2736233 | Outcome C | Outcome D

Outcome A: Report that KB2618451 is unneeded.

Outcome B: Do nothing. Let it pass.

Outcome C: Notify the user about the KB2736233 if he turns on the Advisory option.

Outcome D: Tell the user that he needs either KB2736233 or KB2618451.

Edited by Explorer09
0

Share this post


Link to post
Share on other sites

I understand Mimo's approach: He asks for either one of the updates, so if both are present then one is not needed.

The easiest workaround for this issue is to just ask for the latest and problem solved!

0

Share this post


Link to post
Share on other sites

Just one update for XP.

And one update for Office Word 2003. (MS12-029 KB2598332 will soon be replaced)

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.