Error code 2869 microsoft

Looks to be a custom action Data issue, but why now? InstallEventArgs Handles Me. AfterUninstall Try If String. IsNullOrEmpty Context. OpenSubKey String. CompanyName, My. DeleteSubKeyTree My. This is the first error encountered by the installer.

This may indicate a problem with this package. The error code is Return value 3. Its current value is '1'. How are we doing? Please help us improve Stack Overflow. Take our short survey. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Windows Installer C error code Ask Question. Asked 11 years, 9 months ago.

Active 1 year, 5 months ago. Viewed 35k times. RooiWillie 2, 1 1 gold badge 30 30 silver badges 36 36 bronze badges. Skadoosh Skadoosh 2, 7 7 gold badges 39 39 silver badges 52 52 bronze badges. Add a comment. Active Oldest Votes. Here is how to do so:. Open the MSI in Orca.

Go to the CustomAction table. Find all rows that need modification. All rows whose Type value has the inscript bit set need modification. To verify:. And the Hex value with 0x the inscript bit. If result is not 0, then the row needs modification. For each of these custom action rows, perform the following steps:. Or the Hex value with 0x which is the noimpersonate bit. Convert the value back to decimal.

Save the transformed MSI, if desired, or incorporate the above steps into an existing transform file for future re-use. This command will also open up the command window in admin mode and any application you run from there will be running under administrator.

Also any Setup program get the privileges because of which it runs under the logged in admin user account. Then how is this behaviour different here? In "Everyone" installs the custom actions run as the system account because that's the way they run elevated. If you turn on impersonation they run as the installing user, but they do not run elevated, that's just how UAC systems behave. If you want the impersonated custom actions to run elevated then you must arrange to have the entire MSI install run from an elevated context, either a setup.

Visual Studio setups have custom actions that are already impersonated, which is typically why they fail onm UAC systems unless you elevate the entire install.

My Problem is either I use the. Bat file as suggested by Elizas in this thread earlier or use the setup. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums.

ClickOnce and Setup. Sign in to vote. Monday, January 22, PM. These are the steps to solve the above mentioned problems:. MSI file. Thursday, February 4, AM. So I'd suggest you generate a verbose log of the install to find the root cause: msiexec.

A workaround is to create a shortcut: msiexec. Thursday, February 1, AM. Tuesday, April 10, PM. The error code is Regards, Philippe Don't forget to mark as answer or vote as helpful to help identify good information. Answer an interesting quest ion? Create a wiki article about it! If re-downloading the package does not help then you might want to contact the package creator support to report the problem and get a new package version. Just addition, you can upload the log file to OneDrive and then post that link here.

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff microsoft.