On DA-62, all engine indicators go RED when starting up and engine only runs for ~1 second

Have flown the Diamond DA-62 for over a year with no problems. Today when staring up, the engine temperature, fuel temp, oil temp, gear box temp and oil pressure indicators on the alerts panel of the PFD all came up red and the indicators on the MFD were all to the right end of the display. The engines will start, but only run for a second or two. I have all failures set to disabled. Any ideas on how to get back to normal conditions would be appreciated.
PS This was the first flight attempt of the DA-62 after flying the AS-33ME yesterday. Reset Throttle and Joystick to profile for DA-62. Also shut down and re-started FS2020 after first attempt failed.

It’s been a day since I posted the above request for help and had no replies. Can anyone suggest someplace else where I might find suggestions or a solution? If not, I guess I’m relegated to a re-install. ( a daunting task for an 80+ year old non-computer whiz). Thanks in advance for any help.

Personal Comments

I don’t fly the DA-62 often, and when I do, I use the TommyMxr mod as it makes the plane so much better.

That being said, we’re assuming this is stock aircraft (no mods). What happens if you use CTRL-E to start up the plane?

I’m using the DA62X mod. Starting using ctrl-E produces the same result, I.e., engines runs for about 1-2 seconds and shut down. Removing the DA62X mod from the Community folder and restarting FS2020 produces the same result (not starting), but different indications. I have a low volts indicator on the PFD (yellow) and oil temp and coolant temp gauges on the MFD in the red. Alternator switches are on and aux pumps are on when starting. Starting using ctrl-E works on the second or third attempt, but if I bring the throttle back to idle, both engines shut down.

I replaced the DA62X file in the Community folder and restarted FS2020. Nothing changed; all indicators RED.

Do you have any other addons in your Community folder?
Try with it empty (or just rename it), a conflict with another mod can cause these type of situations.

Did you resolve this problem? I am having the same issues you describe, even after removing the mod.