Hello everyone! After my hard drive recently crashed I decided to move on up into Windows 7 and made the step into 64-bit. I'm getting around to re-installing everything, and so far I haven't had any problems except with Wrye Bash.

I followed all of the instructions as I've done before in the past to install Wrye Bash, but it just won't start. When I double-click the Wrye Bash launcher file in the Mopy directory, the computer just doesn't do anything. I've noticed that, curiously, it doesn't seem to be recognized as a file that can be "run."

I've tried to read around to find a solution for this issue, but nothing seems to suffice. I haven't found much, and what I have found either seems so overly technical that it isn't worth it, or people just saying "you shouldn't have to do that." Has anyone else ever experienced this problem?

EDIT: Here is a little more information that I hope will be helpful.

I found http://www.thenexusforums.com/index.php?/topic/195662-wrye-bash-launcherpyw-file-type-not-recognized-help/ where a person talks about a way they worked around this program, though it is inconvenient. I tried this also, and here is my experience:

- I had to put "python26" into the command prompt, because my python folder at c:\ is python26, not python25.
- When it ran, this was the output in the command prompt:

C:\Program Files (x86)\Bethesda Softworks\Oblivion\Mopy>c:\python26\python.exe bash.py -dTraceback (most recent call last):  File "bash.py", line 95, in     bosh.initDirs(personal,localAppData,oblivionPath)  File "C:\Program Files (x86)\Bethesda Softworks\Oblivion\Mopy\bosh.py", line 27707, in initDirs    dirs[key].makedirs()  File "C:\Program Files (x86)\Bethesda Softworks\Oblivion\Mopy\bolt.py", line 469, in makedirs    if not self.exists(): os.makedirs(self._s)  File "c:\python26\lib\os.py", line 150, in makedirs    makedirs(head, mode)  File "c:\python26\lib\os.py", line 157, in makedirs    mkdir(name, mode)WindowsError: [Error 5] Access is denied: 'C:\\Program Files (x86)\\Bethesda Softworks\\Oblivion Mods'

I have no idea what that means, but I figured the last line might be pretty telling. Any ideas? I get the vague feeling that I am doing something stupid, I just can't quite figure out what it is.

Are you using a 64bit version of python? IIRC wrye bash doesn't play nicely with it so if that is the case switch to a 32 version.

I don't believe I am, but do you know how I could find that out to be sure? I downloaded and ran the python distributions from the Wrye Bash tesnexus page.

If its (was originally) in the Program Files (x86) directory then its 32-bit.

I strongly recommend that you install everything outside of the Program File directories. Windows 7/Vista place access restriction on those folders by default. You can bypass this security feature by disabling UAC or by changing the access permission level, however it much easier to simply install finicky applications (ie Oblivion) outside of the directory. Any other directory will do (ie C:\games).

Thanks for your input. I may just do that - move Oblivion out into another folder somewhere in C. That sounds like it might save me a few headaches down the road.

I get the feeling, however, that this isn't a problem with access. The reason i say this si because when I try to run Wrye Bash, either by double-clicking on the Launcher or Bash.py, just absolutely nothing happens. I don't get an error message, and there is no notification that i'm trying to access something I don't have permission to.

My "Python 26" folder is located in C:\, so I really can't tell if it's a 64-bit version or not. I wouldn't think that it is, only because I used the files hosted with Wrye Bash at tesnexus, but you never know.

EDIT: I temporarily disabled my UAC settings, to see if Windows was blocking something because of Wrye Bash being located within Program Files (x86), but even with UAC disabled nothing changes.

Problem solved guys! Reinstalling Oblivion to a folder in C:\ and then installing Wrye Bash did the trick. So thanks a lot everyone, especially Níeh?ggr! :foodndrink:

I hope this topic might help someone else who has this problem in the future.