Strange directory and Registry entries

  • Thread starter Thread starter Bob S
  • Start date Start date
B

Bob S

I know this is a Win 2000 Registry newsgroup. I could not find a WinXP group
that specialized in the Registry. Can someone here either help me or tell me
where to find a similar XP group?

I recently upgraded my laptop from Win98 to WinXP Pro (with SP1) and have

now added all of the updates. But before any of the updates (except SP1) I

saw a strange directory show up on my HD. I have a normal temp directory
which

is c:\Documents and Settings\Dr. Bob Singleton\Local Settings\Temp. This

directory exists and has had plenty written to it.

The strange temp directory is c:\Documents and
Settings\DRF015~1~BOB\LOCALS~1\Temp.
All levels of this directory are empty and stay that way. When I delete it,
it comes back after a while. I have not determined exactly what brings it
back.
To try to determine this, I searched for the string in my Registry.
I find C:\Documents and Settings\DRF015~1~BOB\LOCALS~1\Temp in my Registry
in 10 places:

HKEY_Classes_Root\Installer\Products\CF05CF94569F9D04984BBCFF08490133\Source
List\Last used Source

HKEY_Classes_Root\Installer\Products\CF05CF94569F9D04984BBCFF08490133\Source
List\Net\1

HKEY_Local_Machine\Software\Classes\Installer\Products\CF05CF94569F9D04984BB
CFF08490133\SourceList\Last used Source

HKEY_Local_Machine\Software\Classes\Installer\Products\CF05CF94569F9D04984BB
CFF08490133\SourceList\Net\1


HKEY_Local_Machine\SOFTWARE\Microsoft\Advanced INS
Setup\ieupdate\InstallINFFile


HKEY_Local_Machine\SOFTWARE\Microsoft\Advanced INS
Setup\oeupdate\InstallINFFile

HKEY_Local_Machine\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserD
ata

\S-1-5-18\Products\CF05CF94569F9D04984BBCFF08490133\InstallProperties\Instal
lSource

HKEY_Local_Machine\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{49FC
50FC-F965-40D9-89B4-CBFF80941033}\InstallSource

HKEY_Local_Machine\SOFTWARE\Microsoft\Windows\Installer\UserData\S-1-5-18\Pr
oducts

\CF05CF94569F9D04984BBCFF08490133\InstallProperties\InstallSource

HKEY_Local_Machine\SOFTWARE\Microsoft\Windows\Uninstall\{49FC50FC-F965-40D9-
89B4-CBFF80941033}\InstallSource.Can someone tell me where this directory
came from and how to get rid of it? Thank you.
 
I know this is a Win 2000 Registry newsgroup. I could not find a WinXP group
that specialized in the Registry. Can someone here either help me or tell me
where to find a similar XP group?

I recently upgraded my laptop from Win98 to WinXP Pro (with SP1) and have

now added all of the updates. But before any of the updates (except SP1) I

saw a strange directory show up on my HD. I have a normal temp directory
which

is c:\Documents and Settings\Dr. Bob Singleton\Local Settings\Temp. This

directory exists and has had plenty written to it.

The strange temp directory is c:\Documents and
Settings\DRF015~1~BOB\LOCALS~1\Temp.
All levels of this directory are empty and stay that way. When I delete it,
it comes back after a while. I have not determined exactly what brings it
back.
To try to determine this, I searched for the string in my Registry.
I find C:\Documents and Settings\DRF015~1~BOB\LOCALS~1\Temp in my Registry
in 10 places:

HKEY_Classes_Root\Installer\Products\CF05CF94569F9D04984BBCFF08490133\Source
List\Last used Source

HKEY_Classes_Root\Installer\Products\CF05CF94569F9D04984BBCFF08490133\Source
List\Net\1

HKEY_Local_Machine\Software\Classes\Installer\Products\CF05CF94569F9D04984BB
CFF08490133\SourceList\Last used Source

HKEY_Local_Machine\Software\Classes\Installer\Products\CF05CF94569F9D04984BB
CFF08490133\SourceList\Net\1


