File Can't Finish "Extracting" Step

[Zanderat]

..........for this mod https://www.nexusmods.com/skyrimspecialedition/mods/13015? in 16.5 Mod itself seems OK. Thanks.

[WastelandAssassin]

have you tried redownloading the mod? have you tried opening the download folder and trying to open the archive yourself?

the mod is somewhat large , so there is a high chance this could simply be due to a corrupted or failed download , meaning the archive is incomplete

 

or have you tested this , and the mod opens and extracts fine outside of Vortex?

[Zanderat]

Yes. I was able to extract it outside of Vortex. I also resaved as .7z. That wasn't able to extract in Vortex, either. I downloaded it three separate times. I did try another small mod and that one was ok. So, it could be tied to the size of the mod.

[Zanderat]

nm

[WastelandAssassin]

were you able to fix this? if so , can you try and point out the issue? just in case others report similar issues

[Zanderat]

Not fixed yet. Can't pinpoint why this particular mod is having trouble. It can extract normally outside of Vortex.

[FilthyGruntler]

I'm having the same problem, with any mod I try to install. Most recently, have been trying to install Skyland Whiterun and Skyland Farmhouses; I have been unsuccessful with any mods I have tried though.

This started happening for me after Nexus mods went down today. After the site was back up, Vortex had me signed out, and I couldn't sign in for nearly an hour. After I got signed back in, I was able to install 2 mods, then this started happening. I have redownloaded, restarted Vortex, and also I reinstalled Vortex. Still getting hung up at the extracting stage. If I let it run for approx. 30 min, I get fail to install errors.

 

EDIT: Ok, I'm in agreement with Zanderat now, it is linked to file size. I tried a few more mods, and small ones will install (I tried Vr mirror which is tiny, and it installed no problem). As far as how big is too much, Skyland Whiterun is a bit over 550mb. So for me at least, anything over 1/2 a gb is not going to install.

[Rattledagger]

Doing a few tests with Skyland reveals this is another problem with sub-directories. Specifically, Skyland includes multiple sub-directories where 3 of the sub-directories is marked read only. Since installing mods in Vortex is a 3-step (or 4 in case of FOMOD) process, where first all files is extracted to a directory ending with .installing for afterwards being copied to final destination and at the end the .installing-directory and all sub-directories is deleted. With one or more of these sub-directories marked read-only Vortex can't delete the sub-directory and get stuck.

 

As a work-around, extract the mod-files to another location, example to c:\example

 

Upen-up a command-line, by clicking "Search"-icon in Windows and typing-in cmd

 

On cmd, give these commands:

 

c:

cd \example

attrib -r whiterun /s /d

 

You can now exit command-line again. (Change the two first lines in case you're extracting the files to another location).

 

Re-package the files into a new arcive, add this arcive to Vortex and install it.

 

Note 1, you can't use File Explorer to change the read-only attributes on the directories, you must use the command line instead (or another tool that can change the read-only attribute).

 

Note 2, while extracting the mod does create a directory called "Skyland Whiterun", you should ​not ​use attrib -r "skyland whiterun", since the 3 directories marked read only is called "whiterun".

 

Note 3, just coping all the sub-directories will also copy the read-only attribute and this will therefore not work.

 

Oh, and while this work-around works with Skyland Whiterun, it won't work with other mods since their read-only sub-directory will not be called "whiterun" but something else.

 

Of course, it's also possible where's some other bugs making it impossible to install some other mods.

 

While I've reported the bug in Vortex, I've no idea if anyone reads these reports and not even if they're correctly saved anythere.

[Tannin42]

Unfortunately the external module we use to build the Vortex installer has a - rather curious - new bug that causes it to use an old version of some other modules (so upgrading one module got us a downgrade of several others). This here is a bug that's already been fixed.

 

@Rattledagger: All reports are read eventually but it should be obvious that ~15000 users can produce more reports than 1-2 people can reply to, especially when all it takes to create a report is click a button. We reply to reports only when we need to ask for more details. Reports are exported to github if they were either made by a logged-in user through a Report button (because then we know there is at least some detail) or after review - and review is done as time permits.

[Zanderat]

Thanks, Tannin.