6
Windows Explorer (Windows 7 x64) crashes when it sees allegedly corrupted .wav files. I'm dealing with this problem and the hotfix outlined in "High CPU usage in the Explorer.exe process when you open a folder that contains corrupted .wav files in Windows 7 or in Windows Server 2008 R2" doesn't work for me.
The hotfix says that this happens if the .wav file is corrupt (which I don't think it is). What makes this even worse is that I can't access the file in any program. As soon as the open dialog sees the file, Windows tries its metadata extraction trick and explorer.exe halts.
Can I by any means tell Windows to stop this "metadata extraction" action? I have seen multiple problems associated with it in the past.
Can you rename the file using a cmd window? Doesn't fix the issue, but you could temporarily stop explorer trying to get metadata if the file extension was changed to something different. – DMA57361 – 2011-01-14T14:37:28.987
1I can access it from command prompt yes and rename it. That's what I did and would have solved the problem BUT ... there is an associated .sfk file to go with it that SoundForge reads. What i tried today was to rename the file as .raw, open it as raw in SoundForge and that worked fine - except I didn't get the extra data (regions that i have created) into the file, since that comes from the .sfk file. – olafure – 2011-01-14T19:35:10.967
1I found a way to open the file in SoundForge and get the .sfk contents too. File > Open, but don't browse to the actual folder. Instead type in the full (or relative) path to the file, including the filename. In that case windows leaves it alone. And btw, SoundForge doesn't have any problems with the file, even though Microsoft says in the hotfix that this only happens if the .wav file is corrupt. – olafure – 2011-01-15T20:53:32.480