RE: SP2 Won't Install

--
oklahoma junebug


"KDB" wrote:

> I recently had to complete a system restore. First I had issues with
> downloading updates, but that is now fixed. My new issue is I cannot get SP@
> installed. It starts the install process and about halfway through it
> cancels by itselft and does not supply any reason or error code. It seems to
> happend during the backup process of the system registery.
>
> Any suggestions?

KDB

On most systems it is C:\Program Files. Is your Programs Files located
on a drive or partition with a different drive letter?

BTW I think the Error Code for your error is 0x80242008 but getting an
explanation for what it means is elusive.

--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



KDB wrote:
> Is there anyone out there that has some suggestions...I tried
> several
> different fixes posted on the group and none have worked.
>
> Please Help...
>
> "junebug" wrote:
>
>>
>> --
>> oklahoma junebug
>>
>>
>> "KDB" wrote:
>>
>>> I recently had to complete a system restore. First I had issues
>>> with downloading updates, but that is now fixed. My new issue is
>>> I
>>> cannot get SP@ installed. It starts the install process and about
>>> halfway through it cancels by itselft and does not supply any
>>> reason or error code. It seems to happend during the backup
>>> process of the system registery.
>>>
>>> Any suggestions?

"Gerry Cornell" <> wrote in message
news:...
> KDB
>
> On most systems it is C:\Program Files. Is your Programs Files located
> on a drive or partition with a different drive letter?
>
> BTW I think the Error Code for your error is 0x80242008 but getting an
> explanation for what it means is elusive.


Where are you seeing that, Gerry?

In any case we can easily find the meaning of that code with a web search:

http://docxp.mvps.org/WU5-ERR.htm

(Live Search for
0x80242008 microsoft codes

<quote>
0x80242008 -2145116152 SUS E UH OPERATIONCANCELLED
The install was canceled via a handler method (as opposed to, for example,
an installer running with UI that was cancelled externally to SUS)
</quote>


I agree that this sounds like a code that OP might be seeing based on
the symptom description. However, its real value would only be apparent
when seen in whatever context it was issued in. That's why I suggest
the ProcMon trace (if necessary) to supplement whatever context there
really is in all of the diagnostics being produced by the install.


FYI

Robert
---

Robert

extended error code = 0xf00d from the log.

Searching on the 0xf00d led me to a Google thread where the Error code
was 0x80242008 and the question asked was where is the Program Files
folder. If the folder is not in the expected place then it is the kind
of situation where an error can arise. If the Program folder cannot be
found how would the system react and report it?

Coincidentally Mow Green was involved in both threads.

--

Regards.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



"Robert Aldwinckle" <> wrote in message
news:...
> "Gerry Cornell" <> wrote in message
> news:...
>> KDB
>>
>> On most systems it is C:\Program Files. Is your Programs Files
>> located
>> on a drive or partition with a different drive letter?
>>
>> BTW I think the Error Code for your error is 0x80242008 but getting
>> an
>> explanation for what it means is elusive.
>
>
> Where are you seeing that, Gerry?
>
> In any case we can easily find the meaning of that code with a web
> search:
>
> http://docxp.mvps.org/WU5-ERR.htm
>
> (Live Search for
> 0x80242008 microsoft codes
>
> <quote>
> 0x80242008 -2145116152 SUS E UH OPERATIONCANCELLED
> The install was canceled via a handler method (as opposed
> to, for example,
> an installer running with UI that was cancelled
> externally to SUS)
> </quote>
>
>
> I agree that this sounds like a code that OP might be seeing based
> on
> the symptom description. However, its real value would only be
> apparent
> when seen in whatever context it was issued in. That's why I
> suggest
> the ProcMon trace (if necessary) to supplement whatever context
> there
> really is in all of the diagnostics being produced by the install.
>
>
> FYI
>
> Robert
> ---
>
>

"Gerry Cornell" <> wrote in message
news:...
> Robert
>
> extended error code = 0xf00d from the log.


Here's how I interpret that code.

Convert it to decimal and search.
Actually there is a particular reference page which I expect to find
but the important thing is that the decimal values are better documented
than their hex equivalents.

http://www.microsoft.com/technet/pro.../winupdte.mspx

(Live Search for
61453 update codes site:microsoft.com
)

<quote>
61453
STATUS_USER_CANCELLED
%1 Setup canceled.


</quote>

So we see that this one is just a generic "we give up" code. ; )

More significant I suspect is the other hex value which appeared after it 0x643.
Again, converting to decimal appears to give the most meaning:

http://support.microsoft.com/default.aspx/kb/229683/
(Live Search for
1603 intitle:codes site:microsoft.com
)

<quote>
ERROR_INSTALL_FAILURE 1603 Fatal error during installation.
</quote>


and again it has insufficient specificity to help us much.
E.g. *what* was the "fatal error"? Hopefully that is where
other diagnostics will help clarify.


>
> Searching on the 0xf00d led me to a Google thread where the Error code
> was 0x80242008 and the question asked was where is the Program Files
> folder. If the folder is not in the expected place then it is the kind
> of situation where an error can arise. If the Program folder cannot be
> found how would the system react and report it?


Ok. I found that. I think it was a guess because no log was provided
to show the context to substantiate it.

Ottmar explained it previously and again, the context of the code
is more important than the code itself.

http://www.microsoft.com/communities...1e6&sloc=en-us

(web interface search for
0x80242008 log
)


FYI

Robert
---

Robert

Your approach is much more sophisticated than my own. This is the post
where I made the connection.

Looking again at this log in this thread. What do you make of these
lines?

810.203: CheckRegistryValue: RegOpenKeyEx for
SOFTWARE\Microsoft\Active
Setup\Installed Components\{FDC11A6F-17D1-48f9-9EA3-9051954BAA24}
KeyName
failed :0x2

It seems not to like something to do with Net Framework.

The problem is I understand that you get a lot of lines in these
update logs which look like failures when they can be safely
disregarded.


--

Regards.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Robert Aldwinckle wrote:
> "Gerry Cornell" <> wrote in message
> news:...
>> Robert
>>
>> extended error code = 0xf00d from the log.
>
>
> Here's how I interpret that code.
>
> Convert it to decimal and search.
> Actually there is a particular reference page which I expect to find
> but the important thing is that the decimal values are better
> documented than their hex equivalents.
>
> http://www.microsoft.com/technet/pro.../winupdte.mspx
>
> (Live Search for
> 61453 update codes site:microsoft.com
> )
>
> <quote>
> 61453
> STATUS_USER_CANCELLED
> %1 Setup canceled.
>
>
> </quote>
>
> So we see that this one is just a generic "we give up" code. ; )
>
> More significant I suspect is the other hex value which appeared
> after it 0x643. Again, converting to decimal appears to give the
> most
> meaning:
> http://support.microsoft.com/default.aspx/kb/229683/
> (Live Search for
> 1603 intitle:codes site:microsoft.com
> )
>
> <quote>
> ERROR_INSTALL_FAILURE 1603 Fatal error during installation.
> </quote>
>
>
> and again it has insufficient specificity to help us much.
> E.g. *what* was the "fatal error"? Hopefully that is where
> other diagnostics will help clarify.
>
>
>>
>> Searching on the 0xf00d led me to a Google thread where the Error
>> code was 0x80242008 and the question asked was where is the Program
>> Files folder. If the folder is not in the expected place then it is
>> the kind of situation where an error can arise. If the Program
>> folder cannot be found how would the system react and report it?
>
>
> Ok. I found that. I think it was a guess because no log was
> provided to show the context to substantiate it.
>
> Ottmar explained it previously and again, the context of the code
> is more important than the code itself.
>
> http://www.microsoft.com/communities...1e6&sloc=en-us
>
> (web interface search for
> 0x80242008 log
> )
>
>
> FYI
>
> Robert
> ---

> The problem is I understand that you get a lot of lines in these update logs which look
> like failures when they can be safely disregarded.

Yeppers, Gerry. Start at the *end* of the log and work backwards.
Knowing which errors are meaningless and which contain a clue would
confuse Sherlock Holmes.

From : http://support.microsoft.com/kb/902093

> Locating Failures in the log file
> If you received a specific error message on the Windows Update Web site, follow these
> steps:
> 1. Open the Windowsupdate.log log file in Notepad.
> 2. On the Edit menu, click Find, and then search for the specific error message.
> Note The Web site displays the final error message. This final error message may have
> been caused by a failure that is described earlier in the Windowsupdate.log log file.
>
> Additionally, if you do not know which error occurred on the Windows update Web site or
> you want to find more information about a failure by Automatic Updates, search for the
> following key words:
> • FATAL
> • WARNING
> Note Not all warnings are critical errors. Start with the fatal errors and then work to
> the top of the Windowsupdate.log log file to make sure that you have identified the
> correct error message.


MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============



Gerry Cornell wrote:

> Robert
>
> Your approach is much more sophisticated than my own. This is the post
> where I made the connection.
>
> Looking again at this log in this thread. What do you make of these lines?
>
> 810.203: CheckRegistryValue: RegOpenKeyEx for SOFTWARE\Microsoft\Active
> Setup\Installed Components\{FDC11A6F-17D1-48f9-9EA3-9051954BAA24} KeyName
> failed :0x2
>
> It seems not to like something to do with Net Framework.
>
> The problem is I understand that you get a lot of lines in these update
> logs which look like failures when they can be safely disregarded.
>
>

Hi Mow

I take on board what you say.

However, in the partial log posted here neither FATAL or WARNING
appear.
The system seems to believe the User cancelled when the user is
unaware
that they cancelled! Of course only a part of the Log is posted here.

At your invitation a copy of the full log was posted by the OP to you
by email on 27 December. I have been watching for your reply but
nothing
has appeared. I would be interested to know what you made of it?

Robert was picking me up for interpreting the extended error code =
0xf00d from the log to an 0x80242008 error code.

Regards.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Hi Mow

I take on board what you say.

