Hi,
yes, this is because silly me forgot to include some files to the update which carry the version information. No functional problem, but makes Core Update 168 being currently displayed as 167.
Since I will have to work on this update either way due to another CPU microcode release by Intel (as usual, we don’t know what happened there, but hey 
), this will be fixed shortly.
Thanks, and best regards,
Peter Müller