you sound like you don’t have keyB control outer also on the Operating System, i.e. the "grub menu screen" this means your BIOS settings for your USB devices are incorrect, confirm they are connected properly. Eg similar to on newer BIOS verify the "USB legacy setting".

If you have already uninstall Ubuntu boot your system from a windows CD, then type as fdisk /mbr in RUN command address bar this will reorganize the master boot record then as you like paying for software go out and buy a copy of partition magic and resize/reformat your drive back to what they where Gpart live CD does the similar thing for free, but it support Linux. If you where having problems with Bluetooth within Ubuntu’s login screen to fix the Bluetooth keep out at startup problem in Ubuntu 8.10 and 9.04. (I thing this is only needed for Bluetooth devices that don't maintain HID thing)

unplug the Bluetooth adaptor and after that plug it back in, (this should give you KeyB and mouse control) and after that login and edit the file on the Ubuntu system located here/etc/default/Bluetooth like this go to the terminals and type sudo gedit /etc/default/Bluetooth change this line from

HID2HCI_ENABLED=1 To HID2HCI_ENABLED=0

And after that you reboot your system and KeyB will be going on.

That Ubuntu that remains on your system is Linux bootloader, identified as GRUB. It is mostly a very little peace of software that begins soon after you start your PC, by Windows boots up. As you've most likely guess its job is to boot the operating system of your choice. For various reasons GRUB is not completely sited on any of your partitions (C:/, D:/, or what ever), a section of it's code is installed into a very small crop of "land" right in front of the initial partition, called MBR (Master Boot Record). MBR is firmly controlled by any Operating System (Windows, Linux ...) and access to it is advantaged. Due to this, WUBI, the Windows-based Ubuntu (un)Installer, probably had a problem restoring the MBR to its unique state. For me, the easiest way to repair this was to run "fixmbr" in the Recovery Console, accessible from Windows installation CDROM.