search

Nexus-Mods / Vortex

Vortex Development
GNU General Public License v3.0
917 stars 135 forks source link

error: System.UnauthorizedAccessException #12669

Closed VortexFeedback closed 2 years ago

VortexFeedback commented 2 years ago

Application error

System
Platform win32 10.0.19044
Architecture x64
Application Version 1.6.5
Process renderer

Message

System.UnauthorizedAccessException

Title

Failed to install dependency

Context

gamemode = Skyrim Special Edition,Downloading "Glorious Doors of Skyrim SE-32376-1-03-1584773006.7z" = nxm://skyrimspecialedition/mods/32376/files/129655?campaign=collection,Downloading "HD Reworked Blended Roads 4k-63674-1-0-1644933549.rar" = nxm://skyrimspecialedition/mods/63674/files/264408?campaign=collection,Downloading "Honed Metal AE-61015-1-22-RC4-1642948811.7z" = nxm://skyrimspecialedition/mods/61015/files/258896?campaign=collection,Installing = FlowerGirls SE and VR Main File-5941-3-0-2-1566171791

Stack

   at Microsoft.Win32.SafeHandles.SafeFileHandle.CreateFile(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options)
   at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize)
   at System.IO.Strategies.OSFileStreamStrategy..ctor(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize)
   at System.IO.Strategies.FileStreamHelpers.ChooseStrategyCore(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize)
   at System.IO.Strategies.FileStreamHelpers.ChooseStrategy(FileStream fileStream, String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, Int64 preallocationSize)
   at System.IO.File.ReadAllBytes(String path)
   at Utils.FileSystem.ReadAllBytes(String filePath)
   at FomodInstaller.Interface.Mod.<>c__DisplayClass27_0.<GetScriptFile>b__0()
   at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
   at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
   at FomodInstaller.Interface.Mod.GetScriptFile(Boolean validate)
   at FomodInstaller.Interface.Mod.Initialize(Boolean validate)
   at FomodInstaller.ModInstaller.Installer.Install(List`1 modArchiveFileList, List`1 stopPatterns, String pluginPath, String scriptPath, Object preset, Boolean validate, ProgressDelegate progressDelegate, CoreDelegates coreDelegate)
   at CallSite.Target(Closure , CallSite , Object )
   at ModInstallerIPC.Server.DispatchInstall(String id, JObject data)
   at ModInstallerIPC.Server.Dispatch(String id, JObject data)
   at ModInstallerIPC.Server.<>c__DisplayClass24_0.<<OnReceived>b__1>d.MoveNext()

Reported from:
Error
    at showError (C:\Program Files\Vortex\resources\app.asar\renderer.js:9295:202)
    at mApi.showErrorNotification (C:\Program Files\Vortex\resources\app.asar\renderer.js:8338:123)
    at C:\Program Files\Vortex\resources\app.asar\renderer.js:4366:102
    at tryCatcher (C:\Program Files\Vortex\resources\app.asar\node_modules\bluebird\js\release\util.js:16:23)
    at Promise._settlePromiseFromHandler (C:\Program Files\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:547:31)
    at Promise._settlePromise (C:\Program Files\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:604:18)
    at Promise._settlePromise0 (C:\Program Files\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:649:10)
    at Promise._settlePromises (C:\Program Files\Vortex\resources\app.asar\node_modules\bluebird\js\release\promise.js:725:18)
    at _drainQueueStep (C:\Program Files\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:93:12)
    at _drainQueue (C:\Program Files\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:86:9)
    at Async._drainQueues (C:\Program Files\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:102:5)
    at Async.drainQueues (C:\Program Files\Vortex\resources\app.asar\node_modules\bluebird\js\release\async.js:15:14)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)

Reported by: ganayem

IDCs commented 2 years ago

Your system is blocking Vortex's fomod installer from creating files - could be a security policy or an anti-virus. Regardless this is something you need to fix on your machine, not a Vortex bug.

TanninOne commented 2 years ago

@IDCs this is likely caused by the new implementation of the security sandbox in 1.6, not by any security settings the users made.

ganayem: you seem to be the only user so far who had this problem. Is there anything unusual about your system you can think of? Have you intentionally changed security settings? Is the system administrated by someone else (like a workstation at a school or university)? Have you updated from another windows version (win 7, 8, 10S, anything like that) to your current one?

