Thanks, also following that bug :-) Indeed, manually running shim-install installs the new shim and the original issue does not occur.