HELP! but I have a clue...

Many posts have been sent, and many suggestions have been offered, about the
NON-installation of the "Critical Update KB837009". Nothing has seemed to
help, as all of the fixes that are downloadable seem to require I be running
WinXP - and I'm still on 98se.

I HAVE, however found the following entry in my Registry, in TWO locations.
Perhaps one of these is the problem......

Location 1:
My Computer\HKEY-CURRENT-USER\Software\Microsoft\Windows\
Current Verison\Explorer\Doc Find Spec MRU

Location 2:
My Computer\HKEY-CURRENT-USER\DEFAULTS\Software\Microsoft\Windows\
Current Verison\Explorer\Doc Find Spec MRU

(Notice that Location 2 has "DEFAULTS" in the path; Loc 1 does not.)

The entries are

NAME Data
ab (Default) [value not set]
ab a "*.qbw"
ab b "wutemp, windowsupdate"
ab c "?837009.*"
ab d "*.exe"
ab e "dox_*.*"
ab f ""
ab g "??837009.*"
ab h "dox-*.*"
ab i "*.doc, *.xls"
ab j "wutemp"
ab MRUList "abjdgcihe"

These are the ONLY places in the registry that '837009' appears.

Any suggestions on how to procede from here? I'm not SUPER comfortable
mucking about in the Registry, but I'm quite capable at following
instructions. :O)

MrBill

Maybe because Win98 is a dead product and no longer supported for Security Updates and
therefore there is NO KB837009 patch for Win98.

Dave



"MrBill" <> wrote in message
news:5231BBB7-0169-4FAD-BFD0-...
| Many posts have been sent, and many suggestions have been offered, about the
| NON-installation of the "Critical Update KB837009". Nothing has seemed to
| help, as all of the fixes that are downloadable seem to require I be running
| WinXP - and I'm still on 98se.
|
| I HAVE, however found the following entry in my Registry, in TWO locations.
| Perhaps one of these is the problem......
|
| Location 1:
| My Computer\HKEY-CURRENT-USER\Software\Microsoft\Windows\
| Current Verison\Explorer\Doc Find Spec MRU
|
| Location 2:
| My Computer\HKEY-CURRENT-USER\DEFAULTS\Software\Microsoft\Windows\
| Current Verison\Explorer\Doc Find Spec MRU
|
| (Notice that Location 2 has "DEFAULTS" in the path; Loc 1 does not.)
|
| The entries are
|
| NAME Data
| ab (Default) [value not set]
| ab a "*.qbw"
| ab b "wutemp, windowsupdate"
| ab c "?837009.*"
| ab d "*.exe"
| ab e "dox_*.*"
| ab f ""
| ab g "??837009.*"
| ab h "dox-*.*"
| ab i "*.doc, *.xls"
| ab j "wutemp"
| ab MRUList "abjdgcihe"
|
| These are the ONLY places in the registry that '837009' appears.
|
| Any suggestions on how to procede from here? I'm not SUPER comfortable
| mucking about in the Registry, but I'm quite capable at following
| instructions. :O)
|
| MrBill

"David H. Lipman" wrote:

> Maybe because Win98 is a dead product and no longer supported for Security Updates and
> therefore there is NO KB837009 patch for Win98.
>
> Dave
>

IF that is the case, how is it that MicroSoft isn't SMART enough to detect
that I'm running Win98, AND NOT TELL ME OVER AND OVER, DAY AFTER DAY, THAT I
NEED THE STUPID UPDATE?????????????????????????? And then it keeps telling
me that I have SUCCESSFULLY downloaded it. All I'm looking for is some way
to make the flippin' message go away.

Sorry if I seem a bit testy - but due to *REAL WORLD WORKING CONDITIONS* I
am forced, for the current and foreseeable future, to run a platform that
supports DOS. To be slapped in the face when I have a problem certainly
doesn't seem helpful. If you can't be constructive, perhaps you could just
be quiet.