HKEY_Local_Machine\SOFTWARE\Microsoft\Advanced INS
Setup\ieupdate\InstallINFFile


HKEY_Local_Machine\SOFTWARE\Microsoft\Advanced INS
Setup\oeupdate\InstallINFFile

HKEY_Local_Machine\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserD
ata

\S-1-5-18\Products\CF05CF94569F9D04984BBCFF08490133\InstallProperties\Instal
lSource

HKEY_Local_Machine\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{49FC
50FC-F965-40D9-89B4-CBFF80941033}\InstallSource

HKEY_Local_Machine\SOFTWARE\Microsoft\Windows\Installer\UserData\S-1-5-18\Pr
oducts

\CF05CF94569F9D04984BBCFF08490133\InstallProperties\InstallSource

HKEY_Local_Machine\SOFTWARE\Microsoft\Windows\Uninstall\{49FC50FC-F965-40D9-
89B4-CBFF80941033}\InstallSource.Can someone tell me where this directory
came from and how to get rid of it? Thank you.
Click to expand...

These are leftovers from Windows 98 and possibly 16 bit applications
or 32 bit apps that defaulted to 8.3 naming convention.

Personally, I would recommend installing an OS fresh whenever
possible. Upgrades always leave "compatibility" remnants behind and
can become a hassle in the long term that outweigh the inconvenience
of a clean install.

If starting over with a fresh install is out of the question, you can
ignore the funky directory or uninstall whatever is associated with
the CLSIDs you found in the registry.

Warren
 
I know this is a Win 2000 Registry newsgroup. I could not find a WinXP group
that specialized in the Registry. Can someone here either help me or tell me
where to find a similar XP group?

I recently upgraded my laptop from Win98 to WinXP Pro (with SP1) and have

now added all of the updates. But before any of the updates (except SP1) I

saw a strange directory show up on my HD. I have a normal temp directory
which

is c:\Documents and Settings\Dr. Bob Singleton\Local Settings\Temp. This

directory exists and has had plenty written to it.

The strange temp directory is c:\Documents and
Settings\DRF015~1~BOB\LOCALS~1\Temp.
All levels of this directory are empty and stay that way. When I delete it,
it comes back after a while. I have not determined exactly what brings it
back.
To try to determine this, I searched for the string in my Registry.
I find C:\Documents and Settings\DRF015~1~BOB\LOCALS~1\Temp in my Registry
in 10 places:

HKEY_Classes_Root\Installer\Products\CF05CF94569F9D04984BBCFF08490133\Source
List\Last used Source

HKEY_Classes_Root\Installer\Products\CF05CF94569F9D04984BBCFF08490133\Source
List\Net\1

HKEY_Local_Machine\Software\Classes\Installer\Products\CF05CF94569F9D04984BB
CFF08490133\SourceList\Last used Source

HKEY_Local_Machine\Software\Classes\Installer\Products\CF05CF94569F9D04984BB
CFF08490133\SourceList\Net\1


HKEY_Local_Machine\SOFTWARE\Microsoft\Advanced INS
Setup\ieupdate\InstallINFFile


HKEY_Local_Machine\SOFTWARE\Microsoft\Advanced INS
Setup\oeupdate\InstallINFFile

HKEY_Local_Machine\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserD
ata

\S-1-5-18\Products\CF05CF94569F9D04984BBCFF08490133\InstallProperties\Instal
lSource

HKEY_Local_Machine\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{49FC
50FC-F965-40D9-89B4-CBFF80941033}\InstallSource

HKEY_Local_Machine\SOFTWARE\Microsoft\Windows\Installer\UserData\S-1-5-18\Pr
oducts

\CF05CF94569F9D04984BBCFF08490133\InstallProperties\InstallSource

HKEY_Local_Machine\SOFTWARE\Microsoft\Windows\Uninstall\{49FC50FC-F965-40D9-
89B4-CBFF80941033}\InstallSource.Can someone tell me where this directory
came from and how to get rid of it? Thank you.
Click to expand...

These are leftovers from Windows 98 and possibly 16 bit applications
or 32 bit apps that defaulted to 8.3 naming convention.

