![]() ![]() ![]() Nothing in the file security should prevent the service from opening "%APPDATA%\Microsoft\Installer" with WRITE_DAC and WRITE_OWNER access, assuming it uses backup semantics with the restore privilege enabled, but apparently it doesn't. The installer service runs as SYSTEM, with an access token at system integrity level that has full privileges and the administrators group enabled. > Anyone else know of any possible causes for this? ![]() It may just be system permissions or corrupt ACLs (waiting on user logs for more ideas here).Īnyone else know of any possible causes for this? I'm not sure if it's anything we could even prevent, but maybe we can make it easier to troubleshoot. So I assume the error came back from the Windows Installer service which couldn't write to the folder for some reason. * %AppData%\Microsoft\Installer is normally readable by Everyone, but only writable by Administrators, even in the user's directory * 'Installer\' is a directory, not a file * error 0 means success, so it shouldn't be popping up an error Verify that you have sufficient privileges to modify the security permissions for this file. > Could not set file security for file 'C:\Users\sc\AppData\Roaming\Microsoft\Installer\'. Messages (5)Ī user received MSI error 1926 in a popup dialog, text reading: Windows install failure "could not set file security"Įryksun, paul.moore, steve.dower, tim.golden, zach.wareĬreated on 23:32 by steve.dower, last changed 14:59 by admin. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |