Hi all,
while I am sorry Core Update 164 caused such a mess (two major bugs in one release - sigh), I am glad to see the discussion going on here, trying to find, understand and resolve the issue. Excellent! 
If I got this right, this and this thread cover the same issue. Therefore, I take the liberty to close this one, to avoid the same problem being discussed in two different places. Please post to the other thread, if necessary.
Thanks for your understanding, and best regards,
Peter Müller