(You wouldn't, by any chance, be a Democrat, would you?)

Worse -- I'm a Republican ;-)

I addition you left a whole bunch of critical information in your post. Only in your reply
do you state you have a cyclical installation, reinstallation problem.

That means it was NOT properly installed in the first place. Perform the update, if
possible, in Safe Mode and make sure *all* programs are closed when you do the update.

Dave




"MrBill" <> wrote in message
news:4C76EBDF-E0E5-453C-AAE1-...
|
|
| "David H. Lipman" wrote:
|
| > Maybe because Win98 is a dead product and no longer supported for Security Updates and
| > therefore there is NO KB837009 patch for Win98.
| >
| > Dave
| >
|
| IF that is the case, how is it that MicroSoft isn't SMART enough to detect
| that I'm running Win98, AND NOT TELL ME OVER AND OVER, DAY AFTER DAY, THAT I
| NEED THE STUPID UPDATE?????????????????????????? And then it keeps telling
| me that I have SUCCESSFULLY downloaded it. All I'm looking for is some way
| to make the flippin' message go away.
|
| Sorry if I seem a bit testy - but due to *REAL WORLD WORKING CONDITIONS* I
| am forced, for the current and foreseeable future, to run a platform that
| supports DOS. To be slapped in the face when I have a problem certainly
| doesn't seem helpful. If you can't be constructive, perhaps you could just
| be quiet.
|
| (You wouldn't, by any chance, be a Democrat, would you?)
|

"David H. Lipman" wrote:

> Worse -- I'm a Republican ;-)
>
> I addition you left a whole bunch of critical information in your post. Only in your reply
> do you state you have a cyclical installation, reinstallation problem.
>
> That means it was NOT properly installed in the first place. Perform the update, if
> possible, in Safe Mode and make sure *all* programs are closed when you do the update.
>

Sorry for my frustration in my earlier response. It's been a VERY long
week.

ANyway - I'll try what you've suggested, and let you know. FWIW, do a
search for "MrBill" in the Windows Update forum to see the string of messages
I've left regarding this issue, and the suggestions I've received before that
haven't worked. Maybe they'll spark an idea for you or someone else for
resolving this issue.

Thanks, and *Go Elephants!*

"David H. Lipman" wrote:

>
> That means it was NOT properly installed in the first place. Perform the update, if
> possible, in Safe Mode and make sure *all* programs are closed when you do the update.
>

== follow-up ==
I attempted the suggested solution, using the update I had downloaded (per
someone's earlier directions) from the Update Catalog.

It returned the error message, "This Update requires Outlook Express 6.0
Service Pack 1 be installed." According to the "About" file, I'm running ver
6.00.2800.1123.

Now what? Thanksagain!

"MrBill" <> wrote in message
news:03210FE8-C250-4C8C-8C81-...
>
>
> "David H. Lipman" wrote:
>
>>
>> That means it was NOT properly installed in the first place. Perform the update, if
>> possible, in Safe Mode and make sure *all* programs are closed when you do the update.
>>
>
> == follow-up ==
> I attempted the suggested solution, using the update I had downloaded (per
> someone's earlier directions) from the Update Catalog.
>
> It returned the error message, "This Update requires Outlook Express 6.0
> Service Pack 1 be installed." According to the "About" file, I'm running ver
> 6.00.2800.1123.
>
> Now what? Thanksagain!


The usual explanation is that you already have the update installed
or one which supersedes it. In order to check what you should do
is find the list of modules and their versions which the update intends
to install. Use that list of module names to check the versions that
you have now. Are they *all* at the right version or greater? If so,
you don't need the update and that would explain why it won't install.
The fact that you can't find it marked as installed in your registry
would explain why you it keeps being reoffered to you. WU does two
tests to determine if an update should be offered: is it in the registry
and are its modules' versions still correct?

<title>MS04-013 : Cumulative Security Update for Outlook Express (837009)</title>


When OE is open its Help, About dialog will show you the versions and
locations of some key OE modules which may be sufficient to do the above
check. Otherwise, provided OE is an open application you could use
msinfo32 to help you check for all version information (version, size, date
and location). Otherwise, check each module separately using File
Properties.

<title>KB184075 - Description of Microsoft System Information (Msinfo32.exe) Tool</title>


Also, have you checked the *.log file the update creates for clues
about what the update has done?

Another consideration is whether or not you had any interfering software
running during the update, especially during the phase when the modules
are copied into the System directory. Anti-virus and other security software
might prevent this final step and this fact often accounts for the sort of
symptom you are seeing.

If you are satisfied that the update is unnecessary somebody could probably
give you the necessary regedit patch to make it look as if it was properly
installed. Alternatively, what you could do is uninstall a superseding update
in order to back out the module versions which may be causing the
confusion and then either install the latest update manually or get
WU to do it for you. FYI 837009 is now not the latest cumulative update
for IE and OE. 823353 is. To see that go to the Security Bulletin Search
and use its "Show bulletins that contain updates that have not been replaced..."
checkbox.

http://www.microsoft.com/technet/security/current.aspx


HTH

Robert Aldwinckle
---

Re KB837009
Has been annoying me for some time. Today found link below and IT WORKED
(Using Windows ME)


http://www.talkaboutsoftware.com/gro...ges/31126.html

"MrBill" wrote:

> Many posts have been sent, and many suggestions have been offered, about the
> NON-installation of the "Critical Update KB837009". Nothing has seemed to
> help, as all of the fixes that are downloadable seem to require I be running
> WinXP - and I'm still on 98se.
>
> I HAVE, however found the following entry in my Registry, in TWO locations.
> Perhaps one of these is the problem......
>
> Location 1:
> My Computer\HKEY-CURRENT-USER\Software\Microsoft\Windows\
> Current Verison\Explorer\Doc Find Spec MRU
>
> Location 2:
> My Computer\HKEY-CURRENT-USER\DEFAULTS\Software\Microsoft\Windows\
> Current Verison\Explorer\Doc Find Spec MRU
>
> (Notice that Location 2 has "DEFAULTS" in the path; Loc 1 does not.)
>
> The entries are
>
> NAME Data
> ab (Default) [value not set]
> ab a "*.qbw"
> ab b "wutemp, windowsupdate"
> ab c "?837009.*"
> ab d "*.exe"
> ab e "dox_*.*"
> ab f ""
> ab g "??837009.*"
> ab h "dox-*.*"
> ab i "*.doc, *.xls"
> ab j "wutemp"
> ab MRUList "abjdgcihe"
>
> These are the ONLY places in the registry that '837009' appears.
>
> Any suggestions on how to procede from here? I'm not SUPER comfortable
> mucking about in the Registry, but I'm quite capable at following
> instructions. :O)
>
> MrBill

"franjon" <> wrote in message
news:2C93A0E6-7864-40CC-9928-...
> Re KB837009
> Has been annoying me for some time. Today found link below and IT WORKED
> (Using Windows ME)
>
>
> http://www.talkaboutsoftware.com/gro...ges/31126.html


"franjon",

Did you find that link in the thread where we are working with Joann?

http://www.microsoft.com/windowsxp/e...0-a05053bf72a7


Did you use the Security Update CD originally too?
Have you been reoffered 887797 yet (e.g since forcing 837009,
assuming that is what you actually did?)

Notice that we suspect that Joann's problem was 887797 plus one
regressed module msident.dll. In that case applying the /N:V idea
of that forum article would be more appropriate with 887797
(at least to fix the second problem). Then if that doesn't stop
837009 from being reoffered I think it would be more appropriate
to uninstall 887797 (and then 823353 and 837009 if necessary)
than doing a forced install of 837009 (which *would* regress both
887797 and 823353).

I think you should check the versions of your modules
(e.g. using the list that I gave to Joann) to see what your
current state is. Unfortunately, there is no version information
given for 887797; otherwise there would have been less
confusion about her case.


Robert Aldwinckle
---