In the six years I've participated on this forum, I don't recall any sort of corrupted file epidemic.
As a user group here, no one can predict, manage or contribute to any experiences with the chat service. I'm sorry you feel that you were treated rudely.
I do sincerely feel your pain with a corrupt file. Having used PC's since their invention, I'm compelled to suggest file corruption is most likely caused by disk errors or other computer faults. Common practices should include saving backups of projects as you work through them. Premier Elements does that in two ways. First is the automatic routine that makes backups of the .prel file. Second is the File > Save as... option that can be exercised after every significant editing accomplishment.
One last suggestion..... If you're seeking help on a user forum, don't start out with an angry post. The internet is crowded with user forums where all that participate do so for the reward of being of help to someone. Anger does not work well for that.
Good luck. I hope you don't have too much time lost rebuilding your project.
Sorry that if it looks like an angry post. It was an architectural presentation which i supposed to submit today, and the entire process really frustrated me. Fortunately i managed to get a one-day extension for the submission, and started to work again.
But still i do believe that Adobe should fix this problem, because i found out that some users experienced the same error as early as 2010.
On the other hand, i use various Adobe products and even though i rarely contact Adobe tech. staff, i would never imagine such a large corporation could hire that rude representatives.That was as important as the "Keyframe.h-142 Error", so i wanted to share my frustration publicly. Again, sorry for this...
I kind of agree with the tech. Your first step is to figure out what caused the corruption. And that's not an easy thing to figure out.
But, as Bill says, it's not a common complaint on this forum, so it's no likely a bug in the program. Though it could be that something you did triggered something in the program that most of us never trigger. Or you tried to open a project created in one version of the program using another version.
It could be a virus (or your antivirus program) or other malware. It could be something up on your hard drive or in that area of your directory or a bad or outdated driver or something going on with Windows 10 (or Mac OS) or even some strange combination of several of these.
But, as your tech said, in the vast majority of cases, the solution is to grab one of your auto-saves. Though the fact that all of your auto-saves are also corrupted is a real cause for concern.
I know that doesn't help you in this case. But you haven't said if this is something that is happening with every project you've created or with only this project. It may never happen again.