The message about “The automatic download for a Paratext update did not succeed.” means that the downloaded file failed a validation check that is done before we try to install the patch. So, in this case, no attempt to update was actually done.
The patches for Paratext 8 have gotten large - around 55 meg - and this is causing more download failures. Each patch has all the changes since 8.0.100.1 - this makes it easier to just apply the latest patch and have the machine be up to date. The reason the patch has become large is because of some corrections were done to a couple of Source Language Tools resources and an update to the Firefox components. This larger patch is becoming a problem for some, but there isn’t an easy way to reduce the patch size.
There also seems to be a separate problem that happens on some machines when the patch is run because of a check being done for some fonts.
It’s possible for a font file to be on a machine, but the font not be completely installed in Windows. The Paratext installer checks for this condition and deletes the orphaned font files. However, on some machines the deleting of the font files is failing with an “access denied” error. Since the installer is running with administrative rights, I’m not sure why access to the file would fail - just ignoring the error would probably just cause the installer to fail later.
This font check is not new - it has been in the Paratext 8 installer since the beginning.
To verify if your machine is having this problem when there isn’t a PtPatch.log file, you can download the patch using this URL:
http://update.ubs-icap.org/Paratext/patch_8.0.100.63.msp
Then run the patch with this command:
msiexec /l*vx update.log /update patch_8.0.100.63.msp
If some one has this problem and can do a remote session with me, it would be helpful so we can determine how to change the installer. Contact me directly at [Email Removed]
John+Wickberg
Paratext Support
