GrantSP

That ENB message isn't reliable. I run it on my laptop and says it is the Intel card not my nVidia yet the game clearly is using that one. I've seen reports on the ENB forum that it is a known issue.

Yes.

If you double-click the 'Overwrite' folder it will open as an explorer window showing the folders/files contained within. Keeping that window open move your cursor away from it and, if your mouse has a wheel, scroll the background modlist until the DSR Patch mod is visible. If your mouse doesn't have a scroll-wheel you can still scroll the modlist pane by clicking the scrollbar or it's arrows at the top and bottom. By the scrollbar I mean the UI element similar to that which you can see in your browser now at the extreme right. Once the DSR Patch is visible use your mouse to select everything in the 'overwrite' folder and drag/drop them onto that DSR Patch mod. Answer yes to any questions about replacing files. To be correct you aren't actually adding files to 'patch', each time you run the DSR patcher you are creating a new 'patch' and dragging these files is simply replacing the existing patch with a new one, but it is essentially the same thing.

Yeah, don't sweat it, it's just the reports that are bugging out, and apparently only on a few systems; yours, mine and I think one other. The bashed patches are created perfectly and that's all we need worry about. Having said that feel free to further investigate this phenomenon, whatever the outcome it all goes towards forming a knowledge base that everyone can learn from. EDIT: May I ask you, in the overwrite folder, when you open it and examine the contents does the 'Docs' folder have that padlock icon I mentioned?

Agreed, $64 is quite reasonable, though Aussie dollars may make it more like $80 for me. Still I may go lifetime premium at some point in the future it doesn't answer though the server listings on my installations?

@pistolouco Actually what you did wasn't exactly the same as me but it does show the principle. In your test the Bashed Patch wasn't active when you ran WB for the second time. At least that is what I am surmising based on the first screenshot. But, MO should have allowed WB to display the report from that current running instead of the error message, so the end result is the same. Regarding permission issues, that isn't possible in my instance. I have checked and triple checked and there are no permission issues with any of my programs. Although this isn't the expected behaviour for MO to show, I'm loathe to make a bug report for what is a very minor issue. The patch itself works just fine and is updated properly, it's just the reports. I think I will just let this rest and this thread can serve as a documented history that might be useful later on.

I understand MO has no impact on the selection of servers but I am confused why on my first installation of MO my available servers box shows this: but subsequent installs only show servers like this: I haven't been a premium account user for years and certainly never since using MO so why are my settings so different?

You may want to provide a bit more information than that. You haven't said which game? What mod manager you use? Or indeed anything useful?

May I suggest reading the wiki before you go on any further. I sense a misunderstanding of how the MO system works and any attempts to proceed further may still be problematic. Using MO is not difficult but it is a major adjustment to how other mod managers work so there can be confusion. STEP itself is just a guide and any of the 'issues' you faced would exist if you were trying to install mods without following it, so STEP of itself is not the reason for your angst. Stick with it, the skills you learn doing this will hold you in good stead with following the other more challenging guides in the future.

Gotta agree with you @Tech, I installed it and it is currently in my modlist but that initial setup is a real PITA. I think I might be dumping it on my next play, unless the new version drastically changes that.

Welcome. Sorry to here about the bad install. All you will need to do is backup the downloads, mods, profiles folders and posssibly the catergories.dat file (if you made any changes to the Catergories in MO) These folders hold respectively: the archives from Nexus, the "installed mods" and the settings for each MO profile, including Skyrim saves if you enabled that option. Other than that you can install MO again and copy back those folders to have your installation as returned. One suggestion, when you do reinstall, do so into a folder away from any that Windows has control of such Program Files or Program Files (x86). EDIT: I have added this question to the MO FAQ.

Like @n\Nozzer66 says, once or twice doesn't really matter. I was just curious about the different outcomes. So long as everything works.

Really? I just tested this procedure again with a new Dawnguard.esm and LOOT reports it as clean after one pass. Are you sure you had the cleaned Dawnguard active before running LOOT and not the previous version?

If you continue to use NMM and MO together you will continue to have issues. Mods installed by NMM will be placed in the 'actual Data' folder, not the 'virtual Data' one created by MO. This is a crucial step. MO will not be able to manage any conflicts with mods outside of its VFS. Time to 'bite the bullet' and make a choice: MO or NMM, but definitely NOT BOTH.

Agreed, though Will I Am does have a hand in a lot of different projects...

Go with the new. All is fine.

Actually, no, I'm facing a similar situation to her in that my WB reports don't automatically get updated as outlined here.

I'm worried by this statement: Which files are you referring to? If they are mods, then this is not what you need to be doing. They should added using MO, which doesn't place anything in that folder. I'm going on the assumption here that this problem is because of a conflict between mods. Managing them all with MO will ease the problem, or at least make it easy to diagnose. Lastly, ensure you start the game from within MO from now on, not any shortcut to Skyrim that is still on the desktop. Those Steam mods the @phazer11 advises to add back, should also be added using MO. If you saved them as archives just use that function to install them. Here's how to do it.

I think the problem is there aren't any other servers listed. I have that situation in the installations of MO besides the first one. I've made bug report on the matter. There seems to be no way to get MO to generate a list of servers if Nexus doesn't give you one.

Excellent, now we're getting somewhere.

I mean no sleight against your suggestion, just as you say though, that avenue was examined. I doubt it. Unless you have some strange setup where that other drive is a NAS or something that requires greater permission than MO grants. Do you have any other audio type mods installed? If not could you find one, install it and check if that one works? That way we can eliminate the MO VFS as interfering if that mod works and then it must be the format of those AOS wav files. Also if you could find the installed codecs that your machine is using. Here's a blog that provides 3 ways to do that. Then we might see if codec issues are at play. (The software from NirSoft is very good, I personally use a few of his tools and recommend them.)

In deference to @hishutup, I think the steps you have already taken have covered anything that suggestion will highlight.

The reason I raised it is because @TheMerryPloughboy will be making a mod out of the overwrite folder, if there was an ini for SKSE, for example, when he makes the new mod that ini will be present and depending on how he sets the priority for the new mod it will take precedence. I keep "bangiing on" about this in the hope that all new users will learn about priority and conflicts and avoid flooding forum posts with questions that could be easily fixed by some simple house-keeping. With all due respect, there shouldn't be a debate about this. The wiki clearly explains the overwrite folder should be cleared.

I have added a brief description to the wiki about this. It is under the 'Right Pane' heading.

Like I mentioned in the other thread, I don't believe it is a MO issue as such but... it is possible the Nexus web page code has been tweaked to look for NMM users and assign a server that is crappy to non-NMM users. Nexus does do things like that as is evidenced by the NMM version lock out that happens from time to time. I have MO setup for all the supported games and the download speeds I get are in the range of 250 - 300 Kbps so maybe I'm just lucky or it is because I had my servers set in MO before Nexus fiddled. There is snippet from Tannin that has a bearing on the matter.