I think I reported this same bug to the Paratext developers last week.
In my case, it was caused by downloading an enhanced resource in Paratext 9.
I fixed it by deleting the newest ldml file in C:\ProgramData\SIL\WritingSystemRepository\3.
At next launch, Paratext recreated the ldml file which I’d deleted and everything worked OK afterwards.
LivingField