This is a known bug according to several Internet sources...
So how can I DISABLE indexing of network shares???
I have a network share which has like 200 folder/sub-folders, and everytime I access it, it works for a second or two, then it hangs windows explorer, sometimes hanging my whole PC (explorer.exe)!!!
And I know it is doing this because the root folder only has like 20 sub-folders, all of which I can clearly see listed, but when I do a Wireshark capture (tcpdump), I see all the sub-folders and files being listed, so I know it must be spidering the share and indexing everything. The worst part is, this share is on a NetApp, so there are .hourly and .daily and .weekly and .monthly snapshots of all my data.. In all, it is several dozen gigabyes of files, folders, and sub-folders, all of which Vista is "attempting" to index, but cannot/store..
Does anyone know how to turn off indexing? Heck, I'd be happy with NO (not even local) indexing just to avoid this damned problem again and again...
No known ETA on a fix from MSFT, from what I can find.. Which is a shame!
So how can I DISABLE indexing of network shares???
I have a network share which has like 200 folder/sub-folders, and everytime I access it, it works for a second or two, then it hangs windows explorer, sometimes hanging my whole PC (explorer.exe)!!!
And I know it is doing this because the root folder only has like 20 sub-folders, all of which I can clearly see listed, but when I do a Wireshark capture (tcpdump), I see all the sub-folders and files being listed, so I know it must be spidering the share and indexing everything. The worst part is, this share is on a NetApp, so there are .hourly and .daily and .weekly and .monthly snapshots of all my data.. In all, it is several dozen gigabyes of files, folders, and sub-folders, all of which Vista is "attempting" to index, but cannot/store..
Does anyone know how to turn off indexing? Heck, I'd be happy with NO (not even local) indexing just to avoid this damned problem again and again...
No known ETA on a fix from MSFT, from what I can find.. Which is a shame!