>Did they perform install under admin login?

Hope so. At least the ISD package will run under admins privileges only. (But they can use the "run as" dialoge as well.)

Assuming ALLUSERS is set:
It somehow feels that the ms installer will add information to the object.
IOW the installer scans all "power users" and sets rights to the elements installed for those users. This will survive a change of user groups. A new install scans trough the list of "power user", doesn't find one, so nothing is set. This is just guessing.

Agnes
>
>>
>>it finaly comes out that they restricted the user to user group "user" - but they have done this months ago.
>>
>>We have set them back to "power users" and everything works as expected.
>>
>>This does not explain why it works on friday, but for now the customer can work.
>>
>>Do you (or somebody else) has an idea how this can happen?
>>
>>Old Version istalled, users are "power user" -> all runs as expected
>>user changed to "user" -> all runs as expected (even registry r/w access to HKEY_LOCAL_MACHINE)
>>new version installed -> dlls not found, after putting a copy of the dlls to the exe registry fails
>>new version deinstalled, old version installed -> dlls not found, after putting a copy of the dlls to the exe registry fails
>>
>>
>>Anyway I set the ALLUSER msi property to "1" via Installscript now.
>>
>>Thanks for your asistance
>
>>>