Outlook 2003 Junk Mail Filter Update Fails

On one PC only.
The update, KB931764, status is downloaded, but several install attempts all
fail. As this update was not a problem on several other PC's, I think I need
to locate the download on my local hard drive, then restart the update
process from the beginning.

How do I locate the download and get rid of it?

Thanks in advance!

"pvdg42" <> wrote in message
news:...
> On one PC only.
> The update, KB931764, status is downloaded, but several install attempts
> all fail. As this update was not a problem on several other PC's, I think
> I need to locate the download on my local hard drive, then restart the
> update process from the beginning.
>
> How do I locate the download and get rid of it?
>
> Thanks in advance!
>
>
Update on this issue:

Update history shows Error Code 0x52F for each failed install.

I've attempted to find and delete all files associated with KB931764 from my
local drive (yes, I set the search to include hidden and system files), and
searched for and removed all registry keys associated with KB931764 from the
registry. After doing that, I attempted to manually download and install the
patch. The install failed with the message: "Error Invalid Drive M:\". There
is no M: drive on the problem PC, and never has been.

After all this, Windows Update still insists the patch has already been
downloaded and tries, unsuccessfully, to install it. I'm assuming it finds
an indication that the file "office2003-KB931764-FullFile-ENU.exe" is on my
local drive? Where would it be?

"pvdg42" <> wrote in message
news:uHfPNL%...
>
> "pvdg42" <> wrote in message news:...
>> On one PC only.
>> The update, KB931764, status is downloaded, but several install attempts all fail. As this update was not a problem on several
>> other PC's, I think I need to locate the download on my local hard drive, then restart the update process from the beginning.
>>
>> How do I locate the download and get rid of it?
>>
>> Thanks in advance!
>>
>>
> Update on this issue:
>
> Update history shows Error Code 0x52F for each failed install.
>
> I've attempted to find and delete all files associated with KB931764 from my local drive (yes, I set the search to include hidden
> and system files), and searched for and removed all registry keys associated with KB931764 from the registry. After doing that, I
> attempted to manually download and install the patch. The install failed with the message: "Error Invalid Drive M:\". There is no
> M: drive on the problem PC, and never has been.


How was the product originally installed? Perhaps it came from a machine
which did have such a drive letter, e.g. a network drive?


>
> After all this, Windows Update still insists the patch has already been downloaded and tries, unsuccessfully, to install it. I'm
> assuming it finds an indication that the file "office2003-KB931764-FullFile-ENU.exe" is on my local drive?


Not necessarily. If it's a file in a temporary directory it could go wherever
the installer thinks there is the most room. Unfortunately, sometimes it
doesn't consider whether the user has the necessary permissions to make
use of such a choice.


> Where would it be?


What does the log say? If there aren't enough clues that way
try installing it manually using a /verbose command-line switch
or Run... ProcMon to supplement whatever the default log shows.


HTH

Robert Aldwinckle
---

"Robert Aldwinckle" <> wrote in message
news:...
>
> How was the product originally installed? Perhaps it came from a machine
> which did have such a drive letter, e.g. a network drive?
>
From distribution media. The PC is not part of a domain. It's one of my home
PC's and just part of my workgroup.
>
> Not necessarily. If it's a file in a temporary directory it could go
> wherever
> the installer thinks there is the most room. Unfortunately, sometimes it
> doesn't consider whether the user has the necessary permissions to make
> use of such a choice.

Per the above, the PC's local drives would be the only possible place, or am
I making an invalid assumption with no network drives?
>
>
> What does the log say? If there aren't enough clues that way
> try installing it manually using a /verbose command-line switch
> or Run... ProcMon to supplement whatever the default log shows.
>
According to the message received when I try to use /verbose, that is not a
supported option of the patch installer.

Where would the log be? Searches for anything with "931764" don't reveal a
log.

>
> HTH
>
> Robert Aldwinckle

I very much appreciate your effort to help. For now, I've just removed it
from my patch list, so WU won't keep bugging me about it.

> ---
>
>

(cross-post added to Office Update)
"pvdg42" <> wrote in message
news:...
>
> "Robert Aldwinckle" <> wrote in message
> news:...

