GrantSP

Thanks, I doubt it's a path-length limit issue then. hmm... wracking brain...

Sorry to break topic, but why is there a SKSE folder in the overwrite folder? After installing SKSE there should be nothing in that 'temp' folder. Whatever files are in it should either be moved to the mod that provided them or made into a new mod themselves. That is what you would do with the output from AV. After every operation by any tool check what is placed in the overwrite folder and deal with it appropriately then move on to the next step. On-topic. How exactly are you doing this step? 5. Go to AV directory and run the jar file. If you are navigating to the AV directory outside of MO then that is the reason for their absence.

Clearly there must be something different with either the steps you did/didn't take or the versions of software on your system or some other Windows control issue that is messing up the patcher. Software just doesn't refuse to work for someone whilst working for someone else. So, what is different between GamerPoet's setup and yours? Additionally, Neovalen probably knows more about the patcher than most, so perhaps a list of mods might be a good thing to provide. You can place them inside a spoiler tag like this: [spoiler] list [/spoiler]

I'm not 100% sure how effective the import feature of MO is but if you could check what is in your Data folder, NMM places files into this folder whereas MO does some magic and never touches it. If there are any remnants of mods from NMM left behind they will cause some issues. This is what should be in the Data folder: Also if you have subscribed to some mods on Steam, I suggest you make copies of those mods and then unsubscribe from Steam for the same reason as NMM, it will place mods into the actual Data folder also. It probably sounds like a lot of effort but believe me once you have your Skyrim Data folder cleared, you can add/remove/replace/update or whatever, and never need to fear that something has been irrevokeably stuffed up again.

Could you tell us which tutorial you followed and any steps you deviated from, if any? That way we can eliminate the obvious errors. I've seen this error message reported before, though not necessarily in this setting. The DSR page says to try the fixes listed here. Have you tried those steps?

It looks like the ENB inis are just the stock standard from 0.264. Have a look at installing a preset for ENB. I have only just started using them and they do come across as a little daunting to those that haven't seen them before. I don't class myself as a noob but even I had to look carefully to know what they are trying to do. Still learning about them BTW. I would suggest following this video by the STEP video master, GamerPoet. He has made an install video for RealVision and it works just fine even on my older gaming laptop. The only thing is it is for the 0.262 version of ENB, so you will need to remove the current files and install that. At least I think you should. I'm not 100% sure if RealVision works with 0.264. As for the other inis. I can't see anything leap out at me as out-of-place. Maybe someone else will see something. Hang in there, there is always a solution.

The selection of the server Nexus uses to download the mod to you is mod manager agnostic. ie. it makes no difference which you use as it is assigned on the browser side of things. You open the mod page, choose the file to download, Nexus does some backroom server assignment and then the browser launches the associated link and the program downloads it. But, you may have a selected server in MO overriding the server choice setup in your ModOrganizer.ini. In the MO Settings dialog under the Nexus tab do you have any servers listed in the right-hand listbox, 'Preferred Servers (Drag & Drop)'?

Ok, this is going to be a really out-of-left-field request. Could you post the exact locations of your Skyrim, Mod Organizer and the 'mods' folder of MO, as well as the name you assigned the AOS mod in MO. e.g. On my system it is this: Skyrim C:\Program Files (x86)\Steam\SteamApps\common\skyrim\Mod Organizer C:\Program Files (x86)\Mod Organizer\AOS mod in the 'mods' folder C:\Program Files (x86)\Mod Organizer\mods\Audio Overhaul for Skyrim 2\I'm just going on a hunch that the combined length of that path to these wav files may somehow exceed a limit. It is a long shot based on nothing but what can we lose?

@keithinhanoi When, and under which circumstances, should your hidden 'goat sound' be heard? I'm confused now. I can clearly see they are different files with differing filesizes, they do sound the same to me though as the AOS files. I'm assuming this is from that rogue audio layer being removed.

It might be good if you could also paste, or link to, your enbseries & enblocal ini files along with your skyrim inis from the MO profile folder you are using. The skse.ini should be minimal and there should be something like this in it: [Memory] DefaultHeapInitialAllocMB=768 ScrapHeapSizeMB=256

I think the only method(s) currently available will always be slightly cumbersome as keeping track of which mods you need is more of a user based task. The closest thing MO will provide is the 'modlist.txt' in each of the profile sub directories. ALL the mods INSTALLED are shown but any not used by that profile will be prefixed by an '-', whereas those used by the profile will have an '+'. It looks something like: -Hold Border Banners +No snow under the roof +Unknown Enchants +No Combat Boundaries and Unofficial Encounter Zone PatchBut as the names are of the installed mods you will still need to know that "Hold Border Banners" is the Hold Border Banners-43493-1-0.rar archive. When you get more obscure naming schemes that may prove tedious.

This isn't actually a wide issue, though for those that have it, that is of little consolation. Have you tried all the methods mentioned to resolve this? Changing the NMM version number, picking a different server? If so then yes, manual download is the only solution. My own theory is it is a rare mixture of chosen server with unusual mod name and NMM version number combination that only affects a small number of users. Totally untested, but in the lack of other answers what is there to go with.

