Solved How to detect corrupt media files?

[Callender]

Does anyone know of a way to scan for corrupt media files? I'm talking about video and image files that might be corrupt. I have found a way to check the entire hard drive for corrupt .jpg files and delete them when found but I'm looking for a way to fix other possibly corrupted media files without needing to locate them and check them one by one. By media files I mean video and image files. (all formats).

 

[Golden]

How do you know what to fix if you don't know it needs fixing in the first place? Surely you need to be able to locate them in the first place which is what you have managed to do?

 

[Callender]

What to fix.

Thanks. I guess that I didn't explain too well. The reason that I'm looking for corrupt media files is that I read somewhere that such a file can cause iconcache.db corruption. Currently I need to rebuild the icon cache one or more times per day. I've tried the usual fixes such as changing colour depth in display to high color 16 bit then back to true color 16 bit. I've also disabled windows tracking of broken shortcuts and keep broken shortcuts to a minimum. I've applied the hotfixes from microsoft.

I've scanned for and deleted all corrupt jpeg files.

I'm looking for a way to automate detection and deletion of other possibly corrupt media files. I read that one possible cause of iconcache.db corruption is the presence of at least one corrupt media file and I'd like to investigate this further.

The problem happens at random times and there doesn't appear to be a common cause that I can track down.

 

[Callender]

Fixed the problem

I didn't find an easy way to check for corrupt media files that I thought might be causing the problem but I went back over steps that I performed some months ago to fix iconcache.db corruption problems and part of the fix was to create the following registry keys:

[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\ScheduledDiagnostics]
“IsBrokenShortcutsTSEnabled”=dword:00000000
“IsUnusedDesktopIconsTSEnabled”=dword:00000000

I checked again today and found that these keys were missing - probably down to using an overly aggressive registry cleaner or something! So I re-created them and so far there have been no further problems.