- 0
MO2 can not launch LOOT (seems auto delete usvfs_proxy_x86.exe)
-
Similar Content
-
- 4 answers
- 912 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,678 views
-
- 13 answers
- 3,668 views
-
-
Recently Browsing 0 members
- No registered users viewing this page.
Question
waitinfuture
I just return to play skyrim SE with MO2 a few days ago. Then I have not installed so many mods, just check one by one and play.
I could install most of Mod (for test) without problem. And I could install and launch recent version Loot from MO2.
But today, I happend to use right pane>plugin> "sort" of MO2 (I know it is old Loot which packaged with MO2)
Though I do not think, it cause problem, but I hoped to check with Loot (which installed and set to luanch from MO)
But MO2 can not launch Loot anymore. everytime I try to launch LOOT from MO2, it show errer message window. after while Loot shut down. It only happen when I run Root from MO2. Even though I use MO then run same version Root it work.
So I could confrim the problem caused by MO2. then I happend to find topic which suggested to copy and paste "usvfs_proxy.exe"
from another version MO2 to current MO2.
I found old downloaded MO2, there were "usvfs_proxy.exe". then copy and paste it to MO2 directory (same folda of
Modorganizor.exe) , after that, I could launch Loot from MO2.
But this time, Loot can not see MO2 data directories any more. Then I finally install MO2 to another drive, then compare files.
I clear see, "usvfs_proxy_86.exe" seems auto deleted from my MO2 directory.
I can confirm, I have never deleted any file from MO2 directory. then it seems happen when I use "sort" of MO2.
After all, I copy and paste the "usvfs_proxy_86.exe" from another drive MO2, this problem solved.
(at least for me).
Though I do not know, actually what cause this issue, (auto- delete the exe file), if it caused another tool, which I launch from MO,
or my Notron system tool delete,, but If someone have same problem, try it.
Of course, clean un-install MO2 and re-install MO2 may work, but if you clear know which file cause issue, It may help when we see
same issue.
2 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