Is there a fix for this problem yet?
As to what an actual fix for the issue people have been experiencing, I don't know. That said, from what I seem to see is that this error it only happens on some machines and not on all machines. The only thing I can think of which is causing this on some machines is that Windows hasn't been updated for quite some time, and some system files are well and truly out of date, including the one that e-Sword uses.
You see, I don't believe for one moment that Jon (JPG) and I, or Bob are the only ones that didn't and don't have that issue with e-Sword, but rather that the overwhelming majority of Users have their Windows updated. So this tends to indicate that those who are experiencing the problem needs to get their OS updated, and at best to turn on the Auto Update switch in Windows Securities and Update settings.