Good afternoon… I have a weird thing that I’ve noticed. Since Overwolf ended their API for Curse it made it so I can’t use wowup. I am not a fan of Overwolf due to their business practices in the past (crypto miners forced in software, etc…) So to use curse to do addon management I run it in a VM on my machine with the directory shared so that the VM can see it and have Curse still work to update. that way it is quasi sandboxed and I run the VM when I update addons and when I’m not I don’t have to worry about it doing anything on my machine I don’t want it to.
The issue I’m having now is that whenever I load battle.net to be able to access wow it updates the permissions for the folder that i have network shared so my VM can see it. (resulting in me needing to constantly readd the permission and then setup curse every time i want to update. My question is, how can i get this to stop updating my network share permissions and why is it doing it in the first place.
I’d like to point out that about a month ago i had an issue where battle.net and zygor couldn’t connect to their services online. I’ve done a fresh install of windows and wow on my machine and that has fixed that issue. Prior to this install my share/vm solution worked perfectly. Now it isn’t. Any help available to be able to run the addon manager on the VM and not have WoW remove the share permissions when i open Battle.net?