• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3165
  • Last Modified:

Error 1926 on Windows 7

I have a problem that occurred only in some Win 7 Ultimate systems.
In my setup is suppose (among others) to copy files to the  "Program Files" & "System32" directories.
The problem occurred when the setup try to copy files to the "System32" directory.
The install shield raise this error message box:
"Error 1926. Could not set file security for file C:\Windows\system32\, Error: 0. Verify that you have sufficient privileges to modify the security permissions for this file. "

I run the setup "As Administrator", run it when logged on as the user administrator, and still get this error every time I ran the setup.

As I write in the beginning this is only happens in some Windows 7 ultimate 32-bit system, on other system (xp, server 2003,vista,server 2008 including on most win 7 systems) it works fine.

I'm compiling the setup with InstallShield 2008 - Professional
  • 2
  • 2
1 Solution

A few questions:

Are you putting any files into system directories?

Are you using any static paths for your components, rather than using the Installshield properties for paths?

Are you creating new directories outside of Program Files when installing?

We might be able to better diagnose with a few more details.

IysAuthor Commented:
hi jmcmunn,
I'm coping some files to the system32 ([SystemFolder]) and system32\drivers ([SystemFolder]Drivers) directories (I have to, I'm installing my drivers). The error occurred at the start of the coping process of these files. Its only happened on the files that should be copied to the the System32 directory, the other files (to INSTALLDIR ) are coping successfully (those who come before the system32's files).

I don't use static path, only Installshield properties.
I'm creating only one directory in the Program Files directory .

thanks in advanced.

Sounds like things should work ok then (as they do on the other machines).  have you tried running with a verbose installation log while installing on the machine that fails?


Maybe that will provide some more insight.
IysAuthor Commented:
I found what was the problem.
One of the component had "everyone" destination permission, after remove it the problem solved.

Thanks you anyway.

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now