Hotfix KB938127 fails to install via WSUS. Errorcode 0x8007F0F1

Getting a handful of desktops that get this error when trying to install the
update from our WSUS server.

They all run WinXP SP3 with IE7.

They were all upgraded from Windows 2000 to XP via a SP3+IE7 slipstream.

Big Hiller wrote:
> Getting a handful of desktops that get this error when trying to
> install the update from our WSUS server.
>
> They all run WinXP SP3 with IE7.
>
> They were all upgraded from Windows 2000 to XP via a SP3+IE7
> slipstream.

** This is not a WSUS newsgroup - although there are WSUS newsgroups and I
have taken the liberty of cross-posting this response and your original
message to one. **

Can we assume the updates don't fail if you install manually and/or via
http://windowsupdate.microsoft.com/ ?

This is the update?
http://support.microsoft.com/kb/938127
And you read up on it?

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

[Crosspost to WSUS newsgroup]

0x8007F0F1 = STATUS_INCOMPARABLE_BRANCHES

In most cases, the error suggests the computer has been compromised by a
hijackware infection.

QED: Is this the only update that fails to install on these computers (e.g.,
did KB969897 install successfully)?

The above notwithstanding...

> They were all upgraded from Windows 2000 to XP via a SP3+IE7 slipstream.

IIRC, you cannot integrate IE7 in a slipstream of WinXP SP3 (unless you use
nLite or similar third-party application; the current IE7 package does not
support the /integrate switch) and such methods are not supported. Have you
upgraded any other computers via this method which are not affected by this
error?
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Client - since 2002


Big Hiller wrote:
> Getting a handful of desktops that get this error when trying to install
> the
> update from our WSUS server.
>
> They all run WinXP SP3 with IE7.
>
> They were all upgraded from Windows 2000 to XP via a SP3+IE7 slipstream.

Yes, the machines that are having issues were ones upgraded from Win2k to Xp
via a slipstreamed source (using nLite). All other updates seem to apply fine.

"PA Bear [MS MVP]" wrote:

> [Crosspost to WSUS newsgroup]
>
> 0x8007F0F1 = STATUS_INCOMPARABLE_BRANCHES
>
> In most cases, the error suggests the computer has been compromised by a
> hijackware infection.
>
> QED: Is this the only update that fails to install on these computers (e.g.,
> did KB969897 install successfully)?
>
> The above notwithstanding...
>
> > They were all upgraded from Windows 2000 to XP via a SP3+IE7 slipstream.
>
> IIRC, you cannot integrate IE7 in a slipstream of WinXP SP3 (unless you use
> nLite or similar third-party application; the current IE7 package does not
> support the /integrate switch) and such methods are not supported. Have you
> upgraded any other computers via this method which are not affected by this
> error?
> --
> ~Robear Dyer (PA Bear)
> MS MVP-IE, Mail, Security, Windows Client - since 2002
>
>
> Big Hiller wrote:
> > Getting a handful of desktops that get this error when trying to install
> > the
> > update from our WSUS server.
> >
> > They all run WinXP SP3 with IE7.
> >
> > They were all upgraded from Windows 2000 to XP via a SP3+IE7 slipstream.
>
>

As I said, slipstreaming IE7 is not supported (hence the
INCOMPARABLE_BRANCHES error; i.e., GDR vs QFX) so WYSIWYG.

Big Hiller wrote:
> Yes, the machines that are having issues were ones upgraded from Win2k to
> Xp
> via a slipstreamed source (using nLite). All other updates seem to apply
> fine.
>
> "PA Bear [MS MVP]" wrote:
>
>> [Crosspost to WSUS newsgroup]
>>
>> 0x8007F0F1 = STATUS_INCOMPARABLE_BRANCHES
>>
>> In most cases, the error suggests the computer has been compromised by a
>> hijackware infection.
>>
>> QED: Is this the only update that fails to install on these computers
>> (e.g., did KB969897 install successfully)?
>>
>> The above notwithstanding...
>>
>>> They were all upgraded from Windows 2000 to XP via a SP3+IE7 slipstream.
>>
>> IIRC, you cannot integrate IE7 in a slipstream of WinXP SP3 (unless you
>> use
>> nLite or similar third-party application; the current IE7 package does
>> not
>> support the /integrate switch) and such methods are not supported. Have
>> you upgraded any other computers via this method which are not affected
>> by
>> this error?
>> --
>> ~Robear Dyer (PA Bear)
>> MS MVP-IE, Mail, Security, Windows Client - since 2002
>>
>>
>> Big Hiller wrote:
>>> Getting a handful of desktops that get this error when trying to install
>>> the
>>> update from our WSUS server.
>>>
>>> They all run WinXP SP3 with IE7.
>>>
>>> They were all upgraded from Windows 2000 to XP via a SP3+IE7 slipstream.

