This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steve.dower
Recipients eryksun, paul.moore, steve.dower, tim.golden, zach.ware
Date 2020-10-07.14:44:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1602081876.64.0.468512445942.issue41961@roundup.psfhosted.org>
In-reply-to
Content
> I was able to reproduce the error dialog by changing the owner of the "Installer" folder to the current user and removing the two DACL entries that grant access to Administrators and SYSTEM.

Yeah, I'd assumed the most likely cause was the ACLs having been reset on the machine in question, though I'd expect that to cause most installs to fail. It might be that Python is the first/only MSI that the user has tried though?

It sounds like just resetting the owner isn't enough on its own, but the inherited ACLs should include SYSTEM and not prevent it from working. So I wonder if something else is at play?

Also, did your change reproduce the "Error: 0"? Or did you get an actual error code?
History
Date User Action Args
2020-10-07 14:44:36steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, zach.ware, eryksun
2020-10-07 14:44:36steve.dowersetmessageid: <1602081876.64.0.468512445942.issue41961@roundup.psfhosted.org>
2020-10-07 14:44:36steve.dowerlinkissue41961 messages
2020-10-07 14:44:36steve.dowercreate