It's just a troubleshooting step, we're not keeping it that way. It seems the solution is probably to follow the advice to install MO outside of program files. Issue closed? Unless we feel like hunting this one down, just to make sure there's not a legit underlying issue.
Nah, something's broken and now we have repro steps, so hopefully it'll be a simple fix. Having MO2 out of Program Files will work as a workaround until another release happens, though. Is it the same problem? There's an issue where Wine doesn't know we need the. NET framework 4. AnyOldName3 so, I was able to install. That's definitely a WINE problem rather than a me problem. Presumably, they're already tracking the lack of 4.
I don't actually, see any open bugs about 4. I just googled the last line of the error and a vaguely similar issue report for different software said that the only supported way to install the. Hey, I fixed this by installing dotnet 4. It gives me this error:. Updated 2. NetFrameworks installed, ndp48 couldn't install because "newer one" already installed. Issue occurred. Downloading MO 2. I experienced same error on Windows 10 Mod Organizer version 2. Suspecting file access privileges changes after starting with admin privileges for the first time causing the issue.
Suspecting file access privileges changes after starting with admin privileges causing the issue. Can confirm that launching in Admin mode resolves the issue for me too, but still throws the error any time I run without admin privileges. Don't start broken software in admin mode. That's like giving a toddler who's shot you with a nerf gun an assault rifle. As for the requires-admin-when-MO2-is-installed-to-program-files issue, it's resolved in the 2.
That's a different issue to this issue, but sounds like it does need fixing. I don't know if it's on our end or theirs, or whether it's just that you've not configured MO2 appropriately for when it's installed into program files. If the Enderal team are telling you to use that as a solution rather than a quick test to diagnose the problem, I'd be inclined to say the problem's on their end as it's something only a moron would suggest as a permanent solution, and morons are much more likely to write software that interacts badly with UAC.
Just in case, though, you should probably check your MO2 is set up right for being installed in Program Files which is potentially fiddly and we explicitly recommend against putting it in Program Files. If it's in instanced mode, it's probably fine, as all the important data lives in AppData. If it's in portable mode, though, the default paths will be wrong, as portable mode expects MO2 to be put in a directory its got permission to edit, and it's not got permission to edit Program Files.
You can change several of the path settings in the Paths tab of the Settings window, and make it use writable directories instead if you haven't already. I couldn't find the post I referenced as the instruction to run MO2 with admin privileges yet, I'll post when it do. EDIT: okay, I've stated wrong. I think the launcher checks if the ini has the same setting as in the launcher. I made an extrapolation error to run MO2 with admin privileges for the sake of having launcher started with admin privileges.
Although it does fix the problem with settings in the game. Side question: so I'm most probably a moron cuz running it with admin privileges, is overdev still a moron too?
Their launcher shouldn't need to be started with admin permissions if none of the files it works on are restricted to admins. Do you maybe accidentally have that whole drive or at least the Games directory restricted? What do you mean by restricted? In any way, most probably not. As I've stated in reproduction steps comment , the issue appears only if MO2 is started with admin privileges, it works properly until that moment.
That's it. That is the issue. Mod Organizer installs itself without giving itself permission to write to its own folders. It's an easy fix which isanae Holt59 Al12rs LostDragonist can probably be integrated into the installer automatically. I installed mine in Program Files. And the guy I am quoting installed his in another drive. Putting a portable instance in program files is absolutely not supported. There are a bazillion potential permissions issues that could cause, and working around them can introduce security holes, so we're definitely not going to meddle with permissions in Program Files.
With a normally-configured Windows machine, users should already have full control of arbitrary loose directories in the root of the boot drive provided those directories don't have explicit protection like Program Files does , so there should be no need for the installer to explicitly set that up. Do you perhaps have a non-default setting that changes this? Already have an account? Sign in here. By using this site, you agree to our Terms of Use.
Search In. Sign in to follow this Followers 0. How to Un-hide Hidden Files? Asked by drift mod organizer. Question drift 0. Posted August 20, Share this post Link to post Share on other sites. Recommended Posts. LostDragonist 0. Posted August 20, edited. Edited August 20, by LostDragonist. Thanks it works. 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.
Register a new account. Sign in Already have an account? Home Discussions Workshop Market Broadcasts. Change language. Install Steam. Store Page.
It is only visible to you. If you believe your item has been removed by mistake, please contact Steam Support. Current visibility: Hidden. This item will only be visible to you, admins, and anyone marked as a creator.
Current visibility: Friends-only. This item will only be visible in searches to you, your friends, and admins. This is a guide on how to both run and mod Skyrim SE. This is taken from my experience searching for hours just to get SKSE 64 installed and may vary if you use a different distribution.
In my case I used Linux Mint This item has been added to your Favorites. Created by.
0コメント