Jump to content

Skyrim Classic - Failed Vortex Modpack Creation - Help Needed

Recommended Posts

So I originally posted the issues I'm having on here: https://github.com/Nexus-Mods/Vortex/issues/6746#issuecomment-650975164 though I felt the guy was being a bit...I guess he thought I was a simpleton or something, but the responses didn't help me at all. I haven't run anything in administration, because that's a risky step and I'd rather thoroughly understand and fix the actual problem rather then mask it over. 


1. I tried following the gentleman's instruction by adding FNIS as a Tool with the "Add Tool" option found on the Vortex Dashboard; Vortex is still reading FNIS as uninstalled and fails to run tool on deployment altogether.


2. The gentleman didn't specify where I could start on a Windows 10 computer on how to find what's blocking the Vortex Mod Manager files, if that's the case; so I need something to go off of here, telling me it's not Vortex's fault doesn't help me. Like a student trying to understand, I need someone to just simplify an explanation for me, guiding me to understand where my fault was so I not only fix the error but don't replicate it again in the future. If I can be pointed in the right direction on file locations or option in my computer, that'd be very appreciative and I won't be so inclined to ask fifty-million questions of exhaustive effort and the link posted on that forum does content pictures I took containing my computer information and the issues experienced.


3. If it was a virus gained from downloading mods, which I usually download ones saying they're safe typically, how do I protect my Vortex/computer in the future? Are there signs to detect if a mod was shady? I do run actively on my computer Malwarebytes Premium and it didn't detect anything, so why my computer would "lock out"/"block" the Vortex from permissions is heavily confusing me.


4. Is there preferences I should edit in my computer somewhere to negate Windows 10 from blocking program permissions? I know this is common sense to some people, but I'm pretty technologically illiterate so please don't be too harsh or exasperated with me :)


5. Does anyone know how to get rid of that blasted blank file stuck in my Downloads folder ;(


Thank you everyone who responds, I deeply appreciate the feedback!



Share this post

Link to post

I believe the root cause of most of your issue is because you installed Skyrim in C:\Program Files (x86). This folder and C:\Program Files are protected so regular users cannot create or modify files in this folder. It's rather unfortunate that Steam defaults the install path to C:\Program Files (x86), but you can find instructions on Steam explaining how to move games to another folder so I would follow these instructions to move Skyrim to a folder that is not protected (say something like C:\SteamApps).

Share this post

Link to post

I've uninstalled everything including steam, and am going to attempt installing everything onto my Desktop to prevent anymore of this "blocking" triggers from Windows 10.


1. I made a new folder on my Desktop, called it Steam, and installed Steam into it.


2. I made a new folder acting as a sub-folder in the Steam Folder, called it Vortex, and placed it in the Steam Folder.


3. Installed Skyrim Script Extender and then Skyrim (Steam), checking both as they're installed to make sure they're not being put in C:\Program Files (x86).


4. I noticed the Desktop icons for SKES and Skyrim were blank, though checking all the folders on Desktop, everything re-installed fine.


5. Downloaded and installed the latest version of Vortex into the Vortex sub-folder located inside the Steam Folder on Desktop.


6. Noticed while doing all of this, the finished installed Skyrim seemed to be stuck in a Validating step for 15-20 minutes, with the Desktop icons for SKES and Skyrim still being blank (like as if incomplete), so going to restart laptop after this to see what happens.

Share this post

Link to post

Restarted, and everything looks fine now; everything installed perfectly, and the icons are normal now on the Desktop. Hopefully when I go to create a modpack now on Vortex, I won't run into this bizarre issue again, but thank you so much for the feedback!

Share this post

Link to post
This topic is now closed to further replies.
  • Similar Content

    • By TechAngel85
      Discussion topic:
      Particle Patch for ENB by mindflux
      Wiki Link
    • By TechAngel85
      Discussion topic:
      Majestic Mountains by T4gtr34um3r
      Wiki Link
      z929669 - Vote to stick with lightside per screens posted below
      Compares from z929669
      Conditions: clear weather, all mod conditions used LODGen applicable to vanilla mountains, MM, MM Darkside, and MM Lightside (so LOD is specific to each of the four sets of screenshots)
      TOD: noon
      Coordinates (cow tamriel): Whiterun lookout tower WSW > 35 -16 > -33 -7 > -10 0
      Mod build: Step 2.0.0 (dev)
      Step (vanilla mountains)  >  MM  >  MM Darkside  >  MM Lightside
      Load up imgbox gallery and cycle through all images to load them. Then use the arrow buttons to toggle back and forth. Images aren't a perfect overlay, due to slight variations in COW positioning but close enough. They can also be examined directly in the spoiler.
    • By sheson
      DynDOLOD DLL for Skyrim, Skyrim Special Edition, Skyrim Anniversary Edition and Skyrim VR
      So far all versions of DynDOLOD use the SKSE plugin PapyrusUtil for the optional dynamic LOD in the game. Starting with version 2.45 there is now the alternative DynDOLOD DLL available.
      The current DLL version is 2.45. It works with dynamic LOD generated by DynDOLOD Standalone 2.45 and newer.
      Read the ..DynDOLOD\Docs\DynDOLOD_DLL.html included in DynDOLOD Standalone for an explanation about DynDOLOD DLL, installation instructions (overwrite papyrus scripts of DynDOLOD Resources) and how it works.
      If there are problems with it, check DynDOLOD_DLL.html and the DynDOLOD FAQ first before posting.
      If a DynDOLOD.DLL version is required for a game version that is not listed below, request it in this thread. First, search this thread if it has been requested already, though. The future will tell how long it takes to release updates.
      Typically a new DynDOLOD.DLL is required for each new game version, but not each new SKSE version. For example a DynDOLOD.DLL compiled with SKSE64 2.0.9 also works with SKSE64 2.0.10 for the same game version.
      Nexus Downloads for DynDOLOD 2.45 and higher
      DynDOLOD DLL for Skyrim
      DynDOLOD DLL SE for Skyrim Special Edition
      DynDOLOD DLL VR for Skyrim VR
      Mega Mirrors:
      DynDOLOD.DLL + Scripts for Skyrim 1.9.32 (overwrite the papyrus scripts included in DynDOLOD Resources)
      DynDOLOD Scripts for Skyrim Special Edition and Skyrim VR (overwrite the papyrus scripts included in DynDOLOD Resources SE)
      DynDOLOD.DLL for Skyrim Special Edition 1.5.39
      DynDOLOD.DLL for Skyrim Special Edition 1.5.50
      DynDOLOD.DLL for Skyrim Special Edition 1.5.53
      DynDOLOD.DLL for Skyrim Special Edition 1.5.62
      DynDOLOD.DLL for Skyrim Special Edition 1.5.73
      DynDOLOD.DLL for Skyrim Special Edition 1.5.80
      DynDOLOD.DLL for Skyrim Special Edition 1.5.97
      DynDOLOD.DLL for Skyrim Special Edition 1.6.318
      DynDOLOD.DLL for Skyrim Special Edition 1.6.323
      DynDOLOD.DLL for Skyrim Special Edition 1.6.342
      DynDOLOD.DLL for Skyrim Special Edition 1.6.353
      DynDOLOD.DLL for Skyrim Special Edition 1.6.629
      DynDOLOD.DLL for Skyrim Special Edition 1.6.640
      DynDOLOD.DLL for Skyrim Special Edition GOG 1.6.659 (untested)
      DynDOLOD.DLL for Skyrim VR 1.4.15
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.