Vortex requires me to confirm "UAC" dialogue after installing game to another drive

[UltraEgoEnthusiast]

Vortex 1.2.20
Modding Monster Hunter World
Amount of enabled mods: 30 for now
Amount of disabled mods: 30
Amount of uninstalled mods: 36
16 GB of RAM, Windows 10, 64-bit Operating System.
Please confirm the "User Access Control" Dialogue just recently started showing up on Vortex. I had recently uninstalled and re-installed (Originally tried just cut/pasting the entire game and seeing if Steam would have an option to find local files, couldn't find one so it just re-installed the whole game, got what I wanted in the end) MHW from an HDD to an SSD and now that I've manually located where MHW is in Vortex, it requires me to confirm a UAC windows pop up every time I need to install/uninstall a mod. This doesn't happen for my Skyrim Special Edition, which is on that HDD along with Vortex, so I can assume it's a problem with having the mod manager and the game on two separate Drives. All I wanna know is if there's any way to circumvent having to keep saying yes to "Do you want to allow this app to make changes to your device" whenever I install/uninstall a MHW mod with Vortex that isn't reinstalling Vortex on the same drive.
UPDATE: After googling a bit more on related issues with UAC and Vortex, I found out I could just move the Mod Staging Folder for the game onto the same Drive, then have the Deployment Method be Hardlink Deployment (This is in the Settings>Mods section of Vortex.) This circumvented having elevation requests happen for MHW.

While my issue is resolved (for now) I still feel as though this post shouldn't be removed as there is a guarantee someone else may have this problem, unless there's a UAC problem section in an FAQ somewhere I don't know about.

Edited August 21, 2020 by YoloSwaginson

[Pickysaurus]

As you say, if you have moved your game to a different HDD without also moving your mod staging folder it will no longer support hardlinks and fallback to symlinks, which require a UAC prompt when you deploy. If the game doesn't support symlinks it will give you an error instead.