Re: [Full-disclosure] Patch tuesday debris

This happens sometimes. The (MSI3) installer doesn't clean up the
temporary folder. The syntax is something similar:



msxml4-KB927978-enu /q REBOOT=ReallySuppress /l*v c:\KB927978.log



Where the last part is the path to the log file





________________________________

From: full-disclosure-bounces@xxxxxxxxxxxxxxxxx
[mailto:full-disclosure-bounces@xxxxxxxxxxxxxxxxx] On Behalf Of ASB
Sent: Monday, November 20, 2006 1:08 PM
To: Aaron Howell
Cc: full-disclosure@xxxxxxxxxxxxxxxxx
Subject: Re: [Full-disclosure] Patch tuesday debris



Yes, there seems to have been some debris left from this one. (Based
on a look at 5 systems)



No errors to speak of.



-ASB



On 11/20/06, Aaron Howell <aaron_howell@xxxxxxxxxxxxxxx> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dave "No, not that one" Korn wrote:
Last tuesday's updates (which I deferred installing until yesterday)
left
a folder on my HD, called "C:\c0772dab3463959f7c", containing a log
file,
msxml6-KB927977-enu-x86.log, which contains install logging details
for the
msxml patch.

My folder is named c:\6ad0c137abd5117c8e8326 , and my file is named
msxml4-KB927978-enu.log

Did everyone get this (or perhaps a similarly-named folder with a
different hex number)? If absolutely everyone ended up with this it's
probably just M$ being careless, but if not it might mean something
failed
during install and that's why it didn't clean up properly.

I just checked 2 random machines at the office, and they both have
similar directories with the same log file. My assumption would be that
it's just sloppy installation leaving files rolling around...

cheers,
DaveK

aaron


This e-mail message is confidential and intended solely for the person to whom or the entity to which it is addressed. All the contents and any attachments remain the property of VR Services (Pty) Ltd unless so stated by contract.
If you are not the intended recipient, you are prohibited from reading, copying, using or disclosing this message to others.
If you received this message in error, please notify the sender immediately by replying to this e-mail or by telephoning +27 21 528 9300 and thereafter delete the message. VR Services (Pty) Ltd does not accept liability for any personal views expressed in this message.
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/

Relevant Pages

  • RE: Product Key for Office XP
    ... Use an Office XP Setup Log File to Troubleshoot Setup Problems in ... How to Create a Log File ... Windows Installer Log Files ...
    (microsoft.public.office.setup)
  • Re: Cannot install Office 2007 SP2 upgrade
    ... Download the 290+ Mbyte Office 2007 SP2 patch again and try to apply it. ... I just tried to post the log file, but I couldn't -- Thunderbird reported that the post is too large. ... Vista SP1/SP2 and Windows 7 already contain the correct version of Windows Installer. ...
    (microsoft.public.officeupdate)
  • Re: KB898461 consistently fails to install
    ... Programs, Windows Installer 3.1, reboot, repeat), I was able to ... because they also appear in the successful log file: ...
    (microsoft.public.windowsupdate)
  • Re: KB898461 consistently fails to install
    ... Programs, Windows Installer 3.1, reboot, repeat), I was able to ... because they also appear in the successful log file: ...
    (microsoft.public.windowsupdate)
  • Re: Office 2000 SP3 Install Failure
    ... CDROM file to a temporary folder on the machine? ... SP3 update process is getting to the point where Windows Installer ... for a temporary location to extract files to. ...
    (microsoft.public.officeupdate)