>>
>> What does the log say? If there aren't enough clues that way
>> try installing it manually using a /verbose command-line switch
>> or Run... ProcMon to supplement whatever the default log shows.
>>
> According to the message received when I try to use /verbose,
> that is not a supported option of the patch installer.


I don't have the update and didn't stop to check the details.
If the update is an msi package there is a different syntax.
From the link in the update's KB article:

http://office.microsoft.com/en-us/or...402381033.aspx

<quote>
msiexec.exe /p [path\name of update MSP file]/a [path\name of MSI file] /qb /lv* [path\name of log file]
</quote>

Generally if you don't have a command-line syntax documented most packages
will give you some clues if you add a /help or /? switch to them.
Unfortunately though sometimes diagnostic options are omitted then
even when they are available.


>
> Where would the log be? Searches for anything with "931764" don't reveal a
> log.


Various update technologies use their own peculiar procedures when creating
diagnostics. I usually use a Windows Explorer search for all files changed
during the interval that the update was running (e.g. all files changed
on a particular day and then sorted by Date Modified) in order to make sure
that I am aware of all possible diagnostics it created. Another newer alternative
is running ProcMon and looking at what it captures.

Cross-posting to Office Update in case someone who actually has installed
the update can explain what diagnostics are available.


HTH

Robert
---

1st Rename Office subkeys


Note: Removing the following registry keys may reset customized user
settings for your Microsoft Office programs.


1. Close all the applications.
2. Click on Start->Run, type in REGEDIT and click on OK.
3. Locate and select the following registry subkeys:


HKEY_CURRENT_USER\Software\Microsoft\Office\11.0
HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0


4. Right click on 11.0 and rename them to Old11.
5. Close the Registry Editor.


2nd. Detect and Repair Office 2003


1. On the Windows taskbar, click Start, point to and click Control Panel.
2. Double-click Add/Remove Programs.
3. Click Change/Remove Programs on the left pane.
4. Highlight Microsoft Office Professional Edition 2003 on the right pane
and click Change.
5. Insert the correct version of CD when it requires.
6. Select "Reinstall and Repair" and click Next.
7. Select "Detect and Repair errors in my Office installation".
8. Click Install and wait the process to end.


3rd. Install the Updates




--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Robert Aldwinckle" <> wrote in message news:...
> (cross-post added to Office Update)
> "pvdg42" <> wrote in message
> news:...
>>
>> "Robert Aldwinckle" <> wrote in message
>> news:...
>
>>>
>>> What does the log say? If there aren't enough clues that way
>>> try installing it manually using a /verbose command-line switch
>>> or Run... ProcMon to supplement whatever the default log shows.
>>>
>> According to the message received when I try to use /verbose,
>> that is not a supported option of the patch installer.
>
>
> I don't have the update and didn't stop to check the details.
> If the update is an msi package there is a different syntax.
> From the link in the update's KB article:
>
> http://office.microsoft.com/en-us/or...402381033.aspx
>
> <quote>
> msiexec.exe /p [path\name of update MSP file]/a [path\name of MSI file] /qb /lv* [path\name of log file]
> </quote>
>
> Generally if you don't have a command-line syntax documented most packages
> will give you some clues if you add a /help or /? switch to them.
> Unfortunately though sometimes diagnostic options are omitted then
> even when they are available.
>
>
>>
>> Where would the log be? Searches for anything with "931764" don't reveal a
>> log.
>
>
> Various update technologies use their own peculiar procedures when creating
> diagnostics. I usually use a Windows Explorer search for all files changed
> during the interval that the update was running (e.g. all files changed
> on a particular day and then sorted by Date Modified) in order to make sure
> that I am aware of all possible diagnostics it created. Another newer alternative
> is running ProcMon and looking at what it captures.
>
> Cross-posting to Office Update in case someone who actually has installed
> the update can explain what diagnostics are available.
>
>
> HTH
>
> Robert
> ---
>
>

Solution !!! I just solved this same problem on my computer. I didn't see
the "Invalid Drive" message until I tried to dl the update and install
locally rather than from the automatic update tool. My problem must have
been due to the fact that I recently reassigned a drive letter on an
auxillary (2nd) hard-drive. MS Office 2003 creates a cache folder called
MSOCache and puts it on the local drive with the most space available, which
for me was the auxillary drive I had added to manage my video files. The
cache folder contains the "Local Installation Source", which was no longer
available for the update to work. Here's what I did:

