[pywin32-bugs] [ pywin32-Bugs-3528888 ] Errors when installing with UAC disabled

[SourceForge.net <no...@so...>]

Bugs item #3528888, was opened at 2012-05-22 10:37
Message generated for change (Comment added) made by mhammond
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3528888&group_id=78018

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: installation
Group: None
Status: Open
>Resolution: Accepted
Priority: 5
Private: No
Submitted By: class101 (class1o1)
Assigned to: Mark Hammond (mhammond)
>Summary: Errors when installing with UAC disabled

Initial Comment:
If your installation of pywin32 on Windows 7 always end with 

close failed in file object destructor:
sys.excepthook is missing
lost sys.stderr

This is maybe because you are running Windows under the "Administrator" account and anything you normally run is equal to a "run as Administrator"

And paradoxically running the installation of pywin32 on Windows 7 as Administrator causes this error.

So a workaround is to create another admin account

net user Admin /add
net user Admin <type your password>
net localgroup Administrators Admin /add

and then run the pywin32 installation with

runas /user:Admin pywin32-217.win32-py2.7.exe


----------------------------------------------------------------------

>Comment By: Mark Hammond (mhammond)
Date: 2012-05-28 23:10

Message:
I can verify that disabling UAC causes this error when run from an admin
account (regardless of that account's name).  It looks like the install
completes successfully (at least the pywin32_postinstall.log file in the
temp dir is complete), but I'll try and dig further into what is causing
this error to be shown.

----------------------------------------------------------------------

Comment By: class101 (class1o1)
Date: 2012-05-27 03:17

Message:
To note that on all of my Windows machines, first things I do is enabling
the Administrator account to take ownage of it, and always disabling the
UAC

To me this is urgent to fix this for good mhammond because postscripts
seems to generate files and its a bit dangerous to redistribute something
that unstable out of the box because the we identify further errors and we
have to investigate few hours to finally find out pywin32 was not 100%
installed, I had made some research about this issue previously, it seems
you applied previous patches for this few years ago, but I'm sorry to
inform you 217 is still not stable and fails to install with reproducable
cases.

Also you may be instered to throw out then don't use the Administrator
account, I'm working with computer each day this is my work and I notice
pywin32 is only or really on of the few product I see failing under the
Administrator account and working under a different admin account, but when
you know how quircky is the Windows security scheme, its more than evident
but definitely not a solution for me to use another Admin account, Windows
is just too quircky for this.

----------------------------------------------------------------------

Comment By: class101 (class1o1)
Date: 2012-05-22 10:43

Message:
Bug identified and workaround tested working on 

Windows 7, 64-bit, English, main admin account: Administrator
Windows 7, 64-bit, French, main admin account: Administrateur
Windows 7, 64-bit, English, main admin account: Admin

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3528888&group_id=78018