Right I have managed to crack the problem, something in the updates I ran to the hyper v host has killed off the subsystem of windows which was causing the services to not start - this is the problem the services have not started so the installer cannot upgrade or work out what the host is hence the message not supported.
a bit of reading on why I could not start the services led me to the following link:https://support.microsoft.com/en-us/hel ... 08-r2-core
now although for 2008 I gave it a shot and ran the following command on the command line on the hyper v host (as an administrator).
dism /online /get-features /format:table
then discovered this was disabled:
ServerCore-WOW64 | Disabled
I have a hyper v host at home so checked there and that had enabled so a simple run on this command followed by a reboot.
DISM.EXE /online /enable-feature /featurename:ServerCore-WOW64
When the server came back up all the veeam services were started and I was then able to upgrade the host with the latest version of Veeam (probably was not necessary to get a backup but as I had patched the console I did it to keep it up to date.)
I did have to remove and re-add to the console however I was able to keep everything the same so my powershell scripted backups ran nightly as before
Thanks for all your help with this one hopefully the above may also help someone one day if they have the same problems!