However, in the partial log posted here neither FATAL or WARNING
appear.
The system seems to believe the User cancelled when the user is
unaware
that they cancelled! Of course only a part of the Log is posted here.

At your invitation a copy of the full log was posted by the OP to you
by email on 27 December. I have been watching for your reply but
nothing
has appeared. I would be interested to know what you made of it?

Robert was picking me up for interpreting the extended error code =
0xf00d from the log to an 0x80242008 error code.

Regards.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


----- Original Message -----
From: "MowGreen [MVP]" <>
Newsgroups: microsoft.public.windowsupdate
Sent: Thursday, January 04, 2007 3:37 PM
Subject: Re: SP2 Won't Install


>> The problem is I understand that you get a lot of lines in these
>> update logs which look like failures when they can be safely
>> disregarded.
>
> Yeppers, Gerry. Start at the *end* of the log and work backwards.
> Knowing which errors are meaningless and which contain a clue would
> confuse Sherlock Holmes.
>
> From : http://support.microsoft.com/kb/902093
>
>> Locating Failures in the log file
>> If you received a specific error message on the Windows Update Web
>> site, follow these steps:
>> 1. Open the Windowsupdate.log log file in Notepad. 2. On the Edit
>> menu, click Find, and then search for the specific error message.
>> Note The Web site displays the final error message. This final
>> error message may have been caused by a failure that is described
>> earlier in the Windowsupdate.log log file.
>> Additionally, if you do not know which error occurred on the
>> Windows update Web site or you want to find more information about
>> a failure by Automatic Updates, search for the following key words:
>> • FATAL • WARNING Note Not all warnings are critical errors. Start
>> with the fatal errors and then work to the top of the
>> Windowsupdate.log log file to make sure that you have identified
>> the correct error message.
>
>
> MowGreen [MVP 2003-2007]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
>

Gerry ... seems there were quite a bit of HP updates needed PRIOR to
installing SP2. Pointed this out to the OP and am still waiting to hear
back.
OEM is just another word for _______

If ya really want to know what was the 'silver bullet' that allowed SP2
to install ... you can bet yer bottom $ I will.


MG

Gerry Cornell wrote:

>
>
> Hi Mow
>
> I take on board what you say.
>
> However, in the partial log posted here neither FATAL or WARNING appear.
> The system seems to believe the User cancelled when the user is unaware
> that they cancelled! Of course only a part of the Log is posted here.
>
> At your invitation a copy of the full log was posted by the OP to you
> by email on 27 December. I have been watching for your reply but nothing
> has appeared. I would be interested to know what you made of it?
>
> Robert was picking me up for interpreting the extended error code =
> 0xf00d from the log to an 0x80242008 error code.
>
> Regards.
>
> Gerry
> ~~~~
> FCA
> Stourport, England
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
>
>
>
> Hi Mow
>
> I take on board what you say.
>
> However, in the partial log posted here neither FATAL or WARNING appear.
> The system seems to believe the User cancelled when the user is unaware
> that they cancelled! Of course only a part of the Log is posted here.
>
> At your invitation a copy of the full log was posted by the OP to you
> by email on 27 December. I have been watching for your reply but nothing
> has appeared. I would be interested to know what you made of it?
>
> Robert was picking me up for interpreting the extended error code =
> 0xf00d from the log to an 0x80242008 error code.
>
> Regards.
>
> Gerry
> ~~~~
> FCA
> Stourport, England
> Enquire, plan and execute
> ~~~~~~~~~~~~~~~~~~~
>
>
> ----- Original Message ----- From: "MowGreen [MVP]"
> <>
> Newsgroups: microsoft.public.windowsupdate
> Sent: Thursday, January 04, 2007 3:37 PM
> Subject: Re: SP2 Won't Install
>
>
>>> The problem is I understand that you get a lot of lines in these
>>> update logs which look like failures when they can be safely
>>> disregarded.
>>
>>
>> Yeppers, Gerry. Start at the *end* of the log and work backwards.
>> Knowing which errors are meaningless and which contain a clue would
>> confuse Sherlock Holmes.
>>
>> From : http://support.microsoft.com/kb/902093
>>
>>> Locating Failures in the log file
>>> If you received a specific error message on the Windows Update Web
>>> site, follow these steps:
>>> 1. Open the Windowsupdate.log log file in Notepad. 2. On the Edit
>>> menu, click Find, and then search for the specific error message.
>>> Note The Web site displays the final error message. This final error
>>> message may have been caused by a failure that is described earlier
>>> in the Windowsupdate.log log file.
>>> Additionally, if you do not know which error occurred on the Windows
>>> update Web site or you want to find more information about a failure
>>> by Automatic Updates, search for the following key words:
>>> • FATAL • WARNING Note Not all warnings are critical errors. Start
>>> with the fatal errors and then work to the top of the
>>> Windowsupdate.log log file to make sure that you have identified the
>>> correct error message.
>>
>>
>>
>> MowGreen [MVP 2003-2007]
>> ===============
>> *-343-* FDNY
>> Never Forgotten
>> ===============
>>
>>
>>
>