Whenever I go to launch WB as an executible from MO2 I get a pop uo saying that it's open in another location/program and craps out a temp file into the overwrite.
I recently unistalled the python version because WB/MO2 were updated and I didn't think I needed that workaround anymore.
Thing is WB launches on it's own fine, just not through MO2. Any advice?
I've tried adding exclusions to my firewalls (win Defender and malewarebyes for the craic)
Question
uncleseano
Whenever I go to launch WB as an executible from MO2 I get a pop uo saying that it's open in another location/program and craps out a temp file into the overwrite.
I recently unistalled the python version because WB/MO2 were updated and I didn't think I needed that workaround anymore.
Thing is WB launches on it's own fine, just not through MO2. Any advice?
I've tried adding exclusions to my firewalls (win Defender and malewarebyes for the craic)
Link to comment
Share on other sites
1 answer 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