>>149330165
I think you're missing the elephant in the room with black people and being portrayed and thieves all the time.

I have Mint live on a usb. Put it in, booted it up to transfer some files from a broken mint on a drive to external drive, neither of whichare even on the same hd as my windoes partitions. Now my win10 bootloader is fucked up, won't recognize the OS and when using a usb win 10 iso startup repair or refresh points won't fix it. The Mint running was live, I didn't do anything to the system whatsoever, although when I was shutting down it did make me do something funny and instructed me to remove the usb media and hit a key before it actually would shut down.
Does running any instance of linux (not saving or installing, I know of efi partition overlapping issues and that doesn't apply) have chances of screwing up anything related to Windows? I'm trying to walk back everything that happened and for the life of me I'm drawing blanks. There were issues with setting my bios to boot legacy/mbr needing to be toggled, which is weird because all my OSes are EFI, but otherwise I can't think of hoe any of this would screw up a completely seperate hard drive.
I think I'm at my wit's end, this is the 2nd time my bootloader for win10 happened to be fucking up, I think the first time was related but I fiddled with so many partitions in multiple drives (because the whole point was to move win 10 off my m.2 that was dual booting onto its own dedicated drive) I assumed it was my own fuckup then.
Can I run a partial instal of the OS just to repair the boot and not actually add another C?