Simple answer is NO there was no resolution from QB Support.
I'm still searching my machine for some remnant of a QB update that may have not been cleaned up by the update process which may be lurking with a dll or some such the is interfering with the new year's update.