Finally: could you go to settings->Workarounds, disable the "Installer Sandbox", restart Vortex and try installing the mods again?

Please do update us on whether this was successful. You are in a very small group where this doesn't work and if we're to fix/improve anything we do need feedback from those affected.

ganayem commented 2 years ago

Hi Disabling "Installer Sandbox" and restart solved my problem. Thank you for your interest.

IDCs commented 2 years ago

@ganayem thanks for confirming. Could you please let us know if there is anything unusual about your system you can think of? Have you intentionally changed security settings? Is the system administrated by someone else (like a workstation at a school or university)? Have you updated from another windows version (win 7, 8, 10S, anything like that) to your current one?

ganayem commented 2 years ago

Hi My system is working normally in all respects. I am using Windows 10 pro and I have all the administration. I did not change any system security settings. This is my home computer which is not upgraded from any older version of windows. Also I use Kaspersky free as an antivirus is enabled all the time.

IDCs @.***>, 12 Ağu 2022 Cum, 14:11 tarihinde şunu yazdı:

@ganayem https://github.com/ganayem thanks for confirming. Could you please let us know if there is anything unusual about your system you can think of? Have you intentionally changed security settings? Is the system administrated by someone else (like a workstation at a school or university)? Have you updated from another windows version (win 7, 8, 10S, anything like that) to your current one?

— Reply to this email directly, view it on GitHub https://github.com/Nexus-Mods/Vortex/issues/12669#issuecomment-1212997146, or unsubscribe https://github.com/notifications/unsubscribe-auth/AI4232FYBKNMEAIKVDBOFMTVYYWO3ANCNFSM56GBKP6A . You are receiving this because you were mentioned.Message ID: @.***>

IDCs commented 2 years ago

Hi @ganayem would you be willing to run a small experiment? Could you temporarily disable your AV and re-enable "Installer Sandbox" and see if you still get the Unauthorized Access Exception ?

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 15.65 GB System: win32 x64 (10.0.22000) Somehow reinstalling Super Mutant Redux worked for me

Reported by: Fantorius

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 31.95 GB System: win32 x64 (10.0.19043) ill try thanks for the fast response!!

Reported by: ChurchOfFuu

ganayem commented 2 years ago

Hi I did what you asked me to do. I got the same access errors I think antivirus software has nothing to do with the problem.

Avyzzvaith commented 2 years ago

Hi there, decided to post here beside closed feedback channel Im here with the same error, im running win 11, normal home user, no changes in system security, meaning only AV im using is untuched Windows Defender, never had any viruses or problems of this kind before. It seems access error is applying only to mods with FOMOD installers, I tried your workaround by dissabling "Installer Sandbox" and reloading Vortex it worked for installation but now I cant run deployment as it shows the error (1392) telling me that there is something wrong with my drive or AV settings. Im running game and modfolder on external drive while vortex is installed on different drive, it was working fine before updating Vortex. Error message tells me you wont be providing any feedback about this, but I can only assure you that I installed around 370 mods with no problems and I did no changes to my settings or any updates to Windows in last few days. My drives are working just fine I can open any file just as usual. New Error file underneath. Right now im almost unable to do anything with modlist.

UPDATE: after two hours i got rid of error (1392) it looks like turning off and on "Installer Sandbox" blocked (or something similar) some files, in my case from mod in my screenshot....after few pc and external drive reloads windows showed message about need to repair files on drive and opened auto repair tool. NOTICE: Main error "UnauthorizedAccessException" is still here with "Installer Sandbox" enabled, can install Fomod mods only with this option disabled.

(702)_edited

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 31.92 GB System: win32 x64 (10.0.19044) by AV you mean anti virus? I dont have any third party AV installed just have the default windows 10 virus protection actived.. so you suggest I should turn that off and then re-enable installer sandbox, correct? how do I reenable installer sandbox?

Reported by: LITOSDV

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 15.81 GB System: win32 x64 (10.0.22000) I disabled the anti-virus, installer sandbox was already enabled, still getting the error

Reported by: luketheguy

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 15.85 GB System: win32 x64 (10.0.19044) Deactivating AV did not help, only keeping Installer Sandbox off did. One thing that I did notice is that the problem did not seem to occur for me regardless of AV and Installer Sandbox settings with a mod without a fomod.

