Comment 246 for bug 1289977

I can confirm that there is some regression going from grub2 2.00 to 2.02~beta2.

I have disk0 with traditional partition table and three partitions:
sda1 is Windows boot
sda2 is Windows system
sda3 is linux Mint root partition (with /boot inside it)

In the past I manually set up the Windows bootloader as to chainload with grub, therefore grub is installed only in sda3 boot sector.
This worked well until I attempted upgrade to Mint Quiana via do-release-upgrade. After the upgrade the Windows bootloader came up as before, but selecting the item for Mint gave exactly the error reported here.

Therefore I booted from a USB stick containing Boot-Repair-Disk (which I understand is really Lubuntu 13.04 "Raring Ringtail") and executed the following as root:
grub-install --force --boot-directory=/mnt/boot-sav/sda3/boot /dev/sda3
It showed the usual warning about blocklists, but the error went away and I was able to boot linux Mint through the Windows bootloader.

Once inside Mint I executed the following as root:
grub-install --force --boot-directory=/boot /dev/sda3
At the next boot the same identical error about "symbol 'grub_term_highlight_color' not found" was to be seen.

The relevant difference seems to be that Boot-Repair-Disk has grub2 2.00 while Mint Quiana has grub2 2.02~beta2.