https://bugs.documentfoundation.org/show_bug.cgi?id=149106
--- Comment #15 from Samuel Mehrbrodt (allotropia) <[email protected]> --- (In reply to Mike Kaganski from comment #13) > (In reply to Samuel Mehrbrodt (allotropia) from comment #11) > > RenamePrgFolder seems to be an immediate-execution DLL custom action. That > means that it would run with user credentials (not scheduled for deferred > elevated execution), and thus it would fail unconditionally when attempted > to rename anything in Program Files (where normal user doesn't have writable > permissions). Ah that makes sense. It worked fine for me when I tested this. > Another failure (even if the action were ) could be when the renamed > directory is being used; the normal MSI behavior in that case would be to > have the new files copied to a temporary directory, and schedule a reboot to > update the now-used files. But the action in question seems to try to do > manually what should be done automatically. Any hints how that can be implemented (having files updated after reboot)? > I seem to remember some discussion about the action(s); possibly we decided > then that it makes sense to keep that for now - I don't remember; but > returning the error from the action looks problematic. Yep, when testing it looked to me that returning an error did not abort the installation, but just wrote something in the log file. Not sure why this user sees a different behavior. -- You are receiving this mail because: You are the assignee for the bug.