Reported by: Lord1

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 15.92 GB System: win32 x64 (10.0.22000) Hi, here with the same and one more error, im running win 11, normal user no changes in system security, meaning only AV im using is untuched windows defender, never had any viruses or problems of this kind before. It sems error is applying only to mods with FOMOD installers, i tried your workaround by disabling "Installer Sandbox" and reloading Vortex, it worked but now i cant run deployment, it shows me error "1392" attached in file, telling me that there is something wrong with my drive or AV settings. Im running game and mod folder on external drive while vortex is installed on different drive, it was working fine before todays update. Error message tells me that you wont be giving me any feedback about this and I just want to assure you that my drives are in good shape im using them all time, installed above 300 mods allready with no problems and i did no updates or changes in system settings in a few days so i dont think its my fault now.

External file: tmp-89523vl89osFyn2r.7z

Reported by: Avyzzvaith

TanninOne commented 2 years ago

This is a real head-scratcher. Based on the logs I've seen in all cases Vortex has granted access to the sandbox to read the installer files, gets a success result from windows and then when the installer actually tries to access one of them, the sandbox refuses access.

The code fundamentally works for the majority of users and as I said: There is no error when we try to grant access, it just doesn't seem to work on your system.

Without any indication of what might be wrong I'm not really sure what to do with this beyond telling you to disable the sandbox.

FrostTheSheikah commented 2 years ago

This has recently happened to me as well with the only things having changed recently being the Vortex update and the .Net needed to be installed. I should like to mention that not every mod fails actually most work just fine it's just some mods seem to fail like this.

FrostTheSheikah commented 2 years ago

To be added yes disabling Sandbox installer did fix my issue with this I just hope there is no future issues that will be caused by me disabling this.

TemperedReaper commented 2 years ago

I'm having this issue now, too and my XP32 Skeleton mod is failing installation. I've disabled Installer Sandbox, but the installation of the mod I'm targeting has continued to fail. Do I need to restart my system to fix this issue post disabling the Sandbox?

Noah2236 commented 2 years ago

I am having this issue as well; mostly same as above, with some potential extra information that may or may not help.

1) The Sandbox disable that was recommended did not work. 2) I use an external Drive. 3) This started today after the .NET install/update. 4) The windows 6.0.6 for tools and extensions is sitting in my Downloads on Vortex and wont install. 5) After installing the .NET update, Vortex asked me about saving file changes in reference to Purging Mods, but since I had not done/approved such a thing, I had the files reverted. This seemed to exacerbate the issue. 6) None of my systems or user account settings have been changed in any way. 7) I run a large amount of Mods. 8) I have another error sitting in my vortex issues, its a too many files open error, feedback number is #11284.

I know nothing about code, but I made a Github to add all of this in case any of this information may help someone figure out a solution since I have no idea what happened; everything was perfect yesterday, and now I can't play modded at all, so I will now sit on my hands and hope a solution comes quickly, thank you!

TemperedReaper commented 2 years ago

I was able to install a updated mod that had its installation failed thanks to this particular issue once I disabled the Sandbox, but, for now, I'm Moy installing any more or updating any mods.

On Sat, Aug 20, 2022, 3:45 PM Noah2236 @.***> wrote:

I am having this issue as well; mostly same as above, with some potential extra information that may or may not help.

  1. The Sandbox disable that was recommended did not work.
  2. I use an external Drive.
  3. This started today after the .NET install/update.
  4. The windows 6.0.6 for tools and extensions is sitting in my Downloads on Vortex and wont install.
  5. After installing the .NET update, Vortex asked me about saving file changes in reference to Purging Mods, but since I had not done/approved such a thing, I had the files reverted. This seemed to exacerbate the issue.
  6. None of my systems or user account settings have been changed in any way.
  7. I run a large amount of Mods.
  8. I have another error sitting in my vortex issues, its a too many files open error, feedback number is #11284 https://github.com/Nexus-Mods/Vortex/issues/11284.

I know nothing about code, but I made a Github to add all of this in case any of this information may help someone figure out a solution since I have no idea what happened; everything was perfect yesterday, and now I can't play modded at all, so I will now sit on my hands and hope a solution comes quickly, thank you!

