Vortex keeps purging when I download and install a mod

[blesch]

18 minutes ago, Pickysaurus said:

Considering this is only happening for the two of you, I can only assume it's something your two systems have in common or something is very broken in both of your setups. 

The first thing to try would be to go to the "Extensions" tab in Vortex and disable all extensions in there, reboot and see if it still happens. If it doesn't then you must both have a faulty extension installed. 

It's literally not just the two of us.

Go back and read the thread, and you'll see this is now four of us reporting this same problem.

Also, I don't have any extensions installed, and never did.

Seriously. READ THE THREAD. There are four of us end-users IN THIS THREAD reporting problems with vortex auto-purging after deployment.

[blesch]

29 minutes ago, Pickysaurus said:

Considering this is only happening for the two of you, I can only assume it's something your two systems have in common or something is very broken in both of your setups. 

The first thing to try would be to go to the "Extensions" tab in Vortex and disable all extensions in there, reboot and see if it still happens. If it doesn't then you must both have a faulty extension installed. 

The part you ignored, again, because apparently you don't know how to read things carefully:

Congratulations. You've perfectly embodied the idea of being terrible at your job: pretending it's quite literally not your problem, and blaming someone else for it.

You still also have four people, not just two, who are reporting this problem.

[showler]

Click the "show hidden" button to see your extensions.

[Pickysaurus]

Just now, showler said:

Click the "show hidden" button to see your extensions.

That actually won't work here. We don't need to see the bundled extensions 

[AKULA108]

58 minutes ago, Pickysaurus said:

Considering this is only happening for the two of you, I can only assume it's something your two systems have in common or something is very broken in both of your setups. 

The first thing to try would be to go to the "Extensions" tab in Vortex and disable all extensions in there, reboot and see if it still happens. If it doesn't then you must both have a faulty extension installed. 

With the info given we have some progress, I disabled all extensions un-related to Skyrim and was able to launch the game through SKSE which is now recognized in the tools tab. However it resulted in an instant CTD. 
My question now is, is there a way to remove unwanted extensions for other games as well as force updating existing extensions? 

Edited May 15 by AKULA108
Clarity

[AKULA108]

Resolved the crashing issue and was able to play the game normally after disabling all extensions unrelated to Skyrim. I advise the other users in this thread to try Picky's solution.
However my previous question still stands, I have around 80 unused extensions from other games, is there a way to delete them? I can only disable. 

[GrampsGohan]

I want to add that I am also getting this purge loop after updating to 1.11.x. Definitely not an isolated bug.

[blesch]

10 hours ago, showler said:

Click the "show hidden" button to see your extensions.

[pbd5108]

Happening to me too.

 

it randomly started purging after I updated (now on version 1.11.4) every single time I enable or disable any mods. 
 

It’s really annoying, happened once while I had the game open and it trashed lots of my mods so I had to entirely re-install like 80 of them (luckily vortex has the re-install function for that at least) and since I’m not home I can’t even check if my game will run properly. 

[pbd5108]

So after some trial and error, I’ve discovered it is one of the “Bundled Extensions” causing this issue.

I am not sure which one specifically, currently trying to narrow it down but it’s not any of the game ones. 
 

i can confirm it’s the extensions because after turning off most of them the purging stopped occurring when I disabled to enabled a mod, now I just need to figure out which extension or extensions specifically are causing the issue.

My working theory is that it’s one of the ones closest to the bottom, perhaps one of the file specific extensions.