I think the big culprint here is that he has '
restored' the files.
I have a very big feeling he used some sort of undelete tool (of which there are 13 in a dozen... all claiming to be gold, but mostly crap) and that those logs are actually not logs at all, but bits of executables or other files which can have certificates. It would explain everything....
-----
AntiRafidah,
Your problem is different than Namnlos'. That is: both of you have file extension associating problems (see my previous post... reinstalling Plus! will fix that). But AntiRafidah, you have one more, much worse problem which most likely can not be solved.
You need to know that the Windows properties dialog does not depend on the file extension (in this case ".ple") but actually reads the file content to display information.
Now, if my guess is correct, your logs are long gone because the actual content on your HDD of those logs was overwritten with other newer files when the logs got deleted. The 'restore' program simply re-assigned the once occupied clusters to that previsouly removed filename.... That is because restore programs never restore the actual content of files, but rather simply re-assign the once occupied clusters (which contained the actual content of those removed files) to the filename again in the file system table.
This is a very common thing to happen and/or misunderstood when people use 'restore' or 'undelete' programs without the proper know-how and in the promise that they can restore everything.
Thus, AntiRafidah. I'm afraid your logs are not logs at all but instead reminenses of other executable files. So what you have 'restored' are other files but with the filename of an old logfile.
So that's the reason why the Log Viewer can't open them; they are not logs at all to begin with so the Log Viewer does not know how to handle them. And that's also the reason why you would see a certificate tab in the properties dialog even while logs files can not have certificates at all.
To make matter worse: there is a small remote chance that other files on your disk are now corrupted too. This because the 'restore' function has assigned clusters on your disk to a file (the ".ple" files) which belonged to other files (the original executables or whatever). If those other files were existing files you have big problems.
Now, don't be that alarmed though. This is just a chance. Usually, 'restore' programs do not assign clusters which are currently in use.... but there are 'restore' programs that do and/or can! And if you used one of those, but without the proper knowledge, you might have done more damage than you think.
Very short bottom line: I'm afraid your logs are gone and they can not be restored anymore.
All you can do now is simply check each and every log you have restored by opening it in the Log Viewer. If the Log Viewer says it can't open the log then that log isn't a log at all and the file should be removed. There is nothing you can do about that, it's gone..... But, even if the Log Viewer can open the file, make sure it actually is a log and check its contents all the way to the end.
EDIT: here is a (technical) link which explains it way better than I can about what happened (but also way more reading to do 
), especially the "What Happens When Data Is Deleted?" part.
http://www.makeuseof.com/tag/impossible-recover-d...hnology-explained/
-----
PS: I also noticed the date assignments in both your screenshots. eg: "den 6 november" ????..... It seems you have some more issues with your PC/Windows OS.
/ 