— Reply to this email directly, view it on GitHub https://github.com/Nexus-Mods/Vortex/issues/12669#issuecomment-1221405827, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2TBQFU62CHHX5X4J4PAHNDV2E7W7ANCNFSM56GBKP6A . You are receiving this because you commented.Message ID: @.***>

GwynnGunawan commented 2 years ago

Same here. After the .net update my entire mod list was redundant so I'm installing them again from the procedure I've used before but at my skeleton as well the error (see below): None of my permissions or settings have changed (unless .net changed them for me). All >100 mods used to work like a charm. I don't even know (and google doesnt tell me) how to disable a sandbox or where to find it.

Edit: Found it and it solved it .. for now

at Microsoft.Win32.SafeHandles.SafeFileHandle.CreateFile(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options) at Microsoft.Win32.SafeHandles.SafeFileHandle.Open(String fullPath, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize) at System.IO.Strategies.OSFileStreamStrategy..ctor(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize) at System.IO.Strategies.FileStreamHelpers.ChooseStrategyCore(String path, FileMode mode, FileAccess access, FileShare share, FileOptions options, Int64 preallocationSize) at System.IO.Strategies.FileStreamHelpers.ChooseStrategy(FileStream fileStream, String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, Int64 preallocationSize) at System.IO.File.ReadAllBytes(String path) at Utils.FileSystem.ReadAllBytes(String filePath) at FomodInstaller.Interface.Mod.<>cDisplayClass27_0.b0() at System.Threading.Tasks.Task.InnerInvoke() at System.Threading.Tasks.Task.<>c.<.cctor>b272_0(Object obj) at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location --- at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(Thread threadPoolThread, ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread) --- End of stack trace from previous location --- at FomodInstaller.Interface.Mod.GetScriptFile(Boolean validate) at FomodInstaller.Interface.Mod.Initialize(Boolean validate) at FomodInstaller.ModInstaller.Installer.Install(List1 modArchiveFileList, List1 stopPatterns, String pluginPath, String scriptPath, Object preset, Boolean validate, ProgressDelegate progressDelegate, CoreDelegates coreDelegate) at CallSite.Target(Closure , CallSite , Object ) at ModInstallerIPC.Server.DispatchInstall(String id, JObject data) at ModInstallerIPC.Server.Dispatch(String id, JObject data) at ModInstallerIPC.Server.<>cDisplayClass24_0.<b__1>d.MoveNext()

TanninOne commented 2 years ago

you may have to restart Vortex after toggling the sandbox in 1.6.7. Once 1.6.8 is out that restart shouldn't be necessary any more.

TemperedReaper commented 2 years ago

Yeah, once I restarted Vortex everything appeared to be back to normal for the most part.

Have they identified this as a problem and do have a plan to fix in 1.6.8?

On Mon, Aug 22, 2022, 1:28 AM TanninOne @.***> wrote:

you may have to restart Vortex after toggling the sandbox in 1.6.7. Once 1.6.8 is out that restart shouldn't be necessary any more.

— Reply to this email directly, view it on GitHub https://github.com/Nexus-Mods/Vortex/issues/12669#issuecomment-1221902729, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2TBQFWJV5MIBTHO6OAZYDTV2MMYTANCNFSM56GBKP6A . You are receiving this because you commented.Message ID: @.***>

TanninOne commented 2 years ago

@TemperedReaper Unfortunately we haven't found out anything that would explain why this is happening. I've been in contact with Microsoft about a similar issue with the sandbox and their response was basically the same as our initial one: "What's the AV? What's unusual about the system of the affected users?". Another thing that may be relevant: How do you start Vortex? As in: Do you start it "manually" from the start menu or desktop or have you set it to start with windows or do you start it by starting a download in the web browser when Vortex isn't running already? Do you use "runas" to run Vortex with a different account? Are there any compatibility settings on the Vortex.exe (right click it -> properties -> compatibility. Please check, windows might enable some of these automatically without you noticing)

The sandbox (which is a windows feature, not our creation nor is it part of .NET btw) has undocumented dependencies/restrictions on the environment (your system configuration, security software, drivers, something like that) that even Microsoft themselves can't give us a list of. So we're basically taking stabs in the dark trying to figure out why/how your system is different from the 99% of our users where this feature works. Once/If we find out what the cause is, maybe we can implement a fix. This is not suggesting it's your own fault btw., the documentation of this functionality is simply awful. Whatever it is that sets your system apart may be perfectly reasonable but it has to be quite uncommon.

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 15.92 GB System: win32 x64 (10.0.19044) I open Vortex through my desktop

