[NAME]  The Ubuntu entry in your boot list is a registration in your UEFI firmware.  Windows makes one as well.  You can go into your BIOS Setup by pressing F2 and choosing to remove it if you want.  But that isn't the source of your problems.  But if you try following the steps I posted above -- adding NOTHING to them that you think might be necessary -- and you still have problems, then I will say for the third or fourth time now that you'll need to be more specific about the problem you're having.  Just saying "the process aborted after starting Setup" isn't specific.  Exactly how far did you get in the process, i.e. what was the last thing you clicked on or saw on screen?  And what exactly does "aborted" mean?  Does that mean an error message of some kind?  If so, what did it say?  Or did you system spontaneously reboot?I'm really trying to help you here, but you continue to do things that have no real resemblance to what I'm suggesting, while providing information that is far too vague to understand what's going on in order to help troubleshoot.
Dell understandably does not support users mucking around with the partition table, but that should not preclude users from discussing that subject with one other.  To that end, I will describe one way of doing that.  You need to boot into a system such as any Linux version that provides a virtual environment in which you can run software that can operate on your hard drive.  That environment treats the hard drive as an external device.  I've already done this with a Kubuntu installation memory stick.  In that case I choose to try Kubuntu rather than install Kubuntu.  The environment that results operates outside of the hard drive's memory.  In particular, you can run a partition editor such as gparted. I'm thinking of trying an experiment where I zero out all of memory and then do a factory reinstall.  I don't if it will work, but it ought to. What led to explore this topic is a situation where none of the factory install images I've gotten from Dell support have worked. The most likely cause is a corrupted partition table, and the procedure I describe offers some hope of allowing the factory reinstall to move forward.  Needless to say, there's no information in the machine that I need to save.
Manipulating the partition table