- 0
Wrye's Bash won't run from inside MO2
-
Similar Content
-
- 4 answers
- 878 views
-
CTD from having dyndolod.esp enabled in new save and old 1 2
By pentapox,
- SKYRIMSE
- DynDOLOD 3
- (and 1 more)
- 18 answers
- 1,664 views
-
- 13 answers
- 3,620 views
-
-
Recently Browsing 0 members
- No registered users viewing this page.
Question
Tabris
So, i have MO2 installed and been trying to run Wrye's Bash from it but when i try i get a window asking if i want to overwrite a temporary file inside a folder on my "C:/Users/Username/AppData/Local/Temp". It then doesn't open at all regardless of the option selected. The BashBugDump.log ends with the line "WindowsError: [Error 32] The process cannot access the file because it is being used by another process: u'c:\\users\\tabris\\appdata\\local\\temp\\WryeBash__e61yq'" that appears to be the cause of the problem. The folder and the file, however, only are created when i run Wrye's Bash and the file is deleted after it crashes (Then when i run it again it creates another folder with another name). I have even tried reinstalling the whole thing but it didn't help.
I noticed that the logs tend to appear in c:\users\tabris\appdata\local\ModOrganizer\logs instead of in the folder where i installed Mod Organizer, and then tried using the default folder for the profiles (also inside /appdata/local/ModOrganizer) as i suspected that might be the cause of the problem but it also didn't fix it. Both MO2 and Wrye's Bash are outside the Program Files folder or other UAC folder (although it shouldn't matter as i have UAC turned off). Logs below (do tell me if i'm missing something):
BashBugDump.log: https://pastebin.com/iXsWEisp
usvfs-2017-07-03_01-36-09.log: https://pastebin.com/6V1miiGP
mo_interface.log: https://pastebin.com/B1Tu6haY
Top Posters For This Question
16
13
10
5
Popular Days
Sep 16
8
Jul 8
8
Sep 19
8
Jul 9
6
Top Posters For This Question
GrantSP 16 posts
outdatedTV 13 posts
shadow1 10 posts
Tabris 5 posts
Popular Days
Sep 16 2017
8 posts
Jul 8 2017
8 posts
Sep 19 2017
8 posts
Jul 9 2017
6 posts
Popular Posts
StahPK
The solution to this is to upgrade to Win 10 1809. But I won't just upgrade win 10 (and have updates off) because as we all know, these recent updates usually mess things up. And 1803 works fine for
mscheetham
Nor me too, just tried it, different issue I suspect. In order to get wrye bash to work for what I want it to do (create bashed patch) I knocked up a batch script that rebuilds the skyrim install w
SSGCull
https://discord.gg/cYwdcxj Sent from my Pixel XL using Tapatalk
91 answers to this question
Recommended Posts
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. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now