It should be booting after Boot Repair has done its thing. You've probably got a defective EFI on your hands. I recommend you check your manufacturer's site for an updated EFI (it will probably be called a "BIOS update" or something similar). If you find one, update the firmware and then try running Boot Repair again. I don't actually hold out much hope that this will work, but it might. One complication with this advice is that you may need to be booted into Windows to update the firmware, so you may need to get it working well enough to boot before you can do this. Other times, though, you can update the firmware using the firmware's own setup utility -- you'll just need to write the setup files to a USB flash drive from another computer.
If that doesn't work, then my next suggestion is to disable Secure Boot, download the USB flash drive or CD-R version of my rEFInd boot manager, prepare a boot medium, and boot with it. This should enable you to boot either Ubuntu or Windows. Boot Windows, open an Administrator Command Prompt window, and type:
bcdedit /set {bootmgr} path \EFI\ubuntu\shimx64.efi
This creates a boot entry from Windows, which is occasionally more reliable than doing the job from Linux. If it works, you can re-enable Secure Boot.
If that doesn't work, then my (almost) final suggestion is to run Boot Repair again, but enter the Advanced menu and select the option to back up and rename boot loaders. (I don't recall the precise phrasing, but it should be obvious.) Run the repair with that option selected. This enables an ugly hack to work around the ugly EFI bug that's causing your problem.
Really, though, if you have to resort to that last option, your computer is broken. As in, broken so badly that it should be returned to the manufacturer as defective. If the computer is new enough to qualify for an in-store return, I suggest you do just that, then write to the manufacturer to report the reason for the return. Without such returns, and knowing the reason for them, manufacturers will continue to ship broken firmware.