PSE 15 Shut down when browsing files

Hi,

Since writing the note I’ve done a lot of work – almost 40 hours so far and think I’ve identified the problem. It was in the Organizer. I’m running windows 7 – 64 edition. The event log indicated a number where it shut down the process and every time the shutdown was triggered by an update on windows security. I went in and checked the actual file using note pad and it had lots of strange symbols as well as text. My assumption was the file was corrupt. So I proceeded to uninstall that update. Ran PSE 15 again and it shut down again and this time the number traced back to the previous windows security update so I uninstalled that update. Once again it shut down and I found the error associated with the next KB file from windows security update. So I thought if I went back all the way to when I first bought the computer I could get rid of the files causing the problem. So I removed all updates from windows security back to August 2015 and it still did not work.

So the problem that started all of this was that when I would try to browse a file in PSE 15 organizer either in the section to add photos from files or in edit preferences to look at a folder, it shut down. This was not the case with PSE 11 which I had already loaded. I tried taking PSE 13 off and loading again and then it got the error message.

So my conclusion is the problem is something in the files that loaded with one of the windows security updates and now when I load or reload a version of PSE, it hits one of those bad files.

Now I’ve created more problems for myself because when I try to load the security updates again, windows update will not work. I tried to go back and do a system restore to the time before I loaded all of those files and it would not work. So I think there are some corrupted files somewhere and I need to fix that and hopefully all the programs will work right.

I would still like your help on a couple of questions.

-Does all kind of strange symbols in a file mean it is corrupted? I get mixed messages when I run a command prompt to check and fix corrupt files – sometimes none are found, sometimes it says it found them and repaired them and sometimes it says it found them and could not correct them. So I need to figure out how to actually find if files are corrupt.

-If I have corrupted files is there a way to fix them without having to roll my computer back to factory settings and reloading everything?

Right now I’m looking at a lot of work if I have to go back and start loading everything.

Thanks for your help.

Paul