This is very strange but this error persisted after a complete wipe & reinstall of the pack. Stranger still is that now, without a reinstall or update, it's no longer producing the error, even after several client restarts... I will continue to monitor & post if it occurs again.