error 0x8007F0F4 when installing update KB944338

Discussion in 'Windows Update' started by shawnr, Apr 8, 2008.

  1. There isn't actually a problem with the patch; the problem (mismatched
    components) was already present on your computers, the patch just revealed it.

    The cause of the problem is currently unknown, but theories include third-party
    anti-malware software preventing system components from being updated during the
    IE7 install and third-party installers downgrading the components afterwards.
    (I favour the latter theory but more experienced experts seem to prefer the
    former, so YMMV.)

    Hopefully Microsoft will release an automated fix at some point, either via this
    patch or an IE7 patch. But as it is likely to take some time, you may prefer to
    deploy Script 5.7 either via a solution like SMS (as Raillon describes) or with
    a startup script, or (failing all else) by brute force. How do you deploy
    third-party software updates?

    Harry Johnston [MVP], Apr 14, 2008
    1. Advertisements

  2. shawnr

    graft Guest

    I have found the source of my problems. I have installed Windows Script 5.6
    manually on these machine due to Problems with the installation of another
    software. I know since thursday last week that an newer version of Windows
    Script (5.7) exist.
    Was it my error? Was it the error from Windows Script 5.6 to install over an
    newer Version? Is it the error in Patch KB944338?

    I think it's not my error!
    graft, Apr 15, 2008
    1. Advertisements

  3. shawnr

    Raillon Guest

    Thank you, graft - I didn't even think about testing the installation of
    Windows Script 5.6 over jscript.dll/vbscript.dll 5.7. It turns out this DOES
    successfully downgrade these dlls to 5.6 - in fact, this even happens if
    Windows Script 5.7 was previously directly installed.
    graft's information and my confirmation show that jscript.dll/vbscript.dll
    can indeed be downgraded from 5.7 to 5.6, so your theory is shown to be
    possible, Harry. However, I do agree with graft that MS is at fault here - by
    not allowing the exe to apply when IE7 and jscript.dll/vbscript.dll 5.6 are
    present, and not even giving a correctly-informative error message, it leaves
    the end-user in confusion as to what to do. If MS protected
    jscript.dll/vbscript.dll from downgrading (at least from 5.7 when IE7 is
    present), this situation could have been avoided. However, the downgrading is
    not prevented, so MS should have included this possible situation in
    KB944338's exe's logic. If the error message from KB944338's exe indicated
    that with IE7, Windows Script should also be 5.7, and is not, then the
    end-user would know what to do.

    As it is, with this oversight I must leave automated detection of IE and
    Windows Script version (with upgrade of Windows Script when needed) constant
    in my environment, lest Windows Script be downgraded by other installs,
    leaving a security hole in which KB944338 cannot be applied.
    Raillon, Apr 15, 2008
  4. Yes, this is certainly a bug in the Windows Script 5.6 installer.
    Sure, but this situation was not anticipated.
    Hopefully there will eventually be a better resolution. However, assuming the
    downgrade does not happen frequently, you could use the failure of KB944338 as a
    warning sign to identify those machines that need assistance.

    Harry Johnston [MVP], Apr 16, 2008
  5. shawnr

    Raillon Guest

    Harry, thank you for your continued conversation on this. A few more thoughts:

    I'm not sure it's just the Windows Script 5.6 installer - it appears that
    jscript.dll/vbscript.dll 5.7 can be overwritten with older versions from any
    installer. I'm not absolutely sure this is a bug - it may be by design.
    Agreed - however, since we've discovered the situation, I do hope it will be
    corrected. I also expect that this situation will be anticipated in future
    updates where its relevant.
    I do have automated notification from my WSUS, however, I am not comfortable
    with relying solely on manual response - we can get overwhelmed with other
    items and not be able to quickly resolve each case. Though we always check on
    machines that report WSUS failures (unless we're overwhelmed), with the
    automated detection/application (and re-application if needed) of Windows
    Script 5.7, I am better covered, especially since - in this case - a
    compliant machine can suddenly become non-compliant due to an unrelated
    Raillon, Apr 16, 2008
  6. shawnr

    4194dave Guest

    i am having the same problem i re-installed windows service pack 2 but that
    didnt fix the problem my next option is going to be to contact my computer's
    manufacturer perhaps that will be helpful to you -when i ran a diagnostic
    test on this problem that is what i was told to do
    4194dave, Apr 21, 2008
  7. shawnr

    chanceu Guest

    You say it's impossible, but I too am running XP SP2 with IE version
    7.0.5730.11, jscript.dll version, and vbscript.dll version

    From what I've read, I have no doubt that installing the package you
    describe will fix the problem. However, I would really like an explanation
    detailing how this happened. This is either something malicious or we all
    installed something reverted the DLL's to 5.6 instead of leaving the newer
    versions in place.
    chanceu, Apr 24, 2008
  8. No, I said it shouldn't be possible - not quite the same thing! It's easy
    enough to reproduce.
    One known way for this to happen is to install IE7 and then Windows Script 5.6.

    I suspect third-party software installers incorporating Windows Script 5.6. It
    could also be the result of security products preventing the files from being
    updated when IE7 is installed.

    Harry Johnston [MVP], Apr 26, 2008
  9. The most likely cause of this behavior (i.e., installing IE7 without Windows
    Script 5.7 also being installed) is due to not having disabled all real-time
    protections prior to installing IE7.

    Sandi's Installation Tips <= Steps #1-8, #10 & #11; take note of #12, then

    IEBlog : IE7 Installation and Anti-Malware Applications

    IMHO this is yet another reason why IE7 should *never* have been offered by
    Windows Update except as an Optional (i.e., user must opt-in) update.
    ~Robear Dyer (PA Bear)
    MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
    AumHa VSOP & Admin
    PA Bear [MS MVP], Apr 26, 2008
  10. Oh Great!!! I should have read all of this PRIOR to downloading 7.0 I can't
    work from home with 7.0 and want 6.0 back but all I've read is I can't get
    6.0 back, either. Screwed again!!! Dang!
    Lightning Bolt, Jun 3, 2008
  11. Required reading IMHO before installing IE7:

    Sandi's Installation Tips <= Steps #1-8, #10 & #11; take note of #12, then
    (ignore any references to Vista)

    And I strongly recommend using as the
    installation source, not Automatic/Windows Update.

    Alternately, use this Direct Download link:

    Tip: Save the installer to your desktop, do not Run it.

    Make *certain* that you check in at Windows Update immediately after
    installing IE7 and install any critical updates offered. If Optional
    Updates category offers Root Certificates update, I recommend installing it
    to take full advantage of IE7's additional security.

    IEBlog : IE7 Installation and Anti-Malware Applications

    What's New in Internet Explorer 7

    Release Notes

    IEBlog: IE and Windows XP Service Pack 3
    IE-specific newsgroup:

    ~Robear Dyer (PA Bear)
    MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
    PA Bear [MS MVP], Jun 3, 2008
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.