<div>Yes, there seems to have been some debris left from this one. (Based on a look at 5 systems)</div>
<div> </div>
<div>No errors to speak of.</div>
<div> </div>
<div>-ASB<br><br> </div>
<div><span class="gmail_quote">On 11/20/06, <b class="gmail_sendername">Aaron Howell</b> <<a href="mailto:aaron_howell@ngenuity-is.com">aaron_howell@ngenuity-is.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">-----BEGIN PGP SIGNED MESSAGE-----<br>Hash: SHA1<br><br>Dave "No, not that one" Korn wrote:<br>> Last tuesday's updates (which I deferred installing until yesterday) left
<br>> a folder on my HD, called "C:\c0772dab3463959f7c", containing a log file,<br>> msxml6-KB927977-enu-x86.log, which contains install logging details for the<br>> msxml patch.<br><br>My folder is named c:\6ad0c137abd5117c8e8326 , and my file is named
<br>msxml4-KB927978-enu.log<br><br>> Did everyone get this (or perhaps a similarly-named folder with a<br>> different hex number)? If absolutely everyone ended up with this it's<br>> probably just M$ being careless, but if not it might mean something failed
<br>> during install and that's why it didn't clean up properly.<br><br>I just checked 2 random machines at the office, and they both have<br>similar directories with the same log file. My assumption would be that<br>it's just sloppy installation leaving files rolling around...
<br><br>> cheers,<br>> DaveK<br><br>aaron<br></blockquote></div>