Some time ago, installed a bigger SSD (1 TB M.2) to act as my OS boot disk, cloning the original OS-sporting HD (256 GB) onto it and it works fine. Recently, I wanted to try out Linux and installed Mint on the old HD, which also works fine, giving me a dual boot option at startup. However, it seems like this left a Windows Boot Manager on the old disk (disk 0 in Windows Disk Mgt), so when I choose that option at dual boot, it goes through that one first and then boots the Windows OS from the new SSD (disk 2 in Disk Mgt). No biggie and quite understandable, since I chose to install Mint on disk 0, but still a bit peculiar.
Now Linux is giving me troubles, so I wanted to wipe the entire drive and install it anew. I already changed the boot order in BIOS/UEFI to boot directly into Windows rather than the Linux Mint boot menu no problems there either. In Windows Disk Management I could wipe the Linux partition on disk 0, after changing it into a dynamic volume, but the remaining 512 MB of "EFI System Partition" is untouchable. Even DISKPART is being sassy and also doesn't allow me to delete it.
Now, first of all, I want to be sure that I'm not rendering my computer unbootable, in any there is still some dependency on disk 0 for a proper Windows boot from disk 2. Second of all, how do I go about killing the last remaining leftovers of the Resistance to completely dominate this particular old drive to be allocated and used at my whim? And without having to resort to third party software?
Here's a screencap of my Win Disk Mgt and boot info: