A directory named, e351ac1256f82aa65c632996?

[Guest JW]

I have a few directory on my drives with names like this,

e351ac1256f82aa65c632996. Another is, 48edb3c370aa660ddf. What are these

things? Where do they come from?

 

Each on has a file in it that reads like an event log.

 

For example, one reads:

 

=== Verbose logging started: 12/6/2006 1:09:01 Build type: SHIP UNICODE

3.01.4000.2435 Calling process: C:\WINDOWS\system32\msiexec.exe ===

MSI © (A4:E0) [01:09:01:750]: Resetting cached policy values

MSI © (A4:E0) [01:09:01:750]: Machine policy value 'Debug' is 0

MSI © (A4:E0) [01:09:01:750]: ******* RunEngine:

******* Product: g:\48edb3c370aa660ddf\msxml6.msi

******* Action:

******* CommandLine: **********

MSI © (A4:E0) [01:09:01:750]: Client-side and UI is none or basic: Running

entire install on the server.

MSI © (A4:E0) [01:09:01:750]: Grabbed execution mutex.

MSI © (A4:E0) [01:09:01:765]: Cloaking enabled.

MSI © (A4:E0) [01:09:01:765]: Attempting to enable all disabled priveleges

before calling Install on Server

MSI © (A4:E0) [01:09:01:781]: Incrementing counter to disable shutdown.

Counter after increment: 0

=== Logging started: 12/6/2006 1:09:01 ===

Action start 1:09:01: INSTALL.

Action start 1:09:01: LaunchConditions.

Action ended 1:09:01: LaunchConditions. Return value 1.

Action start 1:09:01: FindRelatedProducts.

Action ended 1:09:01: FindRelatedProducts. Return value 1.

Action start 1:09:01: CA_SetRefCountUpgradeFlag.

....

*************

 

Can I just delete these things? Where do they come from?

 

Thank you.

 

John Wirt

[Guest Holz]

Re: A directory named, e351ac1256f82aa65c632996?

 

On Fri, 29 Feb 2008 20:31:01 -0800

JW <JW@discussions.microsoft.com> wrote:

> I have a few directory on my drives with names like this,

> e351ac1256f82aa65c632996. Another is, 48edb3c370aa660ddf. What are

> these things? Where do they come from

 

Automated updates downloads.

 

--

Live & let live, or leave.

:-)

[Guest PD43]

Re: A directory named, e351ac1256f82aa65c632996?

 

JW <JW@discussions.microsoft.com> wrote:

>I have a few directory on my drives with names like this,

>e351ac1256f82aa65c632996. Another is, 48edb3c370aa660ddf. What are these

>things? Where do they come from?

 

Where did you find them?

[Guest JW]

Re: A directory named, e351ac1256f82aa65c632996?

 

Do you mean Microsoft Automatic Updates, as in downloading and applying XP

patches?

 

Can I delete these directories?

 

THank you.

 

John Wirt

 

"Holz" wrote:

> On Fri, 29 Feb 2008 20:31:01 -0800

> JW <JW@discussions.microsoft.com> wrote:

>

> > I have a few directory on my drives with names like this,

> > e351ac1256f82aa65c632996. Another is, 48edb3c370aa660ddf. What are

> > these things? Where do they come from

>

> Automated updates downloads.

>

> --

> Live & let live, or leave.

> :-)

>

>

[Guest Holz]

Re: A directory named, e351ac1256f82aa65c632996?

 

On Fri, 29 Feb 2008 21:14:00 -0800

JW <JW@discussions.microsoft.com> wrote:

> Do you mean Microsoft Automatic Updates, as in downloading and

> applying XP patches?

 

Yes. This is a log file for the patches left behind after

installation.

>

> Can I delete these directories?

 

Yes

 

--

Live & let live, or leave.

:-)

[Guest John Wirt]

Re: A directory named, e351ac1256f82aa65c632996?

 

Holz wrote:

> On Fri, 29 Feb 2008 21:14:00 -0800

> JW <JW@discussions.microsoft.com> wrote:

>

>> Do you mean Microsoft Automatic Updates, as in downloading and

>> applying XP patches?

>

> Yes. This is a log file for the patches left behind after

> installation.

>> Can I delete these directories?

>

> Yes

>

Thank you.

[Guest John Wirt]

Re: A directory named, e351ac1256f82aa65c632996?

 

Holz wrote:

> On Fri, 29 Feb 2008 21:14:00 -0800

> JW <JW@discussions.microsoft.com> wrote:

>

>> Do you mean Microsoft Automatic Updates, as in downloading and

>> applying XP patches?

>

> Yes. This is a log file for the patches left behind after

> installation.

>> Can I delete these directories?

>

> Yes

>

One of these "directories" is apparently where a .DLL called,

wbemcore.dll, resides. There is a registry repair program on the web

that promises to remove this file.....

 

JOhn Wirt

[Guest Holz]

Re: A directory named, e351ac1256f82aa65c632996?

 

On Sat, 01 Mar 2008 00:50:31 -0500

John Wirt <user@invalid.com> wrote:

> One of these "directories" is apparently where a .DLL called,

> wbemcore.dll, resides. There is a registry repair program on the web

> that promises to remove this file.....

>

> JOhn Wirt

 

Do not install any "cleaner" you are not familiar with. Let your system

be, and report problems back here.

 

--

Live & let live, or leave.

:-)

[Guest John Wirt]

Re: A directory named, e351ac1256f82aa65c632996?

 

Holz wrote:

> On Sat, 01 Mar 2008 00:50:31 -0500

> John Wirt <user@invalid.com> wrote:

>

>> One of these "directories" is apparently where a .DLL called,

>> wbemcore.dll, resides. There is a registry repair program on the web

>> that promises to remove this file.....

>>

>> JOhn Wirt

>

> Do not install any "cleaner" you are not familiar with. Let your system

> be, and report problems back here.

>

The problem is that I cannot delete this directory,

8bf3e4fa68f4d4f48e0085e0.

 

It has a directory under it called, SP2QFE, and in that directory is a

file called, wbemcore.dll.

 

I am unable to delete this file. I get an error message, Cannot delete

wbemcore.dll. It's a .DLL so probably not.

 

Searching on the web, I found a Microsoft Hotfix for this .DLL

(http://support.microsoft.com/?kbid=838884).

 

Apparently, the update that installed it sometimes has a problem.

 

However, I don't have the slowdowns that are cited as the problem. I

would just like to get rid of the update directory.

 

John Wirt

[Guest Holz]

Re: A directory named, e351ac1256f82aa65c632996?

 

On Sat, 01 Mar 2008 02:34:14 -0500

John Wirt <user@invalid.com> wrote:

> The problem is that I cannot delete this directory,

> 8bf3e4fa68f4d4f48e0085e0.

 

Probably because the file is "busy".

Delete all other files in the the directory, restart, and delete the

rest.

 

--

Live & let live, or leave.

:-)