Eryk Sun added the comment:
> It might be that Python is the first/only MSI that the user
> has tried though?
It's likely the first per-user MSI install attempted since the security of the
"Installer" directory was modified. There's no problem with a per-machine
install.
> did your change
Steve Dower added the comment:
> 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
Eryk Sun added the comment:
> Anyone else know of any possible causes for this?
The installer service runs as SYSTEM, with an access token at system integrity
level that has full privileges and the administrators group enabled. Nothing in
the file security should prevent the service from
Steve Dower added the comment:
Suspicious points:
* error 0 means success, so it shouldn't be popping up an error
* 'Installer\' is a directory, not a file
* %AppData%\Microsoft\Installer is normally readable by Everyone, but only
writable by Administrators, even in the user's directory
So I
New submission from Steve Dower :
Original report:
https://twitter.com/Steve_Casselman/status/1313564671652159488?s=20
A user received MSI error 1926 in a popup dialog, text reading:
> Could not set file security for file
> 'C:\Users\sc\AppData\Roaming\Microsoft\Installer\'. Error: 0.
