Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
This will compare your current installation against the version provided by Steam and any differences will be downloaded and overwritten; thus fully resetting your game back to vanilla.
To set up new mods again you'd first have to install SKSE, then just set up your mod manager and let it handle the rest of your mods. Vortex is quite good at that.
If you are using a mod manager you can uninstall mods quite easily, you just need to start a new game.
If you aren't using a mod manager, or are using the built in mod system, then you need to delete the data folder
Documents>games>skyrim SE
If you’re using Vortex - hit the “Purge Mods” button on the top of the window that shows all your enabled/disabled mods.
This won’t physically delete those mods, it’ll just prevent Vortex from deploying all of them and it’ll be like they don’t even exist in your game anymore (until you manually deploy again).
This only applies to mods in Vortex though, if you’ve done any manual installations (like SKSE or an ENB) or made any changes to files yourself - those will still be there.
Some mods can mess with configuration files, thus uninstalling the mod still leaves some changes behind. Vortex can do a lot, but it doesn't always catch everything. This method does.
Also... I could easily accuse you of being wrong as well. A mod manager like Vortex allows you to disable mods as well, which would be much quicker and also mimics the impression of having removed everything.
Just because you prefer another method doesn't render others wrong.
https://steamcommunity.com/sharedfiles/filedetails/?id=2743619856
And DO NOT clean or edit the Master files or any Creation Club content.
Link is from the following section of the PINNED TOPIC Helpful Links and References
https://steamcommunity.com/sharedfiles/filedetails/?id=2882871440
Good luck!
Given the OP is asking how to remove mods, and your method doesn't touch mods, I ask you for a better term than wrong???
Fun fact: with the introduction of 'Creations' Skyrim is actively using the 'Data' folder as well for its own expansions, it even provides in-game load order optimization.. Basically everything is affected and mods are supported 'out of the box'.
Thing is... just removing mods doesn't cut it. For example... what do you think is going to happen if you remove, say, "ccfsvsse001-backpacks.bsa" (and it's .esl counterpart) from the Data folder, then restart your game? I'll tell you: your game is going to crash. Why? Simple: because the loading (or using) of mods isn't merely defined by its presence, there are also config files involved.
(edit) => Forgot to mention: my point is easily proven: just use Vortex to disable a mod, then go look at your Data folder. You'll notice that nothing has changed there, the disabled mods are still present, yet won't be loaded.
Speaking of which.... there's a reason why the general rule exists that you should never edit / modify the ini files in your program folder.
But bottom line: those config files are affected when you reset your game back to its default.
And the reason I know that I'm right is because last week I used this method for myself. I started playing again after I took a break for almost a year, and to make matters worse I also accidentally upgraded Skyrim somewhere in between but couldn't be bothered with grabbing any backups at that time, also because I figured that the mods would eventually catch up anyway.
So my installation was a complete mess. Almost instant CTD's, even without SKSE. But after I had reset my game as mentioned above, then used the Steam client to fire it up again the whole thing behaved as expected: no more mods, no more crashes; things just worked as expected again.
From there on I got Vortex to reset my mods, then upgraded the whole lot and sorted out version conflicts and what not. Eventually resulting with my game being fully back on track again.
There's a big difference between reciting theory, or sharing hands on experiences.
Good luck, once again!
The rest is waffle, apart from pointing out that creations work slightly differently, not the way you say, but differently...
As for the OP, listen to smr and use the links he provided.
That's because the mod configuration was still baked into it.
What you are merely doing is that you reset the entire setting back to default stats and manually remove/delete mod via Vortex.
This work fine if you are using mod manager, but it doesn't work if you manually install mod. That's because mod manager such as Vortex is hardlink, any mod you installed via Vortex would be deposit to the game main data folder. The same applies when you removing the mod via Vortex, it would delete it from the game main data folder where it is stored.
But if you are doing manual installation without using mod manager. Verify files integrity only detect the origin files for corruption and reset it back to default stage, it doesn't remove the mod that are manually placed inside the data folder.
You should also delete the Skyrim folder in "c:\users\<username>\appdata\local" and to be totally pristine also delete the "<Steam install path>\userdata\<bignumber>\489830"
In the simplest words I can think of:
Why not do it any other way? Mods may contain Papyrus scripts. Scripts may contain Properties. Those properties are stored in your save file and when those mods are removed, the data are still in the save file and may cause issues in the long run.