Personally, I would recommend installing an OS fresh whenever
possible. Upgrades always leave "compatibility" remnants behind and
can become a hassle in the long term that outweigh the inconvenience
of a clean install.

If starting over with a fresh install is out of the question, you can
ignore the funky directory or uninstall whatever is associated with
the CLSIDs you found in the registry.

Warren
 
Warren Young said:
e
B
B
-

These are leftovers from Windows 98 and possibly 16 bit applications
or 32 bit apps that defaulted to 8.3 naming convention.

Personally, I would recommend installing an OS fresh whenever
possible. Upgrades always leave "compatibility" remnants behind and
can become a hassle in the long term that outweigh the inconvenience
of a clean install.

If starting over with a fresh install is out of the question, you can
ignore the funky directory or uninstall whatever is associated with
the CLSIDs you found in the registry.

Warren
Click to expand...

Thank you Warren. Could you help me a bit more. As I analyze the 10
entries in the Registry (which I listed above), it seems that all 10 relate
either to:

installer + CF05CF94569F9D04984BBCFF08490133
or
uninstaller + {49FC50FC-F965-40D9-89B4-CBFF80941033}
or
oeupdate
or
ieupdate

Question: Could you tell from this what exactly I should install?

Thanks a bunch.
Bob
 
Warren Young said:
e
B
B
-

These are leftovers from Windows 98 and possibly 16 bit applications
or 32 bit apps that defaulted to 8.3 naming convention.

Personally, I would recommend installing an OS fresh whenever
possible. Upgrades always leave "compatibility" remnants behind and
can become a hassle in the long term that outweigh the inconvenience
of a clean install.

If starting over with a fresh install is out of the question, you can
ignore the funky directory or uninstall whatever is associated with
the CLSIDs you found in the registry.

Warren
Click to expand...

Thank you Warren. Could you help me a bit more. As I analyze the 10
entries in the Registry (which I listed above), it seems that all 10 relate
either to:

installer + CF05CF94569F9D04984BBCFF08490133
or
uninstaller + {49FC50FC-F965-40D9-89B4-CBFF80941033}
or
oeupdate
or
ieupdate

Question: Could you tell from this what exactly I should install?

Thanks a bunch.
Bob
 
Thank you Warren. Could you help me a bit more. As I analyze the 10
entries in the Registry (which I listed above), it seems that all 10 relate
either to:

installer + CF05CF94569F9D04984BBCFF08490133
or
uninstaller + {49FC50FC-F965-40D9-89B4-CBFF80941033}
or
oeupdate
or
ieupdate

Question: Could you tell from this what exactly I should install?

Thanks a bunch.
Bob
Click to expand...

Bob,

Unfortunately I don't know what those CLSIDs refer to. However,
oeupdate refers to Outlook Express update and ieupdate refers to
Internet Explorer update. Perhaps a DWORD value in the registry keys
mentioned gives a clue

Since these registry entries all refer to install or uninstall
locations, it is unlikely they are recreating the errant folder. The
most likely offender is an application that writes scratch files has a
setting to use that directory and creates it if it is missing. Maybe
an ini file?

I don't have a Windows 98 machine to refer back to that would lend a
clue either or one that has been upgraded to XP from 98 to see how the
upgrade differs from a fresh install.

Wish I could provide a definitive answer as to the cause.

Warren
 
Thank you Warren. Could you help me a bit more. As I analyze the 10
entries in the Registry (which I listed above), it seems that all 10 relate
either to:

installer + CF05CF94569F9D04984BBCFF08490133
or
uninstaller + {49FC50FC-F965-40D9-89B4-CBFF80941033}
or
oeupdate
or
ieupdate

Question: Could you tell from this what exactly I should install?

Thanks a bunch.
Bob
Click to expand...

Bob,

Unfortunately I don't know what those CLSIDs refer to. However,
oeupdate refers to Outlook Express update and ieupdate refers to
Internet Explorer update. Perhaps a DWORD value in the registry keys
mentioned gives a clue

