Another option available, if the OP chooses to exercise a choice of Ubuntu, is to install a WUBI setup that will run from Windows, and work from there with the troubleshooting.
This may be a good idea under three conditions.
1) Fully image the drive first to ensure that there's no mistakes made.
2) Make sure (if not a SSD) to run a couple of defrag passes, my first taste of Linux was via WUBI, and this left my HDD in a 55% fragmented state, reducing performance big time for both OS's. Back in early 2009, this wasn't included in the documentation, otherwise may have created a partition just for WUBI.
3) Go light on the extra software, and no 'cleaners' (more below on this).
Either less folks are using WUBI, or it's a well worn out idea by now, as I rarely see anymore of these tutorials nor do I see the option on the install media. Back in 2009, it was a big deal, attempting to lure users to Linux, and it worked. Had I not seen these articles, would have never thought to try Linux, only thing was that I made one fatal mistake that I know now how to correct, bootloader repair. Running 'cleaners' from within WUBI is an outright dangerous thing to do.
The really odd thing in my case was Ubuntu was an installed program within XP, yet I couldn't boot into that OS, only Ubuntu. Computer Janitor messed up the boot loader, and like I stated above, know what to do to fix it now, but didn't then, and the worst part was that it was a new, yet to be imaged, install. So I made 3 mistakes, didn't defrag first, didn't backup, and finally the install of a cleaning app within Ubuntu.
To sum things up on this, cleaners aren't needed on Linux OS's, because these doesn't leave 2-3GiB of files to delete post install. Maybe 300-400MiB & that's it. The only thing that will need cleanup from time to time is the browser, and both Firefox & Google Chrome has an option to perform cleaning of built up temporary Internet files, the cache, cookies & more. Much safer than any cleanup utility can do.