I used the easy(unattended) install when I created my VM. Something in the VMware install script is probably be causing the keyboard type to be set as 'SKIP'.
That said, it works initially before upgrading packages and breaks after package upgrades. So it might be a good idea to see if the package upgrade is causing the keyboard type to change, or if something in the package update is just illuminating a dormant problem caused by the vmware install script.
Charles makes a good point.
I used the easy(unattended) install when I created my VM. Something in the VMware install script is probably be causing the keyboard type to be set as 'SKIP'.
That said, it works initially before upgrading packages and breaks after package upgrades. So it might be a good idea to see if the package upgrade is causing the keyboard type to change, or if something in the package update is just illuminating a dormant problem caused by the vmware install script.