I have had a problem with a few programs crashing on file opens. Checking the windows logs show that all have the following in common
"Faulting module name: comdlg32.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdf76"
- Running sfc /scannow results in a cannot fix error and identifies comdlg32.dll as corrupt. probably ran about 10 to 15 times with no success (plus a few other non fixables)
- I took ownership of the comdlg32.dll file and renamed it to corruptcomdlg32.dll just in case I needed it later
- reran sfc with the same results and no fix
- then ran a install repair from the Windows 7 DVD again with the same result - did not install a new comdlg32.dll
- did a search of my C drive looking for comdlg32.dll which found about 20 copies of "...longstring..comdlg32.dll.mui" one for each time I had run sfc /scannow from the date:timestamps.
- picked one of these copied it into C:\windows\system32 and renamed it to comdlg32.dll. Ran a selection of the previously crashing applications and all worked as required.
I have wasted a couple of days on this and was getting close to going back to LINUX. My question really is "Why would neither the repair install nor sfc /scannow actually do the repair but leave the required files in place"
I could only come to the conclusion that even using an elevated cmd shell it could not handle files that were identified as belonging to "trusted installer"
This is not just an academic question as while the other files thast cannot be repaired appear to mainly truetypefont files one is winresume.exe