Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

--user-access-control=force produces invalid installer on Vista #53116

Closed
techtonik mannequin opened this issue Jun 1, 2010 · 9 comments
Closed

--user-access-control=force produces invalid installer on Vista #53116

techtonik mannequin opened this issue Jun 1, 2010 · 9 comments
Assignees
@tarekziade
Labels
stdlib Python modules in the Lib dir type-crash A hard crash of the interpreter, possibly with a core dump

Comments

@techtonik
Copy link
Mannequin

techtonik mannequin commented Jun 1, 2010

BPO 8870
Nosy @mhammond, @tarekziade
Superseder
  • bpo-8908: friendly errors for UAC misbehavior in windows installers
    		•
    Files
  • wget-0.6.win32.exe: --user-access-control=force
    		•

    Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = 'https://github.com/tarekziade'
closed_at = <Date 2010-06-02.19:51:26.292>
created_at = <Date 2010-06-01.18:37:58.999>
labels = ['invalid', 'library', 'type-crash']
title = '--user-access-control=force produces invalid installer on Vista'
updated_at = <Date 2010-06-11.02:21:48.950>
user = 'https://bugs.python.org/techtonik'

    bugs.python.org fields:

    activity = <Date 2010-06-11.02:21:48.950>
actor = 'r.david.murray'
assignee = 'tarek'
closed = True
closed_date = <Date 2010-06-02.19:51:26.292>
closer = 'eric.araujo'
components = ['Distutils']
creation = <Date 2010-06-01.18:37:58.999>
creator = 'techtonik'
dependencies = []
files = ['17520']
hgrepos = []
issue_num = 8870
keywords = []
message_count = 9.0
messages = ['106852', '106856', '106859', '106864', '106865', '106868', '106895', '106910', '107161']
nosy_count = 4.0
nosy_names = ['mhammond', 'techtonik', 'koen', 'tarek']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = None
status = 'closed'
superseder = '8908'
type = 'crash'
url = 'https://bugs.python.org/issue8870'
versions = ['Python 2.6', 'Python 2.7']
    @techtonik
    Copy link
    Mannequin Author

    techtonik mannequin commented Jun 1, 2010

    Running python setup.py bdist_wininst --user-access-control=force produces invalid installer that fails to install with the error message:

    Failed to start elevated process (ShellExecute returned 5)

    @techtonik techtonik mannequin assigned tarekziade Jun 1, 2010
    @techtonik techtonik mannequin added stdlib Python modules in the Lib dir type-crash A hard crash of the interpreter, possibly with a core dump labels Jun 1, 2010
    @techtonik
    Copy link
    Mannequin Author

    techtonik mannequin commented Jun 1, 2010

    See also bpo-8871 and original report http://scons.tigris.org/issues/show_bug.cgi?id=2533

    @mhammond
    Copy link
    Contributor

    mhammond commented Jun 1, 2010

    Is it possible the installer is being run from a network share? A comment from PC/bdist_wininst/install.c:

    // interesting failure scenario that has been seen: initial executable
// runs from a network drive - but once elevated, that network share
// isn't seen, and ShellExecute fails with SE_ERR_ACCESSDENIED.

    SE_ERR_ACCESSDENIED is 5, so googling for that might offer more insights.

    @techtonik
    Copy link
    Mannequin Author

    techtonik mannequin commented Jun 1, 2010

    It is local Ext2 partition system accessible through http://www.fs-driver.org/ on the same HDD as primary system partition. But there is definitely issue with difference between drives.

    There is no problem if the package is executed from the NTFS system drive - permissions asked as expected, no errors. On the Ext2 partition VLC and other installers that require elevated privileges fail. I do not remember any such problems last year, but it just can be that most applications on this drive are not windows specific or do not require elevated privileges.

    I still doesn't explain why this drive is threatened as "network". It would be nice to see how Windows treats other partition types - FAT32 or FAT16.

    @techtonik
    Copy link
    Mannequin Author

    techtonik mannequin commented Jun 1, 2010

    Attaching installer file for testing.

    @koen
    Copy link
    Mannequin

    koen mannequin commented Jun 1, 2010

    This is listed as a known limitation of the Ext2 FS driver. From http://www.fs-driver.org/relnotes.html :

    ===
    Running programs on an Ext2/Ext3 volume on Windows Vista

    Currently it is not possible to start a program on Vista if UAC is enabled and the program's executable is stored on an Ex2/Ext3 volume. An "invalid parameter" message box appears, but the program does not start.

    UAC is the feature of Vista that prompts the user to elevate the user privileges to administrator level when necessary. UAC is enabled by default. It is not recommended to disable it.

    The problem is caused by Vista's internals: There is some code that compares whether the name of the file system type is one of the following: "NTFS", "FAT", "FAT32", "CDFS", "NPFS", "MSFS" or "UDF". If there is a match, it is one of Microsoft's file system types and a lot of code is skipped in the Multiple UNC Provider (MUP) implementation of Vista. If the file system type is a third-party type, for example "Ext2", some code runs in the MUP of Vista that always generates an ERROR_INVALID_PARAMETER error status code due to a bug of Vista.
    ===

    So the bug is in that FS (or in Windows if you will). It is not something Python can fix.

    @techtonik
    Copy link
    Mannequin Author

    techtonik mannequin commented Jun 2, 2010

    Thanks for thorough explanation. Can somebody close it with some resolution like "Can't fix. OS level problem"?

    @merwok merwok closed this as completed Jun 2, 2010
    @merwok merwok added the invalid label Jun 2, 2010
    @techtonik
    Copy link
    Mannequin Author

    techtonik mannequin commented Jun 2, 2010

    Is it possible to detect this situation and display more user-friendly error message with a reference to this issue?

    @techtonik
    Copy link
    Mannequin Author

    techtonik mannequin commented Jun 5, 2010

    Please add bpo-8908 as superseder.

    @ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Assignees

    @tarekziade tarekziade

    Labels
    stdlib Python modules in the Lib dir type-crash A hard crash of the interpreter, possibly with a core dump
    Projects
    None yet
    Milestone
    No milestone
    Development

    No branches or pull requests
    2 participants
    @mhammond @merwok