Frustrating W7 permissions issue (or so it seems)


Recommended Posts

I've used WinInstall LE to package software as part of my job for years and year with no issues. I've usually used Windows XP for packaging, but now that i support pretty much just W7 computer, I've now switched my packaging PC (which is a VM) over to W7 also.

 

I do the "before" snapshot with no issues.

 

I then install and customise the software

 

and then do the "after" snapshot

 

No issues yet.

 

After returning my package building PC back to a "clean" state, i then run the Msi to check that it installs correctly.

 

This testing stage has always worked fine on my XP VM (and i'm quite confident that it's worked on W7 also), but now i just get the error message in the attached pic linked below.

 

gallery_31269_3438_10113.png

 

I've used numerous virtualisation software, but with exactly the same outcome. I doubt that it's the Windows 7 install media, as it's all genuine.

 

I've also tried:

 

giving the account full access and owner permissions to every file and folder on the computer

 

giving the account full access to the entire registry (not that i think i'd need to do either of these steps, as the account is an admin user anyway)

 

Ensuring that the "System" account is also a local admin (again, i didnt think this would fix anything...but i did it anyway)

 

Am i doing something stupidly wrong here?

 

Link to comment
Share on other sites

I should add that this is a totally fresh install of W7 today, and the only other software on the VM is WinInstall.

 

UAC is turned off, as is Windows Firewall and Automatic Updates

Link to comment
Share on other sites

So its a UAC issue basically,do WinInstal not have a support section you can search in this regard?

 

 

Because UAC restricts privileges during the stages of an installation, developers of Windows Installer packages should not assume that their installation will always have access to all parts of the system. Windows Installer package developers should therefore adhere to the package guidelines described in Guidelines for Packages to ensure their package works with UAC and Windows Vista. A package that has been authored and tested to comply with UAC should contain the MSIDEPLOYMENTCOMPLIANT property set to 1.

http://msdn.microsoft.com/en-us/library/aa372468%28v=vs.85%29.aspx

More

http://msdn.microsoft.com/en-us/library/aa372468%28v=vs.85%29.aspx

Link to comment
Share on other sites

Yeah that sounds like it could be the issue. It's still hurting my head as to why it would error even for my admin account...when i seem to have write permissions to everything (as does the "System" account)

 

Thank you for the info though, it's given me a new direction to research

Link to comment
Share on other sites

Hi guys

 

I've been working on this even more

 

I've trawled through the settings of WinInstall to try and find the setting for "MsiDeploymentCompliant"...but i can't see it anywhere.

 

The next issue i have is that a package appears to be trying to write to a reg key which doesn't even exist (or it's trying to make it as part of the package installation). Screenshot of error below.

 

gallery_31269_3438_22437.png

 

I've modified the permissions of the key so that "everyone" has full access...but hitting "Retry" just keeps the error there (as it if's trying to write to a non-existent key rather than creating it)

Link to comment
Share on other sites

Perhaps this will help:

 

Take Ownership Shell Extension, from Rizonesoft, is a freeware shell extension that lets a user easily take ownership of objects in Windows through right-click.

With the releases of Windows Vista, and later Windows 7, more home users of Windows have experienced restrictions on accessing and modifying files that they are not marked as the owner of.

This simple shell extension makes it an easy task to simply take ownership of files in Windows.

 

http://www.afterdawn.com/software/system_tools/misc_system_tools/take_ownership_shell_extension.cfm

TakeOwnership.zip

Link to comment
Share on other sites

I think that's the same app which was linked earlier in the thread :)

 

I've just stripped out the reg keys which are causing the errors when the package is installed...and it's now installing and running fine. Hmmm

Link to comment
Share on other sites

Did you check the Guidelines for packages ?

To check for UAC compliance outside of Group Policy
  1. Log on to the computer as an administrator.
  2. Advertise the package for a per-machine installation:

    msiexec /jm package.msi

  3. Log off the computer.
  4. Log on to the computer as a standard user.
  5. Attempt to install the advertised package:

    msiexec /i package.msi

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.