See: http://support.microsoft.com/default...b;en-us;873301 for info.
Download ListTool at
http://www.microsoft.com/downloads/d...5-b812ba0fed3e
Run the tool and move the LIS to a valid drive.


"pvdg42" wrote:

>
> "pvdg42" <> wrote in message
> news:...
> > On one PC only.
> > The update, KB931764, status is downloaded, but several install attempts
> > all fail. As this update was not a problem on several other PC's, I think
> > I need to locate the download on my local hard drive, then restart the
> > update process from the beginning.
> >
> > How do I locate the download and get rid of it?
> >
> > Thanks in advance!
> >
> >
> Update on this issue:
>
> Update history shows Error Code 0x52F for each failed install.
>
> I've attempted to find and delete all files associated with KB931764 from my
> local drive (yes, I set the search to include hidden and system files), and
> searched for and removed all registry keys associated with KB931764 from the
> registry. After doing that, I attempted to manually download and install the
> patch. The install failed with the message: "Error Invalid Drive M:\". There
> is no M: drive on the problem PC, and never has been.
>
> After all this, Windows Update still insists the patch has already been
> downloaded and tries, unsuccessfully, to install it. I'm assuming it finds
> an indication that the file "office2003-KB931764-FullFile-ENU.exe" is on my
> local drive? Where would it be?
>
>
>
Solution !!! I just solved this same problem on my computer (after many
hours of troubleshooting). I didn't see the "Invalid Drive" message until I
tried to dl the update and install locally rather than from the automatic
update tool. My problem must have been due to the fact that I recently
reassigned a drive letter on an auxillary (2nd) hard-drive. MS Office 2003
creates a cache folder called MSOCache and puts it on the local drive with
the most space available, which for me was the auxillary drive I had added to
manage my video files. The cache folder contains the "Local Installation
Source", which was no longer available for the update to work. Here's what I
did:

See: http://support.microsoft.com/default...b;en-us;873301 for info.

Download ListTool at
http://www.microsoft.com/downloads/d...5-b812ba0fed3e

Run the tool and move the LIS to a valid drive.

Re-run the update (I ran the version I downloaded locally).
That worked!

Hope this helps. Write back if it works so others will follow.

"Robert Aldwinckle" <> wrote in message
news:...
> (cross-post added to Office Update)
<snip>
> Cross-posting to Office Update in case someone who actually has
> installed
> the update can explain what diagnostics are available.
>
>
> HTH
>
> Robert
> ---
>
Yes! Thank you very much for crossposting. Peter's solution worked like a
charm.

"Peter Foldes" <> wrote in message
news:...

1st Rename Office subkeys


Note: Removing the following registry keys may reset customized user
settings for your Microsoft Office programs.


1. Close all the applications.
2. Click on Start->Run, type in REGEDIT and click on OK.
3. Locate and select the following registry subkeys:


HKEY_CURRENT_USER\Software\Microsoft\Office\11.0
HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0


4. Right click on 11.0 and rename them to Old11.
5. Close the Registry Editor.


2nd. Detect and Repair Office 2003


1. On the Windows taskbar, click Start, point to and click Control Panel.
2. Double-click Add/Remove Programs.
3. Click Change/Remove Programs on the left pane.
4. Highlight Microsoft Office Professional Edition 2003 on the right pane
and click Change.
5. Insert the correct version of CD when it requires.
6. Select "Reinstall and Repair" and click Next.
7. Select "Detect and Repair errors in my Office installation".
8. Click Install and wait the process to end.


3rd. Install the Updates

Thanks very much, Peter! It did the job for me.

YW. Thanks for posting back and letting us know

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"pvdg42" <> wrote in message news:%...
>
> "Robert Aldwinckle" <> wrote in message
> news:...
>> (cross-post added to Office Update)
> <snip>
>> Cross-posting to Office Update in case someone who actually has
>> installed
>> the update can explain what diagnostics are available.
>>
>>
>> HTH
>>
>> Robert
>> ---
>>
> Yes! Thank you very much for crossposting. Peter's solution worked like a
> charm.
>
>