A couple of things... Ditch NMM. You will always have difficulties if you install mods with NMM & MO. The entire design of MO is to keep the Skyrim Data folder free of clutter and as soon as you use NMM, mods will again be placed in there and cause conflicts that need a reinstall to solve, rather than just a deactivate of the mod or drag/drop to get a different priority. You cannot slave for two masters, and keeping those two mod managers happy together will never work. @phazer11 I read that first answer you gave and saw this acronym I had never seen before, LMGTFY, and thought: WTH? So I clicked the link and, OMG that is brilliant. What a fantastic tool. Not only are you providing an answer but also assisting the questioner to develop skills to find answers themselves. Hallelujah! This a must have for me now. Why have I never seen this before? It's probably been around for ages. At any rate, for that little gem alone, I thank you.

Just read those threads and I haven't had as much fun since I fell in a nest of Fire ants. Oh wait...

Yeah agreed, but I can't figure out what it is. I've just removed the current Standalone install and tried the installer version, same result. Both Oblivion and Skyrim installs produce the same thing and I can not for the life of me figure out why that locked overlay icon appears for the Docs folder. Oh hang on, just re-read your post. The Wrye Bash report gets placed directly in the Skyrim Data folder? Not into a mod folder under the ModOrganizer folder? That is really strange. Why would it do that? MO doesn't allow anything like that to happen. This is the setting in ModOrganizer.ini that handles the custom executable for Wrye on my system. 9\binary=C:/Games/Utils/Mopy/Wrye Bash.exe 9\title=Wrye Bash 9\arguments=-g Skyrim 9\workingDirectory= 9\closeOnStart=false 9\steamAppID= 9\custom=true 9\toolbar=falseWrye Bash runs just fine from outside MO and generates reports and makes bashed patches just fine, so the install location shouldn't have any bearing. All I've done is placed 1 installation in that folder and used the switch -g Skyrim or -g Oblivion to tell it to work for whatever game MO is currently on. Is that similar to yours?

Well I'll be a monkey's ***. I have never seen that and just assumed the window worked properly. Apparently not. Apologies to @Questdog. I just thought he missed that selection action. I'll make a report if you want. I've got the code downloaded so I'll also look at how he has that dialog set. Yes @Vulgar! it is madness.

Wow what a difference a 'M' instead of a 'n' makes! I think it still applies. Of course I only deal in MO matters and the wav files supplied work just fine for me. Clearly though some of them just refuse to work for @NomenNescio. As @Keithinhanoi is linked to the mod and he is already found something odd with those files, I'd let him run through his thinking before trying something else.

I have no idea about FCOM, so it may well be 'easier' to deal with using a familiar tool like BOSS, I simply make the case that LOOT is developed by the same team that did BOSS and it, BOSS, WILL be phased out. LOOT is it's successor so why not start now using it, more users that come to the pack will be looking for guidance on the currently accepted tools, LOOT will be that tool. BOSS, as good as it was, will be left behind. Just some reasons why LOOT shouldn't be dismissed. A posting by Uhuru about LOOT. The official LOOT FAQ. I am coming to this forum with the mindset of supplying 'current' knowledge to installing mods, that is why I have taken on the task of championing MO as the best manager. Older, established users will know how to use a wide range of tools already but I am looking at the newer users that will actually be reading these pages.

Well I might be at odds with you on that, I see no evidence to not use it so it may be problematic if there are two sets of recommendations on sorting methods within the same pack. I'll step back from this pack for the time being.

AH Hotkeys - Skyrim Hotkey Manager In the words of the author: I've been using, or to be more accurate, trying to use, More Hotkeys Please with SkyUI and Categorized Favorites. This might be a better option.

If you are using MO and you installed some mods that either, don't work for you or they don't do what you want, just deactivate them from the mod list in MO, there should be no time in the future when anything you install in MO makes it necessary to completely redo your Skyrim install. Retrace you steps here and fix the ENB issue and then make a backup of the Skyrim folder, just in case. Afterwards, any mods installed via MO will have NO IMPACT on the Skyrim folder. You may add/remove/reorder/edit/stuff-up those mods to your hearts content and your Skyrim installation will be fine. So let's go back to the beginning. What ENB are you wanting and how have you tried to install it? This is assuming you have installed any other extension like SKSE correctly. I am making this assumption since this thread seems to say that.

After you have selected the saves and they are all highlighted, just right-click the top-most save and select "Delete X saves(s)"

Thank you. So there is something wrong with my Wrye Bash install then. I think another user reported something similar here, I'll look and see if the two setups are similar. Just one more thing, the reports, do they automatically get placed into the Bashed Patch mod or do you still have to manually move them from overwrite?

I wouldn't be so dismissive, @keithinhanoi is on to something here, there is something odd about the operating environment of @NomenNescio's machine that is causing this. There can be no conflict as those files exist only in AOS. The test sounds supplied work just fine on my machine so it can't be the plugin or wav files rather it is the way those sounds are handled on his machine.

If you mess with *.nifs, or any file really, and you are unsure which one is being loaded into the game. Look at the right-hand pane of MO and open the Data tab. You can navigate through the filetree as it exists in the VFS. The 2nd column shows which mod supplies it and the colour of the text and the tooltip shows any mods that have the same file but lose out in the conflict. So if you were editing, for example, farmhouse01.nif you would see that this file is provided by SMIM, Unofficial Skyrim Patch & Better Dynamic Snow. (in the example of my setup that is. you will have different mods loaded) SMIM though has priority and if your editing was on the BDS version it wouldn't show in game. I'm glad you sorted things out. MO is a very powerful tool and it provides a number of features that make things much better but can also take a bit of learning to understand fully.