So, in less complicated terms, I'm screwed.

Wonderful.

For future reference, what is the best way to upgrade 150 PCs from Windows
2000 -> XP and install IE7?

Does MS think we should walk around and manually upgrade them all 150PCs?
Buy some really expensive software that we'll use once?

What if I said that IE7 was NOT slipstreamed? Then would the solution be
different?

Basically, this isn't much help to me.

Off to the next forum, I guess.


"PA Bear [MS MVP]" wrote:

> As I said, slipstreaming IE7 is not supported (hence the
> INCOMPARABLE_BRANCHES error; i.e., GDR vs QFX) so WYSIWYG.
>
> Big Hiller wrote:
> > Yes, the machines that are having issues were ones upgraded from Win2k to
> > Xp
> > via a slipstreamed source (using nLite). All other updates seem to apply
> > fine.
> >
> > "PA Bear [MS MVP]" wrote:
> >
> >> [Crosspost to WSUS newsgroup]
> >>
> >> 0x8007F0F1 = STATUS_INCOMPARABLE_BRANCHES
> >>
> >> In most cases, the error suggests the computer has been compromised by a
> >> hijackware infection.
> >>
> >> QED: Is this the only update that fails to install on these computers
> >> (e.g., did KB969897 install successfully)?
> >>
> >> The above notwithstanding...
> >>
> >>> They were all upgraded from Windows 2000 to XP via a SP3+IE7 slipstream.
> >>
> >> IIRC, you cannot integrate IE7 in a slipstream of WinXP SP3 (unless you
> >> use
> >> nLite or similar third-party application; the current IE7 package does
> >> not
> >> support the /integrate switch) and such methods are not supported. Have
> >> you upgraded any other computers via this method which are not affected
> >> by
> >> this error?
> >> --
> >> ~Robear Dyer (PA Bear)
> >> MS MVP-IE, Mail, Security, Windows Client - since 2002
> >>
> >>
> >> Big Hiller wrote:
> >>> Getting a handful of desktops that get this error when trying to install
> >>> the
> >>> update from our WSUS server.
> >>>
> >>> They all run WinXP SP3 with IE7.
> >>>
> >>> They were all upgraded from Windows 2000 to XP via a SP3+IE7 slipstream.
>
>

Big Hiller wrote:
> So, in less complicated terms, I'm screwed.
>
> Wonderful.
>
> For future reference, what is the best way to upgrade 150 PCs from
> Windows 2000 -> XP and install IE7?
>
> Does MS think we should walk around and manually upgrade them all
> 150PCs? Buy some really expensive software that we'll use once?
>
> What if I said that IE7 was NOT slipstreamed? Then would the
> solution be different?
>
> Basically, this isn't much help to me.
>
> Off to the next forum, I guess.

Group Policies.
Scripts.

All of those are great ways (free) to do what you wanted to do.

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html

"Shenan Stanley" <> wrote in message
news:O0ce4vy%...
> Big Hiller wrote:

>> Re: Hotfix KB938127 fails to install via WSUS. Errorcode 0x8007F0F1

>> Getting a handful of desktops that get this error when trying to
>> install the update from our WSUS server.
>>
>> They all run WinXP SP3 with IE7.
>>
>> They were all upgraded from Windows 2000 to XP via a SP3+IE7
>> slipstream.

There are three different packages for KB938127 for Windows XP. One of them
is for IE6 on XPSP2, which was superseded by Windows XP Service Pack 3. This
package should not have detected as Needed on an XP/SP3 or XP/IE7 system,
but that's not to say it doesn't. It's also possible that something in the
SP3+IE7 slipstream is adversely affecting the detection logic of this
package, and it's not properly detecting the SP3 and/or the IE7. In any
event, this package should be declined, unless you still have XP machines
without IE7 or SP3.

The second package is explictly for IE7 on Windows XP systems, and has not
been superseded. This update is identified as Update ID:
a2a1d3b3-c228-45ad-9175-566e7dd41dd1. This should be the only
KB938127/MS07-050 package approved for XP/SP3 or XP/IE7 systems. Verify that
it is this package that is approved. If you're receiving the 0x8007F0F1
error on this package, then we'll need to evaluate the situation further.

The third package was released in error on Feb 26th of this year, identified
as Update ID: bbd4e93a-59e6-4756-bf81-f8cef5dbe734, and it also should be
declined, as should all of the other KB938127 package released on 2/26/09.

(I believe those Feb 26th packages may even be Expired by Microsoft.)

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Shenan Stanley tells us that Big Hiller wrote:

