Jump to content

Deployment failed error please help most likely locked by external applications fix please!


tbclandot92

Recommended Posts

I'm having the same issue;

The mod downloads properly but whenever i try to install any mod I get this error:
Deployment failed
x files were not correctly deployed (see log for details).
The most likely reason is that files were locked by an external application so please ensure no other applications has a mod file open, then repeat deployment.
For troubelshooting I have uninstalled MO and NMO, reinstalled vortex multiple times both on OS drive and game drive with no change of result.
Link to comment
Share on other sites

The most likely candidate to keep a lock on a file is an Anti-Virus Software since they may try to access any file newly added to the disk and then prevent other applications from accessing it until it was scanned.

 

Also, as the error message says: Your (vortex) log may contain further details, without that anyone can only speculate.

Link to comment
Share on other sites

I had the same issue but I don't use any anti virus software (other than MS' own defender).

 

Uninstalling the mods, closing and reopening Vortex and reinstalling the mods helped me in that case. Before that I tried many other steps without much success. I never found out what the actual problem was.

Link to comment
Share on other sites

Thank you guys for taking the time to reply :smile:

@tannin I dont have an anti-virus software other that the basic ms defender, just as Grestorn.

@grestorn I tried that with no success.

The scroll-down option "Diagnostic files" is what shows the log right?

Ill just paste the log here as I'm unable to deduct whats wrong myself:

 

Fri, 20 Apr 2018 23:09:24 GMT - info: Vortex Version 0.14.1
Fri, 20 Apr 2018 23:09:24 GMT - info: using C:\Users\Jonas\AppData\Roaming\Vortex as the storage directory
Fri, 20 Apr 2018 23:09:25 GMT - info: python not found not found: python
Fri, 20 Apr 2018 23:09:28 GMT - info: python not found not found: python
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=settings_interface
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=settings_application
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=about_dialog
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=diagnostics_files
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=dashboard
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=starter_dashlet
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=firststeps_dashlet
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=mod_management
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=category_management
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=profile_management
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=nexus_integration
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=download_management
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=gamemode_management
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=symlink_activator
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=symlink_activator_elevate
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=hardlink_activator
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=updater
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=installer_fomod
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=installer_nested_fomod
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=settings_metaserver
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=test_runner
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=extension_manager
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=ini_prep
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=news_dashlet
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=sticky_mods
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=browser
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=common-interpreters
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=feedback
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=game-falloutnv
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=game-kingdomcome-deliverance
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=game-skyrimse
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=game-skyrimvr
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=game-teso
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=gamebryo-archive-invalidation
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=gamebryo-ba2-support
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=gamebryo-bsa-support
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=gamebryo-plugin-indexlock
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=gamebryo-plugin-management
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=gamebryo-savegame-management
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=gamebryo-test-settings
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=gameinfo-steam
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=local-gamesettings
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=meta-editor
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=mo-import
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=mod-dependency-manager
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=mod-highlight
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=modtype-dinput
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=modtype-dragonage
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=modtype-gedosato
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=mtframework-arc-support
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=nmm-import-tool
Fri, 20 Apr 2018 23:09:30 GMT - info: init extension name=open-directory
Fri, 20 Apr 2018 23:09:30 GMT - info: all extensions initialized
Fri, 20 Apr 2018 23:09:30 GMT - info: register protocol protocol=nxm
Fri, 20 Apr 2018 23:09:30 GMT - info: register protocol protocol=http
Fri, 20 Apr 2018 23:09:30 GMT - info: register protocol protocol=https
Fri, 20 Apr 2018 23:09:30 GMT - info: found game location=D:\Games\SteamLibrary\steamapps\common\Skyrim Special Edition\, name=Skyrim Special Edition
Fri, 20 Apr 2018 23:09:30 GMT - info: changed game mode newMode=skyrimse
Fri, 20 Apr 2018 23:09:30 GMT - info: read font D:\Games\Vortex\resources\app.asar\assets\fonts\icons.svg
Fri, 20 Apr 2018 23:09:32 GMT - info: updated loot masterlist false
Fri, 20 Apr 2018 23:09:35 GMT - info: set channel
Fri, 20 Apr 2018 23:09:38 GMT - info: no update available

 

 

The only thing that looks a bit odd to me is the first line:

info: using C:\Users\Jonas\AppData\Roaming\Vortex as the storage directory

 

as that directory doesn't exist.

btw. it is when enabling mods i get the error mentioned before, not when installing.

Edited by Arlaug
Link to comment
Share on other sites

Diagnostics files will show different "sessions". Each session is from the time you started vortex to where you closed it. What you send is presumably the latest, still running, session at the time you copied it. Nothing happened there.

What we need is the session where the error occured.

 

But you can also just go to "Send Feedback" and under "Attach special file" select "Vortex Log" which will attach 1-2 MB of logs which will usually contain a day or two - meaning you still have to do it reasonably shortly after the error occured, not days later.

Link to comment
Share on other sites

same exact issue, except I'd like to add I've never gotten a mod to deploy. I also noticed there are several processes named vortex, under the primary vortex process, not sure if that is supposed to happen or if there are multiple instances running, and it is these multi instance that is locking the files for deployment. I just submitted a feedback file with everything there was a drop down item for.

Link to comment
Share on other sites

@DrifingEvil: Interesting, I haven't seen a report like this yet.

The error messages you get are


failed to link error=EISDIR: illegal operation on a directory, link F:\Mods\skyrimvr\mods\SMIM SE 2-07-659-2-07\textures\smim\furniture\smelter\smim_smelter_dome_n.dds' -> 'F:\SteamLibrary\steamapps\common\SkyrimVR\data\textures\smim\furniture\smelter\smim_smelter_dome_n.dds

 

 

This would indicate that F:\Mods\skyrimvr\mods\SMIM SE 2-07-659-2-07\textures\smim\furniture\smelter\smim_smelter_dome_n.dds or F:\SteamLibrary\steamapps\common\SkyrimVR\data\textures\smim\furniture\smelter\smim_smelter_dome_n.dds

is a directory, could you check if that is true?

If the path in f:\mods is actually a directory, that would indicate Vortex already messed up somehow when installing the mod, if the path in f:\steamLibrary is a directory it would indicate a previous deployment went wrong.

 

If not, is F: a regular hard disk or is there anything "unusual" about it, like is it a network drive or encrypted or something like that? Or are you using junction points/links in your game directory or in f:\mods?

Link to comment
Share on other sites

'F:\SteamLibrary\steamapps\common\SkyrimVR\data\textures\smim\furniture\smelter\'

 

 

is an 'empty folder' with a files named __delete_if_empty in it.

 

I am using an external SSD, I am not sure if it self-encrypts or anything odd like that, it might but. Looking through the properties there is nothing obvious. Its a SanDisk Extreme 500, which comes with encryption software, but I didn't intentionally encrypt it. So nothing else that might be odd.

 

How do I completely uninstall Vortex? I've uninstalled it a couple of times and tried to wiped out everything to do a totally clean reinstall, but it always finds the previous preferences.

 

 

 

edit: I also noticed that even with I try to uninstall all mods (via vortex), the splash screen says there are still '4 active mods'

 

 

also tried again, this time only deploying the unofficial patch. Still no luck on deployment and I submitted everything again. Time is ~544GMT incase there's a pile of submissions.

Link to comment
Share on other sites

Is it possible your external SSD is an exFAT filesystem? To find out, open your start menu and type "diskmgmt.msc" and check the "File System" Column alongside your F partition.

 

If so I'm afraid there isn't a solution right now, the Vortex alpha only works on NTFS partitions because exFAT doesn't support any form of hard/soft links.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...