Since these registry entries all refer to install or uninstall
locations, it is unlikely they are recreating the errant folder. The
most likely offender is an application that writes scratch files has a
setting to use that directory and creates it if it is missing. Maybe
an ini file?

I don't have a Windows 98 machine to refer back to that would lend a
clue either or one that has been upgraded to XP from 98 to see how the
upgrade differs from a fresh install.

Wish I could provide a definitive answer as to the cause.

Warren
 
Warren Young said:
Bob,

Unfortunately I don't know what those CLSIDs refer to. However,
oeupdate refers to Outlook Express update and ieupdate refers to
Internet Explorer update. Perhaps a DWORD value in the registry keys
mentioned gives a clue

Since these registry entries all refer to install or uninstall
locations, it is unlikely they are recreating the errant folder. The
most likely offender is an application that writes scratch files has a
setting to use that directory and creates it if it is missing. Maybe
an ini file?

I don't have a Windows 98 machine to refer back to that would lend a
clue either or one that has been upgraded to XP from 98 to see how the
upgrade differs from a fresh install.

Wish I could provide a definitive answer as to the cause.

Warren
Click to expand...

Warren,
Thanks. I checked the DWORD values and found 2 things. Several places it
mentioned MS MovieMaker 2.0. Also, I noticed in one location it had
C:\Documents and Settings\DRF015~1~BOB\LOCALS~1\Temp\ixp000.tmp\Q824145.inf
rather than just
C:\Documents and Settings\DRF015~1~BOB\LOCALS~1\Temp

In light of that and your mentioning that I might need to uninstall an
offending program, I looked in my Add/Remove programs list and found
IEUpdate Q824145. Then I looked at another machine which had XP Pro on it
with almost all of the updates installed and I did NOT find Q824145 listed
in the Add/Remove Programs. So then I checked the updates waiting to be
installed on my other machine, and Q824145 was NOT included there either.

Is Q824145 likely the culprit?

Bob
 
Warren Young said:
Bob,

Unfortunately I don't know what those CLSIDs refer to. However,
oeupdate refers to Outlook Express update and ieupdate refers to
Internet Explorer update. Perhaps a DWORD value in the registry keys
mentioned gives a clue

Since these registry entries all refer to install or uninstall
locations, it is unlikely they are recreating the errant folder. The
most likely offender is an application that writes scratch files has a
setting to use that directory and creates it if it is missing. Maybe
an ini file?

I don't have a Windows 98 machine to refer back to that would lend a
clue either or one that has been upgraded to XP from 98 to see how the
upgrade differs from a fresh install.

Wish I could provide a definitive answer as to the cause.

Warren
Click to expand...

Warren,
Thanks. I checked the DWORD values and found 2 things. Several places it
mentioned MS MovieMaker 2.0. Also, I noticed in one location it had
C:\Documents and Settings\DRF015~1~BOB\LOCALS~1\Temp\ixp000.tmp\Q824145.inf
rather than just
C:\Documents and Settings\DRF015~1~BOB\LOCALS~1\Temp

In light of that and your mentioning that I might need to uninstall an
offending program, I looked in my Add/Remove programs list and found
IEUpdate Q824145. Then I looked at another machine which had XP Pro on it
with almost all of the updates installed and I did NOT find Q824145 listed
in the Add/Remove Programs. So then I checked the updates waiting to be
installed on my other machine, and Q824145 was NOT included there either.

Is Q824145 likely the culprit?

Bob
 
Warren,
Thanks. I checked the DWORD values and found 2 things. Several places it
mentioned MS MovieMaker 2.0. Also, I noticed in one location it had
C:\Documents and Settings\DRF015~1~BOB\LOCALS~1\Temp\ixp000.tmp\Q824145.inf
rather than just
C:\Documents and Settings\DRF015~1~BOB\LOCALS~1\Temp

In light of that and your mentioning that I might need to uninstall an
offending program, I looked in my Add/Remove programs list and found
IEUpdate Q824145. Then I looked at another machine which had XP Pro on it
with almost all of the updates installed and I did NOT find Q824145 listed
in the Add/Remove Programs. So then I checked the updates waiting to be
installed on my other machine, and Q824145 was NOT included there either.

