We have regularly seen this issue with older versions of Timeslips on Windows 8 or Windows 10. Why it would impact one user and not another, don't really know. The only thing I can think of is that they might have different versions of the richedxx.dll, but we don't really know what the cause is. Assuming running Windows 8 or Windows 10, the only guaranteed answer is upgrade.
↧