>> Getting a handful of desktops that get this error when trying to
>> install the update from our WSUS server.
>>
>> They all run WinXP SP3 with IE7.
>>
>> They were all upgraded from Windows 2000 to XP via a SP3+IE7
>> slipstream.

It has been known for a long time that slipstreaming IE7 into XP breaks it. In
particular it is usually impossible to install updates to IE7.

If you've only recently started moving to XP you might not be aware that the
Windows 2000 method for slipstreaming updates is no longer supported in XP. You
need to use the /integrate command-line argument instead. (If you do this with
IE7, you get an error message which basically says that IE7 cannot be integrated.)

In a different post, Big Heller wrote:

> So, in less complicated terms, I'm screwed.
>
> Wonderful.

It would be worth trying a repair install, aka in-place upgrade, using
uncorrupted Windows XP SP3 media, on one of the machines. This *might* fix the
problem, at any rate I suspect it would be the best bet.

> For future reference, what is the best way to upgrade 150 PCs from Windows
> 2000 -> XP and install IE7?

WSUS would be the easiest way for you to do the IE7 install, since you are
already using it.

> Does MS think we should walk around and manually upgrade them all 150PCs?

How did you do the 2000->XP upgrade this time? You can do the same thing, just
use uncorrupted install media.

> Buy some really expensive software that we'll use once?
>
> What if I said that IE7 was NOT slipstreamed? Then would the solution be
> different?

Well, yeah - uninstall and reinstall IE7. Sorry.

> Basically, this isn't much help to me.

Unfortunately sometimes there just isn't any known way to fix a problem. :-(

> Off to the next forum, I guess.

If you do find a solution, please let us know so we can pass it on to the next
person to ask. Folks don't get caught by this quite as often anymore, due to
the decreasing count of Win2k machines I suppose, but it still comes up now and
then. Unfortunately some third party web sites are still advising people to use
Windows 2000 techniques without pointing out that they aren't supported in later
versions. :-(

Harry.

> It would be worth trying a repair install, aka in-place upgrade, using
> uncorrupted Windows XP SP3 media, on one of the machines. This *might*
> fix
> the problem, at any rate I suspect it would be the best bet.

I disagree, Harry, at least not without first seeing...

How to perform a repair installation of Windows XP if a later version of
Internet Explorer is installed
http://support.microsoft.com/kb/917964

--
~Robear


Harry Johnston [MVP] wrote:
> Shenan Stanley tells us that Big Hiller wrote:
>
>>> Getting a handful of desktops that get this error when trying to
>>> install the update from our WSUS server.
>>>
>>> They all run WinXP SP3 with IE7.
>>>
>>> They were all upgraded from Windows 2000 to XP via a SP3+IE7
>>> slipstream.
>
> It has been known for a long time that slipstreaming IE7 into XP breaks
> it.
> In particular it is usually impossible to install updates to IE7.
>
> If you've only recently started moving to XP you might not be aware that
> the
> Windows 2000 method for slipstreaming updates is no longer supported in
> XP.
> You need to use the /integrate command-line argument instead. (If you do
> this with IE7, you get an error message which basically says that IE7
> cannot be integrated.)
> In a different post, Big Heller wrote:
>
>> So, in less complicated terms, I'm screwed.
>>
>> Wonderful.
>
> It would be worth trying a repair install, aka in-place upgrade, using
> uncorrupted Windows XP SP3 media, on one of the machines. This *might*
> fix
> the problem, at any rate I suspect it would be the best bet.
>
>> For future reference, what is the best way to upgrade 150 PCs from
>> Windows
>> 2000 -> XP and install IE7?
>
> WSUS would be the easiest way for you to do the IE7 install, since you are
> already using it.
>
>> Does MS think we should walk around and manually upgrade them all 150PCs?
>
> How did you do the 2000->XP upgrade this time? You can do the same thing,
> just use uncorrupted install media.
>
>> Buy some really expensive software that we'll use once?
>>
>> What if I said that IE7 was NOT slipstreamed? Then would the solution be
>> different?
>
> Well, yeah - uninstall and reinstall IE7. Sorry.
>
>> Basically, this isn't much help to me.
>
> Unfortunately sometimes there just isn't any known way to fix a problem.
> :-(
>
>> Off to the next forum, I guess.
>
> If you do find a solution, please let us know so we can pass it on to the
> next person to ask. Folks don't get caught by this quite as often
> anymore,
> due to the decreasing count of Win2k machines I suppose, but it still
> comes up now
> and then. Unfortunately some third party web sites are still advising
> people to use Windows 2000 techniques without pointing out that they
> aren't
> supported in later versions. :-(
>
> Harry.