screwyou00

That's what I'm doing though. I only clicked on Skyrim because I wanted to show that WB through MO2 will still launch if I choose Skyrim 2011, but for some reason not if I choose Skyrim Special Edition. I only use MO2 for Skyrim Special Edition; for Skyrim 2011 I use the old Mod Organizer, which everything works with 100%. Thanks for trying to help though.

So does this mean WB does not support SkyrimSE through MO2? Because if I do what I said way near the top of the thread, WryeBash works perfectly and I can make patches.

GrantSP, on 02 Jan 2017 - 4:29 PM, said: @screwyou00 From what I see in your logs it looks like it may be down to UAC issues, likely caused by your installation of WB into the Program Files (x86) folder. STEP in general, and MO in particular, recommends installing all tools outside of Windows UAC folders like those. Try removing your existing WB install and place it into a folder all its own. I have a D:\Games\Utils\ folder in which I place my other tools such as WB or xEdit. @tjax323 You needn't worry about your details too much, firstly your password is saved in the INI in an encrypted state so unless someone wants to force break it open it isn't exposed, secondly you can simply delete that line after you paste it into the webpage. Now, unrelated to WB, but you seem to have Qt issues with some UI elements in MO2, try deleting everything inside the [Geometry] section of your INI and then start MO2 again to see if it is corrected. The file: usvfs-2017-01-02_22-27-54.log is actually the most important one for me here as it details what is, or isn't loading. -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- I don't think it's because of UAC. I have the full access control for my ModOrganizer and Steam folders. Here are my logs when I switch WryeBash to my downloads folder and run it for Skyrim 2011 Wrye Bash "BashBugDump.log" MO2 "mo_interface.log" MO2 usvfs log and here are the logs when I run WryeBash for SkyrimSE Wrye Bash "BashBugDump.log" MO2 "mo_interface.log" MO2 usvfs log link to gifv of what I did

I should have clarified that Wrye Bash does not work on Skyrim Special Edition for me using MO2. Here is what my logs say Wrye Bash "BashBugDump.log": MO2 "mo_interface.log": MO2 "usvfs-2017-01-02_23-15-50.log": WryeBash seems to work for the original Skyrim when running it through MO2, but for some reason it crashes or does nothing for Special Edition.

What I ended up doing was copying all esp and esm files from the ModOrganizer "mod" directory into the "data" directory of Skyrim Special Edition, then I had to make sure "plugins.txt" from "%localappdata%\Skyrim Special Edition" had the same load order as "loadorder.txt" from ModOrganizer, and then I ran Wrye Bash. After the patching is finished, I copied/moved the bash patch and the related bash patch folders created inside Skyrim Special Edition's "Data" directory into the bash patch folder of ModOrganizer, and then I deleted all the esps and esms from Skyrim Special Edition's "Data" directory. It requires a little effort, but hopefully this works for you too.