WRYE BASH WIN 7 COMPATIBILITY

[jwoltz]

I have been having a major problem with my Oblivion freezing on fast traveling and / or walking into some cells. I was told to install Wrye Bash to solve what might be a bloat issue using Wrye Bash's bloat fix. PROBLEM: Wrye bash will NOT properly install on my new WIN 7 Computer. Any suggestions? Anyone?

[RaineAndrews]

I have been having a major problem with my Oblivion freezing on fast traveling and / or walking into some cells. I was told to install Wrye Bash to solve what might be a bloat issue using Wrye Bash's bloat fix. PROBLEM: Wrye bash will NOT properly install on my new WIN 7 Computer. Any suggestions? Anyone?

 

What files are you attempting to install. Version? Wrye Bash requires a collection of python installations to work properly. Also, make sure to right click and run as an administrator, otherwise the install might not work correctly.

[Smooth613]

You need to reinstall Oblivion and Wrye Bash outside of Program Files in order for it to work. Otherwise UAC will only cause headaches. No if, and, or buts about it, just re-install to an alternate location. The following information will help assist you with the process.

[/line]

Well first you installed to a protected directory and that's likely your cause for the issues you have.

File "C:\Program Files (x86)\Bethesda Softworks\Oblivion\

Bad idea to install Oblivion and mods there. You'll only have issues with mods and utilities due to UAC. UAC doesn't like it when files are altered in anyway and sees this as a security threat. This is why you should always install Oblivion outside of Program Files to a directory such as <drive letter>:\Games\Oblivion. Follow Bben's Installation Procedure to reinstall outside of a protected directory. In all likelihood this alone will solve any issues you have and prevent weird issues from happening in the future.

 

Upon reinstalltion you need to ensure you properly install Wrye Bash and the Python Libraries. Proper procedure is as follows.

 

1. Go to Control Panel and remove anything with the word Python in it.
   
2. Next, uninstall Wrye Bash and delete the Mopy folder. If you used the installer version you should have an uninstaller as well.
   
3. After you have removed everything related to Python and Wrye Bash it's time to reinstall, properly.
   
4. Install WryePython03a from the Wrye Bash page here on TESNexus
   
5. Install Wrye Bash 275 from the Self-Installer
   
6. Update to Wrye Bash 287 by overwriting the Oblivion\Mopy folder.
   
7. Finally, Update to Wrye Bash 290 by again overwriting the Mopy folder.
   
8. Go to your Oblivion Mopy folder and create a shortcut for Wrye Bash Launcher.pyw and send to desktop.
   
9. You're done! Double click the shortcut and Wrye Bash should launch and you're good to go.
   

 

Wrye Bash v291 will be released as a full Self-Installer version and will eliminate many of the above steps. It's currently in BETA.2 and it's working very well, I've had virtually no problems with v291. The full release to the public should happen in the near future so keep your eyes open for it.

 

The Wrye Bash Pictorial Guide for Newbies is also an excellent way to get your hands dirty with Wrye Bash. Check it out!

 

If Wrye Bash fails to start or you are still having issues, first check in your Oblivion\Mopy folder for a pidfile.tmp. If that file is present and Wrye Bash is not running, delete it. Then try to start Wrye Bash again. If that fails you need to post the bug dump information in the Official Thread @ BethSoft for someone to look over.

 

Good luck!

[rhapsodicink]

You need to reinstall Oblivion and Wrye Bash outside of Program Files in order for it to work. Otherwise UAC will only cause headaches. No if, and, or buts about it, just re-install to an alternate location. The following information will help assist you with the process.

[/line]

Well first you installed to a protected directory and that's likely your cause for the issues you have.

File "C:\Program Files (x86)\Bethesda Softworks\Oblivion\

Bad idea to install Oblivion and mods there. You'll only have issues with mods and utilities due to UAC. UAC doesn't like it when files are altered in anyway and sees this as a security threat. This is why you should always install Oblivion outside of Program Files to a directory such as <drive letter>:\Games\Oblivion. Follow Bben's Installation Procedure to reinstall outside of a protected directory. In all likelihood this alone will solve any issues you have and prevent weird issues from happening in the future.

 

Upon reinstalltion you need to ensure you properly install Wrye Bash and the Python Libraries. Proper procedure is as follows.

 

1. Go to Control Panel and remove anything with the word Python in it.
   
2. Next, uninstall Wrye Bash and delete the Mopy folder. If you used the installer version you should have an uninstaller as well.
   
3. After you have removed everything related to Python and Wrye Bash it's time to reinstall, properly.
   
4. Install WryePython03a from the Wrye Bash page here on TESNexus
   
5. Install Wrye Bash 275 from the Self-Installer
   
6. Update to Wrye Bash 287 by overwriting the Oblivion\Mopy folder.
   
7. Finally, Update to Wrye Bash 290 by again overwriting the Mopy folder.
   
8. Go to your Oblivion Mopy folder and create a shortcut for Wrye Bash Launcher.pyw and send to desktop.
   
9. You're done! Double click the shortcut and Wrye Bash should launch and you're good to go.
   

 

Wrye Bash v291 will be released as a full Self-Installer version and will eliminate many of the above steps. It's currently in BETA.2 and it's working very well, I've had virtually no problems with v291. The full release to the public should happen in the near future so keep your eyes open for it.

 

The Wrye Bash Pictorial Guide for Newbies is also an excellent way to get your hands dirty with Wrye Bash. Check it out!

 

If Wrye Bash fails to start or you are still having issues, first check in your Oblivion\Mopy folder for a pidfile.tmp. If that file is present and Wrye Bash is not running, delete it. Then try to start Wrye Bash again. If that fails you need to post the bug dump information in the Official Thread @ BethSoft for someone to look over.

 

Good luck!

 

Or just disable UAC lolololololol. Fixes whatever you guys are talking about