classification
Title: Encrypted MSI fails to install with code 2755
Type: Stage: resolved
Components: Installation, Windows Versions: Python 2.7
process
Status: closed Resolution: wont fix
Dependencies: Superseder:
Assigned To: Nosy List: jaraco, steve.dower, terry.reedy, tim.golden, zach.ware
Priority: normal Keywords:

Created on 2015-04-05 02:08 by jaraco, last changed 2018-12-08 19:46 by terry.reedy. This issue is now closed.

Messages (3)
msg240099 - (view) Author: Jason R. Coombs (jaraco) * (Python committer) Date: 2015-04-05 02:08
When installing Python (3.4.3 or 2.7.9) from an EFS encrypted installer file, the installation proceeds normally through the target selection and feature selection, but then immediately reports "/!\ The system cannot open the device or file specified," and aborts the installation with "The installer has encountered an unexpected error installing this package. This may indicate a problem with the package. The error code is 2755."

Other MSI products install fine when the MSI is encrypted (pandoc, MongoDB), so there appears to be something unique about the Python installer that's failing when the Trusted Installer cannot read the MSI itself. Decrypting the MSI before installing works around the issue.

Environment: Windows 8.1 64-bit with Python 64-bit
msg240100 - (view) Author: Jason R. Coombs (jaraco) * (Python committer) Date: 2015-04-05 02:13
A search for "EFS error code 2755" reveals others who have encountered this issue with other packages, so it's not unique to Python, though it may be something that Python might be able to address or may be unable to solve due to the required operations.
msg331391 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2018-12-08 19:46
For 3.x, this is out of date.  Since 3.5, Windows installers are .exe, not .msi. There will be no more 3.4 installers.

For 2.x, there should be at most 3 more releases.  But the .msi installer author has been inactive since before this was opened.  Given the rarity of the problem, the workaround of decrypting the file back to what we distribute, and the possibly of introducing a regression that only shows up after a release, I am confident that no one else wants to touch this.  So closing as won't fix.
History
Date User Action Args
2018-12-08 19:46:27terry.reedysetstatus: open -> closed

versions: - Python 3.4
nosy: + terry.reedy

messages: + msg331391
resolution: wont fix
stage: resolved
2015-04-05 02:13:59jaracosetmessages: + msg240100
2015-04-05 02:08:27jaracocreate