Is Q824145 likely the culprit?

Bob
Click to expand...

No, Q824145 is the November cumulative security update for IE.

The truncated folder structure is left over from Windows 98 and has
been inherited by XP. It may be so ingrained that removing it isn't an
easy option. Since the directory isn't causing any actual harm, you
are probably better off leaving it.

Since the perpetrator(s) that are recreating it are elusive, the
result of picking the wrong thing out of the registry may end with
more trouble than the empty folder is worth.

Even an uninstall/reinstall has no guarantees if the install routine
finds that it is supposed to still use the truncated folder structure
based upon something left behind in the registry.

Honestly, at this point, if you don't want to install XP fresh, I
would let it be as hacking away at it may lead to an unstable system
that could result in a fresh install being required anyway to correct.

Warren
 
Warren,
Thanks. I checked the DWORD values and found 2 things. Several places it
mentioned MS MovieMaker 2.0. Also, I noticed in one location it had
C:\Documents and Settings\DRF015~1~BOB\LOCALS~1\Temp\ixp000.tmp\Q824145.inf
rather than just
C:\Documents and Settings\DRF015~1~BOB\LOCALS~1\Temp

In light of that and your mentioning that I might need to uninstall an
offending program, I looked in my Add/Remove programs list and found
IEUpdate Q824145. Then I looked at another machine which had XP Pro on it
with almost all of the updates installed and I did NOT find Q824145 listed
in the Add/Remove Programs. So then I checked the updates waiting to be
installed on my other machine, and Q824145 was NOT included there either.

Is Q824145 likely the culprit?

Bob
Click to expand...

No, Q824145 is the November cumulative security update for IE.

The truncated folder structure is left over from Windows 98 and has
been inherited by XP. It may be so ingrained that removing it isn't an
easy option. Since the directory isn't causing any actual harm, you
are probably better off leaving it.

Since the perpetrator(s) that are recreating it are elusive, the
result of picking the wrong thing out of the registry may end with
more trouble than the empty folder is worth.

Even an uninstall/reinstall has no guarantees if the install routine
finds that it is supposed to still use the truncated folder structure
based upon something left behind in the registry.

Honestly, at this point, if you don't want to install XP fresh, I
would let it be as hacking away at it may lead to an unstable system
that could result in a fresh install being required anyway to correct.

Warren
 
Warren Young said:
No, Q824145 is the November cumulative security update for IE.

The truncated folder structure is left over from Windows 98 and has
been inherited by XP. It may be so ingrained that removing it isn't an
easy option. Since the directory isn't causing any actual harm, you
are probably better off leaving it.

Since the perpetrator(s) that are recreating it are elusive, the
result of picking the wrong thing out of the registry may end with
more trouble than the empty folder is worth.

Even an uninstall/reinstall has no guarantees if the install routine
finds that it is supposed to still use the truncated folder structure
based upon something left behind in the registry.

Honestly, at this point, if you don't want to install XP fresh, I
would let it be as hacking away at it may lead to an unstable system
that could result in a fresh install being required anyway to correct.

Warren
Click to expand...

Thanks Warren. That was very clear and wise. Much abliged.
Bob
 
Warren Young said:
No, Q824145 is the November cumulative security update for IE.

The truncated folder structure is left over from Windows 98 and has
been inherited by XP. It may be so ingrained that removing it isn't an
easy option. Since the directory isn't causing any actual harm, you
are probably better off leaving it.

Since the perpetrator(s) that are recreating it are elusive, the
result of picking the wrong thing out of the registry may end with
more trouble than the empty folder is worth.

Even an uninstall/reinstall has no guarantees if the install routine
finds that it is supposed to still use the truncated folder structure
based upon something left behind in the registry.

Honestly, at this point, if you don't want to install XP fresh, I
would let it be as hacking away at it may lead to an unstable system
that could result in a fresh install being required anyway to correct.

Warren
Click to expand...

Thanks Warren. That was very clear and wise. Much abliged.
Bob
 
Back
Top