From the comments, I gather the problem is fixed; however, I want to offer some explanations and clarifications, so....
I had UEFI turned off I think.
The vast majority of EFI-capable computers use EFI firmware. It cannot be turned off. Some such computers do enable you to force a BIOS/CSM/legacy-mode boot, but the EFI is still running underneath it all. Most EFIs don't even let you truly force a BIOS-mode boot; enabling the Compatibility Support Module (CSM) just makes a BIOS-mode boot an option, not a requirement. To understand this, consider an analogy: The CSM (which enables BIOS/legacy-mode booting) is to EFI what dosemu is to Linux -- both enable a more sophisticated environment (EFI or Linux) to run programs written for a less sophisticated environment (BIOS or DOS). When you run a DOS program via dosemu under Linux, though, the computer is still running Linux; and when you boot a BIOS-mode OS via the CSM, the firmware is still EFI.
Ultimately, the CSM creates more problems than it solves, at least on modern computers. Occasionally it's necessary, but as a general rule, my recommendation is to leave the CSM disabled. Enabling it (aka "disabling UEFI mode") may be what caused your problem in the first place -- or at least, it may have been a critical part of what caused the problem.
Both your GParted screen shot and the Boot Info Script output indicate that /dev/sda uses GPT. As such, Windows must be installed to the disk in EFI mode, and in fact the Boot Info Script output shows EFI-mode Windows boot loader files (or at least, files with appropriate filenames). The Boot Info Script output also, however, shows a BIOS-mode Windows boot loader on the disk. This boot loader would be useless on a GPT disk, though. My hunch is that EaseUS wrote that code to the MBR, but it might have been left over from a previous installation. In any event, it's possible that by activating the CSM, it ended up executing this useless boot code, which resulted in your failure to boot.