Reported by: Timewalker42

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 15.89 GB System: win32 x64 (10.0.19043) I redownloaded vortex from the website and no longer got the issue, so fairly certain it was an update that broke it. I have not been updating vortex and been able to download and use mods without getting that error. I start Vortex manually and I only have one account on the computer and it has admin privileges.

Reported by: alejeron

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 15.84 GB System: win32 x64 (10.0.19043) Ok thanks, I'll have a look on my end too :)

Reported by: isg70

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 15.85 GB System: win32 x64 (10.0.22000) I fixed it by removing and going through my mod list one by one

Reported by: deathknightt

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 15.77 GB System: win32 x64 (10.0.22000) All good, answering the questions: this is only a problem with a particular mod I start vortex from the start menu/desktop manually, (from the shortcut) I don't use runas, nor know what it is Compatibility is normal, vortex is running in normally with compatibility mode for windows 8 (running windows 11)

My system used to work normally. Although I may have a lead to where the problem originated from

The external SSD drive I have the the game and mod installed has form time to time problems in which it suddenly desconnects and reconnects back, but one time I decided to use the option to repair the drive to fix any possible errors. Later, I decided to reinstall the mod which was running perfectly but just wanted to select a different option in the installation wizard, so it would have compatibility with another mod. The moment it uninstalls it and installs it suddenly that error popped up. The only thing that changed was the repair of the drive which maybe windows made changes to permissions of vortex and/or the file types (if read only, etc).

Although no important issue as it is only with that one mod.

Reported by: PanzerTanker3000

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 31.78 GB System: win32 x64 (10.0.22000) I've actually come to fix my issue but more so on the end of avoiding it I suppose. My main files and mod files were in separate drives; one external and one internal. What's weird is that it worked fine before but recently gave me issues. After installing my game files and mod files into just the one internal drive everything was fine. I am unable to understand what you mean by Microsoft' sandbox tool as I tried looking for it but could find it in my system. To maybe help you get a clearer picture on this, all my settings were set to default as I went through a whole system reset to figure this out and I still had the issue. Maybe it has to do with having files downland in two separate drives? idk. Regardless, thank you for taking the time to look into it and hopefully the issue can be solved at some point.

Reported by: InsaneMose8D

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 7.98 GB System: win32 x64 (10.0.19044) I haven't changed my method of starting vortex, just starting it up from desktop, though. I'm also going to keep trying as well to see if I can jerry-rig a solution too

Reported by: GreyGrenade

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 7.34 GB System: win32 x64 (10.0.22000) Hello and thank you for responding, I usually start vortex through the short cut on my home screen and one of the few things I can think of that might have cause the problem is I use a external hardrive but even if its what's causing the problem I'm not sure why its now stopped working since its worked before but I hope some of this information has helped.

Reported by: SullenMWeasel

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 15.74 GB System: win32 x64 (10.0.19043) I think my firewall blocked the download. Odd that's its only certain ones.

Reported by: tdferg3654

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 39.93 GB System: win32 x64 (10.0.19044) the issue for me was resolved by turning off the sandbox option in the workarounds tab.

Reported by: armizinsanity

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 31.92 GB System: win32 x64 (10.0.19044) hello, I managed to fix it by turning off sandbox mode in vortex settings

Reported by: LITOSDV

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 15.93 GB System: win32 x64 (10.0.19043) I don't get what it says.

Reported by: Pommpeii

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 31.95 GB System: win32 x64 (10.0.19043) it must have been the install location, it was on my primary drive in one of the program files folders, i simply reinstalled elsewhere and it was fixed.

Reported by: dragonmetal6

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 15.87 GB System: win32 x64 (10.0.22000) I manually start vortex from my desktop taskbar.

Reported by: Jermologist

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 23.90 GB System: win32 x64 (10.0.19044) Hello. Thanks for the response. I start vortex manually from a desktop icon. I do not use runas (or even know what that is). No compatibility settings on Vortex. The issue only started after vortex recently updated. One thing that me be relevant. I run Vortex (and Steam) from an external drive as opposed to system one. But as stated, there has never been an issue before Sunday. Appreciate your attempts to assist.

