Re: Explorer Directory Cache Corrupted - Fixes?

"Sharon F" wrote:

> On Sun, 4 Sep 2005 10:32:01 -0700, Leland Bruns wrote:
> > ...
> Thanks for the added info Leland. In the case of music folders you have
> Windows and your default media player poking fingers at it. Windows will
> follow your customizations (folder properties> Customize> Change Picture).
> However a media player can be configured to update album info (and album
> photo pics) from the internet.
>
> Try disabling the customizing features in your media player. If you use
> multiple players, you should repeat the steps in each program. Then try
> sorting out the music folder info directly via Windows options only.
>
> Also, album art is controlled by desktop.ini in the album folder and not by
> thumbs.db. Here is a link to an article that explains how to rebuild the
> desktop.ini files for music and picture folders:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;555077
>
> Since there is an outside element of players updating album info, you may
> also want to ask in those newsgroups about how to manage albums and how to
> correct wrong info where the player is involved in maintaining info in one
> of these folders. There is an index within Windows Media Player (WMP) but I
> don't know much about it. However, the folks in the mediaplayer newsgroup
> should be able to give you some helpful suggestions. A link for the web
> interface for this newsgroup can be found under Windows Media on this web
> page:
> http://support.microsoft.com/newsgroups/default.aspx
>
>
> --
> Sharon F
> MS-MVP ~ Windows Shell/User
>

Sorry, sloppy text editing (I can't work in these little boxes!)
resulted in several typos on my part in my last; corrections:

|This is not a media player problem. I only reluctantly use Windows
|Media Player 10 and it is set to neither retrieve info automatically
|from the internet nor automatically update music files.
|...
|For fear of making a bad situation worse, I think I'll hold off on
|executing the "rundll32 mydocs.dll,PerUserInit" command until it's
|my last resort!

More input:
Disk checks on both drives on this system showed only the following
types of errors...
Cleaning up minor inconsistencies on the drive.
Cleaning up 932 unused index entries from index $SII of file 0x9.
Cleaning up 932 unused index entries from index $SDH of file 0x9.
Cleaning up 932 unused security descriptors.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Windows has made corrections to the file system.
The corrections did not resolve any of the problems.

Examining the registry, I have been able to determine that there
must be some corruption to the hashing mechanism for the "bags"
in "HKCU\Software\Microsoft\Windows\ShellNoRoam\Bags\...". If
I change the picture associated with one directory to a uniquely
named JPEG file, it shows up in a single bag. However, that
image shows up in the thumbnail view of at least 2 directories,
even tho there's only a single reference to it in the registry.
Changing the image to a brand new JPEG (thus previously not in
the registry) in one of the 2 directories results in that image
appearing in both directories' thumbnail views...tho only in a
single bag. Thus, it would appear that both directories are
hashing to that same "bag". And further examination of the
registry shows that directories to which I've never made any
customizations (in Shared Documents for example) must be
hashing back to other directories (in My Documents or on
disk D:) that I've modified since whatever event damaged
the hashing mechanism.

So my desire at this time would be a safe way to correct the
hash tables. It would seem unlikely that there is any way
to do that without loosing all the entries that are correct...
I'm resolved now to having to repair everything. Is there some
published procedure to clear the "bag" cache AND it's hash table?
That is, some procedure short of my manually deleting the Bags
entries AND whatever is pointing to them? Searches of the
MS Knowledge Base and in general on the internet so far have
turned up nothing. Too many hits on the keywords I can think
of to use, and nothing really relevant to the situation at hand.

But I can't be the only one with this problem! If this is a system
bug or the result of damage to the registry due to a system crash,
then everyone using XP must be vulnerable to the problem.

Leland

.

Relevant Pages