The problem investigated in issue8870 detected that bdist_wininst installers fail in Vista and Windows 7 with enabled UAC (user access control) when run from local drives with non-MS file systems and from network drives.

The error message returned in this case is not explanative at all.
"Failed to start elevated process (ShellExecute returned 5)"

Further investigation revealed that if network samba share requires authentication, and authentication passes, then the installer won't fail. Unfortunately, I can not setup network access to unauthenticated Samba shares right now to test behavior, but I attach installer generated with --user-access-control=force in case somebody can help.

The error message needs to be improved to give users immediate hint what Windows UAC doesn't allow to run privileged executables from non-MS file systems and/or network drives.

A proper user error message requires investigation of behavior on anonymous samba shares. Attaching patch to install.c with backlinks to relevant ticket descriptions.

Side remarks about tracker process:
1) I’m not sure attaching binary executable files is helpful; if I ran Windows, I wouldn’t run them.
2) Select the 3.3 version for bugs that won’t be fixed to 3.2. Selecting both is redundant: 3.2 is current py3k trunk, it’s not a different branch than 3.3, in contrary to 2.6 and 2.7.
HTH

Can you please tell if this still applies now that distutils has been reverted to its previous stable state?  Can you test with distutils2?  Thanks in advance.