It turns out that the attached VirtualBox.xml file and subsequent screen shots was not the current file being used. My current %UserProfile% is indeed c:\users\director not the d:\ drive, yet I changed the default folder settings with VBox to d: drive. After deleting the xml file, I was able to create a new vdi, but was unable to hack the xml succesfully to attach my original machine and hard disk. It was upon resetting back the original correct xml file and hacking it so my restore point vdi now lives on an external USB/SATA drive that I found the root cause!Ultimate cause
: The original VirtualBox.xml file had the hidden attribute set
thereby all the "permissions" releated issues. I am quite certain I never set this flag
manually and the fact two other people have had similar issues, I'm guessing somehow VBox has done this??? This is the first time I've mucked about with the xml file. Being the admin of this pc, I show hidden files and folders and therefore didn't realise this file was indeed hidden.
I'm concerned that while deleting the file forcing VBox to re-create it as an alternate fix, VBox unable to reattach an existing machine and hard disk, and the new xml has a slightly different heading tags ie: the upgrade didn't upgrade the xml file.
Anyways I'm happy now and everything is running fine - I now have two VM's. I think I might even be able to hack a way to copy a pre-built vdi but I'll do that another day at my own risk.
Thanks everyone and good night.