Script errors w/ Vista 64

Same issue. Here's my log:

http://pastebin.com/7TtBLAGv

Turned off UAC - also killed antivirus just to make sure before the install. Is there something else that would use the Python script (software-wise) that I might have installed that I should look for? Also, is there a location I should look for the Python files to be to see if they are there?

For what it's worth, I even tried running it in compatibilty mode with XP with the same results.

For what it's worth, I did a quick search for why python issues on Vista. Found a guide to installing python. They suggested loading python from a command line to see if it was active. Tried that and it didn't recognize the command. Followed their guide to installing Python 2.5, including adjusting the environmental variables to add the path. After that, I got a response to Python from the command line. Uninstalled and re-installed XBMC and got the same results.

Is it worth creating a different user account and re-installing from that account? I'm the only account on the machine right now.

You should not have to install Python on it's own. When XBMC installs it should install the Python resources it needs into Xbmc\system\python.

I'm at a loss for answers with this issue at the moment.

please enable debug logging, restart xbmc and post a new log file.

also, check if you have this file:
C:\Program Files (x86)\XBMC\system\python\Lib\os.py

Here's the log file:

http://pastebin.com/mcHJC3qE

That file does exist in the python library

i am also have the same issue on my vista 64bit also i had to get the 10.0 and eveything works like it should they have a big issue on 11.0 eden and are not fixing it for vista 64bit i have intalled it on xp and windows 7 and works good but when it comes to vista you are out of luck they dont want to address that they have a issue on the Eden

I also have the same problem...
Even after 3 or 4 install attempts still same missing os module error in log..
Any suggestions ?

Any solutions yet on this issue ?
I got the same problem

Unfortunately not. I'm not sure anyone has figured out exactly why Vista has this issue.