![]() It got a lot of helpful votes in just two days. I think macario1983's comment points at the real troublemaker. The generic workaround is to disable this install step by disabling the installation of the ETW performance counters. This issue has been dogging users for a long time, but they are having trouble finding the root cause. Searching for "nodejs install 0xc0000409" takes you to this bug report, notable from December 2015. STATUS_STACK_BUFFER_OVERRUN is a stack corruption error, triggered by code that protects against viral attacks. This is the relevant part of the log and where the install keels over, noise removed. DLL: C:\WINDOWS\Installer\MSI33C1.tmp, Entrypoint: CAQuietExecĬAQuietExec: Error 0xc0000409: Command line returned an error. MSI (s) (74:A0) : Invoking remote custom action. MSI (s) (74:88) : Executing op: CustomActionSchedule(Action=RegisterEventManifest,ActionType=3073,Source=BinaryData,Target=CAQuietExec,CustomActionData="wevtutil.exe" im "C:\Program Files\nodejs\node_etw_provider.man") Wait for the operating system to apply the permissions that you have selected to all child folders.MSI (s) (74:88) : Executing op: ActionStart(Name=RegisterEventManifest,) In the Permissions tab, select the SYSTEM entry and click Edit.Ĭlick the Applies to dropdown and select This folder, subfolder, and files. ![]() If prompted, approve the User Account Control. If not, select the Allow check box.Ĭlose the Permissions dialog and return to the Properties dialog. Select the SYSTEM user account, and verify in the Permissions section that Full Control is set to Allow. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |