error 0x8007F0F4 when installing update KB944338

  • Thread starter Thread starter shawnr
  • Start date Start date
Re: Windows Update - KB944338

graft wrote:

> Wi have the same Problem with over 100 computers in our company.
> Installing Script 5.7 is no solution.. it's only a workaround for a single
> computer.
>
> MS must fix this Patch!

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.
 
Re: Windows Update - KB944338

"Harry Johnston [MVP]" wrote:

> graft wrote:
>
> > Wi have the same Problem with over 100 computers in our company.
> > Installing Script 5.7 is no solution.. it's only a workaround for a single
> > computer.
> >
> > MS must fix this Patch!
>
> 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.)

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!

> 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.
>
 
Re: Windows Update - KB944338

"graft" wrote:

>
> 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!
>

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.

> "Harry Johnston [MVP]" wrote:
>
> >
> > 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.)

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.
 
Re: Windows Update - KB944338

Raillon wrote:

> If MS protected
> jscript.dll/vbscript.dll from downgrading (at least from 5.7 when IE7 is
> present), this situation could have been avoided.

Yes, this is certainly a bug in the Windows Script 5.6 installer.

> [...] 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.

Sure, but this situation was not anticipated.

> 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.

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.
 
Re: Windows Update - KB944338

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

"Harry Johnston [MVP]" wrote:
> Yes, this is certainly a bug in the Windows Script 5.6 installer.

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.

> Sure, but this situation was not anticipated.

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.

> ...you could use the failure of KB944338 as a
> warning sign to identify those machines that need assistance.

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
install.
 
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

"shawnr" wrote:

> Repeated attempts to install this update from MS updates result in error code
> 0x8007F0F4. I have not tried through WSUS yet.
> KB944338.log:
> C:\WINDOWS\SoftwareDistribution\Download\77a3382edfdc03e5fb59ec5858f5073e\update\update.exe (version 6.2.29.0)
> 1.109: Hotfix started with following command line: /si
> /ParentInfo:bb999d44bb8b9647ae1f5a977943f5ed
> 1.109: FileVersion of C:\Program Files\internet explorer\iexplore.exe is
> Greater or Equal To 7.0.0.0
> 1.109: Condition Check for Line 1 of PreRequisite returned FALSE
> 1.109: KB944338 Setup encountered an error: The version of Internet
> Explorer you have installed does not match the update you are trying to
> install.
> 1.109: The version of Internet Explorer you have installed does not match
> the update you are trying to install.
> 1.109: Update.exe extended error code = 0xf0f4
>
> It appears browser detection has a problem. OS xpsp2, browser 7.0
> I have opened ticket with support. Anybody else seeing this?
 
You say it's impossible, but I too am running XP SP2 with IE version
7.0.5730.11, jscript.dll version 5.6.0.8831, and vbscript.dll version
5.6.0.8825.

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.


"Harry Johnston [MVP]" wrote:

> shawnr wrote:
>
> > both are ver 5.6.
>
> Did you check the version of the actual DLL files, or just the installed version
> of VBScript/Javascript? (Normally you'd expect them to be the same, but that
> isn't true in this case.)
>
> You can check the file version by navigating to c:\windows\system32, selecting
> jscript.dll, right-clicking, selecting Properties, and going to the Version tab.
> Please let us know the full version number, and also the modification date and
> file size in bytes.
>
> The reason I ask is that IE7 includes version 5.7.0.5730 of jscript.dll and
> vbscript.dll, so it shouldn't be possible to have version 5.6 if IE7 is installed.
>
> Harry.
>
 
chanceu wrote:

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

No, I said it shouldn't be possible - not quite the same thing! It's easy
enough to reproduce.

> 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.

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.
 
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
STOP
http://www.ie-vista.com/known_issues.html#pre-install

IEBlog : IE7 Installation and Anti-Malware Applications
http://blogs.msdn.com/ie/archive/2006/10/11/IE7-Installation-and-Anti_2D00_Malware-Applications.aspx

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 http://aumha.net
DTS-L http://dts-l.net/


chanceu wrote:
> You say it's impossible, but I too am running XP SP2 with IE version
> 7.0.5730.11, jscript.dll version 5.6.0.8831, and vbscript.dll version
> 5.6.0.8825.
>
> 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.
>
>
> "Harry Johnston [MVP]" wrote:
>
>> shawnr wrote:
>>
>>> both are ver 5.6.
>>
>> Did you check the version of the actual DLL files, or just the installed
>> version of VBScript/Javascript? (Normally you'd expect them to be the
>> same, but that isn't true in this case.)
>>
>> You can check the file version by navigating to c:\windows\system32,
>> selecting jscript.dll, right-clicking, selecting Properties, and going to
>> the Version tab. Please let us know the full version number, and also
>> the modification date and file size in bytes.
>>
>> The reason I ask is that IE7 includes version 5.7.0.5730 of jscript.dll
>> and
>> vbscript.dll, so it shouldn't be possible to have version 5.6 if IE7 is
>> installed.
>>
>> Harry.
 
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!

"chanceu" wrote:

> You say it's impossible, but I too am running XP SP2 with IE version
> 7.0.5730.11, jscript.dll version 5.6.0.8831, and vbscript.dll version
> 5.6.0.8825.
>
> 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.
>
>
> "Harry Johnston [MVP]" wrote:
>
> > shawnr wrote:
> >
> > > both are ver 5.6.
> >
> > Did you check the version of the actual DLL files, or just the installed version
> > of VBScript/Javascript? (Normally you'd expect them to be the same, but that
> > isn't true in this case.)
> >
> > You can check the file version by navigating to c:\windows\system32, selecting
> > jscript.dll, right-clicking, selecting Properties, and going to the Version tab.
> > Please let us know the full version number, and also the modification date and
> > file size in bytes.
> >
> > The reason I ask is that IE7 includes version 5.7.0.5730 of jscript.dll and
> > vbscript.dll, so it shouldn't be possible to have version 5.6 if IE7 is installed.
> >
> > Harry.
> >
 
Required reading IMHO before installing IE7:

Sandi's Installation Tips <= Steps #1-8, #10 & #11 take note of #12, then
STOP!
http://www.ie-vista.com/known_issues.html#pre-install
(ignore any references to Vista)

And I strongly recommend using
http://www.microsoft.com/windows/downloads/ie/getitnow.mspx as the
installation source, not Automatic/Windows Update.

Alternately, use this Direct Download link:
http://www.microsoft.com/downloads/details.aspx?familyid=9ae91ebe-3385-447c-8a30-081805b2f90b

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
http://blogs.msdn.com/ie/archive/2006/10/11/IE7-Installation-and-Anti_2D00_Malware-Applications.aspx

What's New in Internet Explorer 7
http://msdn2.microsoft.com/en-us/library/ms649487.aspx

Release Notes
http://msdn2.microsoft.com/en-us/ie/Aa740486.aspx

IEBlog: IE and Windows XP Service Pack 3
http://blogs.msdn.com/ie/archive/2008/05/05/ie-and-xpsp3.aspx
--
IE-specific newsgroup:
news://msnews.microsoft.com/microsoft.public.internetexplorer.general

~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002


Lightning Bolt wrote:
> 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!
>
> "chanceu" wrote:
>
>> You say it's impossible, but I too am running XP SP2 with IE version
>> 7.0.5730.11, jscript.dll version 5.6.0.8831, and vbscript.dll version
>> 5.6.0.8825.
>>
>> 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.
>>
>>
>> "Harry Johnston [MVP]" wrote:
>>
>>> shawnr wrote:
>>>
>>>> both are ver 5.6.
>>>
>>> Did you check the version of the actual DLL files, or just the installed
>>> version of VBScript/Javascript? (Normally you'd expect them to be the
>>> same, but that isn't true in this case.)
>>>
>>> You can check the file version by navigating to c:\windows\system32,
>>> selecting jscript.dll, right-clicking, selecting Properties, and going
>>> to
>>> the Version tab. Please let us know the full version number, and also
>>> the modification date and file size in bytes.
>>>
>>> The reason I ask is that IE7 includes version 5.7.0.5730 of jscript.dll
>>> and vbscript.dll, so it shouldn't be possible to have version 5.6 if IE7
>>> is installed.
>>>
>>> Harry.
 
Back
Top