Reported by: 112mark99

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 15.91 GB System: win32 x64 (10.0.19043) Everything is working correct with old Vortex versions (year 2020)

Vortex is started "manually" I don't use any "runas" to run Vortex No compatibility settings are enabled

I hate Microsoft docs too

Reported by: dayskachatmod

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 15.96 GB System: win32 x64 (10.0.19043) i kinda forgot what i send a report for but im guessing its for the problem i had when i updated to the new stable version of vortex and while most mods installed just fine some major ones just didnt work like the weapon mod menu for fallout new vegas as when i try to install it i got i think the error that said user.unathourizedacess or something similar ive reinstall a earlier version and it worked but any attept to update comes with the problem mention above, after messing around with adminb permission ( i know it said not to give admin priv but after trying with and without it makes no difference) and even making mutiple folder a exemption on window defender or even messing with red only settings, it seem a hard wipe could solve this. its not that big of a deal for me just kinda weird it happened. also idk much about system stuff but im running a dell optiplex 7010 something with window 10 so i dont think it should be to rare of a system and i start it by clicking a desktop icon

Reported by: emperiumon

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 15.88 GB System: win32 x64 (10.0.22000) Thank you for the response I have been searching for the problem for five days or so and have found a way to fix sorry for wasting your time. You have my sincerest apology.

Reported by: Cruelty2all

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 15.91 GB System: win32 x64 (10.0.19043) Everything is working correct with old Vortex versions (year 2020)

Vortex is started "manually" I don't use any "runas" to run Vortex No compatibility settings are enabled

I hate Microsoft docs too

Reported by: dayskachatmod

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 15.88 GB System: win32 x64 (10.0.22000) Tanks for the answer, I finally found the problem, it was about the file format that I had on the hard drive, I had an exFat file system and when I formatted it to NTFS it started to work fine.

Reported by: Daniell2000

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 15.96 GB System: win32 x64 (10.0.19043) i kinda forgot what i send a report for but im guessing its for the problem i had when i updated to the new stable version of vortex and while most mods installed just fine some major ones just didnt work like the weapon mod menu for fallout new vegas as when i try to install it i got i think the error that said user.unathourizedacess or something similar ive reinstall a earlier version and it worked but any attept to update comes with the problem mention above, after messing around with adminb permission ( i know it said not to give admin priv but after trying with and without it makes no difference) and even making mutiple folder a exemption on window defender or even messing with red only settings, it seem a hard wipe could solve this. its not that big of a deal for me just kinda weird it happened. also idk much about system stuff but im running a dell optiplex 7010 something with window 10 so i dont think it should be to rare of a system and i start it by clicking a desktop icon

Reported by: emperiumon

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 15.88 GB System: win32 x64 (10.0.22000) Thank you for the response I have been searching for the problem for five days or so and have found a way to fix sorry for wasting your time. You have my sincerest apology.

Reported by: Cruelty2all

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 15.91 GB System: win32 x64 (10.0.19043) Cheers for your response,

I start vortex from a desktop shortcut, and my PC was a pre-build, with an external SSD where most my games were.

I did manage to fix it by finding the app data folder and creating an 'everyone' user and giving them full control (see attached screenshot)

External file: tmp-5332ODU5rw8W24T6.7z

Reported by: Lightswitch69

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 23.90 GB System: win32 x64 (10.0.19043) reverting off the beta version fixed it so all good

Reported by: cinnasnake099

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 15.70 GB System: win32 x64 (10.0.19044) I feel that this has been a once-off thing. It has never happened again and I'll be honest I can't even remember what I did to cause the conditions that led to this. Safe to say I can't replicate this.

I just checked the incident and I was installing an FO4 mod, not Skyrim. It was a weapon mod as well, not any of the mods referenced. I truly have no idea what went wrong. I rebooted my computer and ran Vortex before opening Nexus Mods. No problems ever since.

Reported by: wildfranky19

VortexFeedback commented 2 years ago

Vortex Version: 1.6.7 Memory: 7.91 GB System: win32 x64 (10.0.22000) i started having issues after the latest update. vortex changed my location of my mod folder so now i have to redownload everything.

Reported by: venomsn95