Node js setup wizard ended prematurely because of an error

Node.js setup wizard ended prematurely #8663

I am trying to install node JS on my windows-7 desktop. but unable to install it error msg is : Node.js setup wizard ended prematurely

I have run command : reg query HKLM /f node.js /s

C:UsersAnand Vaidya>reg query HKLM /f node.js /s

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstallerFolders
C:UsersI.alamAppDataRoamingMicrosoftWindowsStart MenuProgramsNode.j
s REG_SZ 1

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstallerUserData
S-1-5-18Components7AF2F219CD048254396417AD1299EB7B
B846977CE014ABB47BB58551CBFE7ED1 REG_SZ C:Program Files (x86)Safari
Apple Application SupportWebKit.resourcesinspectorShowMoreDataGridNode.js

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstallerUserData
S-1-5-21-2313175759-918084051-1754577449-1002Components2DE2CA3205882EA5493CB7A
C9277A426
96C4018C0F4F98544B0233DD280838D5 REG_SZ 01:SOFTWARENode.jsComponent
sEnvironmentPathNpmModules

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstallerUserData
S-1-5-21-2313175759-918084051-1754577449-1002Components3FA9057E0CD5FF64F8FB48C
DCA47A800
96C4018C0F4F98544B0233DD280838D5 REG_SZ C:Program Files (x86)nodejs
node_modulesnpmnode_modulesnode-gypnode_modulespath-arraynode_modulesarra
y-indexnode_modulesdebugnode.js

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstallerUserData
S-1-5-21-2313175759-918084051-1754577449-1002ComponentsA37CEAA6FEC91A956AE3C47
2F83A6BBE
96C4018C0F4F98544B0233DD280838D5 REG_SZ 02:SOFTWARENode.jsComponent
sEnvironmentPathNode

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstallerUserData
S-1-5-21-2313175759-918084051-1754577449-1002ComponentsC135159586665BC59BEC5EA
FE5D8F927
96C4018C0F4F98544B0233DD280838D5 REG_SZ 01:SOFTWARENode.jsComponent
sDocumentationShortcuts

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstallerUserData
S-1-5-21-2313175759-918084051-1754577449-1002ComponentsF93E3E7F66A6A8553ABF580
A6DFA4CE1
96C4018C0F4F98544B0233DD280838D5 REG_SZ 01:SOFTWARENode.jsInstallPa
th

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionInstallerUserData
S-1-5-21-2313175759-918084051-1754577449-1002Products96C4018C0F4F98544B0233DD2
80838D5InstallProperties
DisplayName REG_SZ Node.js

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionPerflib_V2Provi
ders<1e2e15d7-3760-470e-8699-b9db5248edd5> <3a22a8ec-297c-48ac-ab15-33ec93033fd
8>
NeutralName REG_SZ Node.js

HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftWindowsCurrentVersionUninsta
ll
DisplayName REG_SZ Node.js

HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftWindows NTCurrentVersionPerf
lib_V2Providers<1e2e15d7-3760-470e-8699-b9db5248edd5> <3a22a8ec-297c-48ac-ab15
-33ec93033fd8>
NeutralName REG_SZ Node.js

The text was updated successfully, but these errors were encountered:

@vaidyaanand Thanks for reporting! That is actually an interesting list of registry entries. Would you also be able to create an installation log with

and share it here? Thanks!

InstallLog.txt
Please check my install logs

@joaocgreis I have uploaded the logs please check it.

Property(S): ProductToBeRegistered = 1
MSI (s) (94:78) [16:50:21:415]: MainEngineThread is returning 1603
MSI (s) (94:E8) [16:50:21:417]: RESTART MANAGER: Session closed.
MSI (s) (94:E8) [16:50:21:418]: User policy value ‘DisableRollback’ is 0
MSI (s) (94:E8) [16:50:21:418]: Machine policy value ‘DisableRollback’ is 0
MSI (s) (94:E8) [16:50:21:418]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (94:E8) [16:50:21:418]: Note: 1: 1402 2: HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionInstallerRollbackScripts 3: 2
MSI (s) (94:E8) [16:50:21:419]: Note: 1: 1402 2: HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionInstallerRollbackScripts 3: 2
MSI (s) (94:E8) [16:50:21:419]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (94:E8) [16:50:21:420]: Restoring environment variables
MSI (s) (94:E8) [16:50:21:420]: Destroying RemoteAPI object.
MSI (s) (94:9C) [16:50:21:420]: Custom Action Manager thread ending.
MSI (c) (14:18) [16:50:21:423]: Back from server. Return value: 1603
MSI (c) (14:18) [16:50:21:424]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (14:18) [16:50:21:424]: PROPERTY CHANGE: Deleting SECONDSEQUENCE property. Its current value is ‘1’.
Action ended 16:50:21: ExecuteAction. Return value 3.
MSI (c) (14:18) [16:50:21:424]: Doing action: FatalError
MSI (c) (14:18) [16:50:21:424]: Note: 1: 2205 2: 3: ActionText
Action 16:50:21: FatalError.
Action start 16:50:21: FatalError.
Action 16:50:21: FatalError. Dialog created
Action ended 16:50:23: FatalError. Return value 2.
Action ended 16:50:23: INSTALL. Return value 3.
MSI (c) (14:18) [16:50:23:498]: Destroying RemoteAPI object.
MSI (c) (14:F8) [16:50:23:499]: Custom Action Manager thread ending.
Property(C): UpgradeCode = <47c07a3a-42ef-4213-a85d-8f5a59077c28>
Property(C): INSTALLDIR = C:Program Filesnodejs

MSI (s) (94:78) [16:50:20:944]: Executing op: ComponentUnregister(ComponentId=<1a357df6-3af1-5a76-ae55-3676ccfa4513>,ProductKey=,BinaryType=1,)
MSI (s) (94:78) [16:50:20:944]: Executing op: ComponentUnregister(ComponentId=,ProductKey=,BinaryType=1,)
MSI (s) (94:78) [16:50:20:945]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)
MSI (s) (94:78) [16:50:20:945]: Error in rollback skipped. Return: 5
MSI (s) (94:78) [16:50:20:948]: Calling SRSetRestorePoint API. dwRestorePtType: 13, dwEventType: 103, llSequenceNumber: 281, szDescription: «».
MSI (s) (94:78) [16:50:20:948]: The call to SRSetRestorePoint API succeeded. Returned status: 0.
MSI (s) (94:78) [16:50:20:948]: Unlocking Server
MSI (s) (94:78) [16:50:21:349]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is ‘1’.
Action ended 16:50:21: INSTALL. Return value 3.
Property(S): UpgradeCode = <47c07a3a-42ef-4213-a85d-8f5a59077c28>
Property(S): INSTALLDIR = C:Program Filesnodejs
Property(S): ApplicationProgramsFolder = C:ProgramDataMicrosoftWindowsStart MenuProgramsNode.js
Property(S): NpmFolder = C:Program Filesnodejsnode_modulesnpm
Property(S): AppDataDir = C:Usersa.prasadAppDataRoamingnpm

s) (94:78) [16:50:08:009]: Source for file ‘npm.sh’ is compressed
InstallFiles: File: npm, Directory: C:Program Filesnodejs, Size: 867
MSI (s) (94:78) [16:50:08:010]: Executing op: CacheSizeFlush(,)
MSI (s) (94:78) [16:50:08:010]: Executing op: ActionStart(Name=RollbackRegisterPerfmonManifest,,)
Action 16:50:08: RollbackRegisterPerfmonManifest.
MSI (s) (94:78) [16:50:08:013]: Executing op: CustomActionSchedule(Action=RollbackRegisterPerfmonManifest,ActionType=3393,Source=BinaryData,Target=CAQuietExec,CustomActionData=»unlodctr.exe» /m:»C:Program Filesnodejsnode_perfctr_provider.man»)
MSI (s) (94:78) [16:50:08:013]: Executing op: ActionStart(Name=RegisterPerfmonManifest,,)
Action 16:50:08: RegisterPerfmonManifest.
MSI (s) (94:78) [16:50:08:014]: Executing op: CustomActionSchedule(Action=RegisterPerfmonManifest,ActionType=3073,Source=BinaryData,Target=CAQuietExec,CustomActionData=»lodctr.exe» /m:»C:Program Filesnodejsnode_perfctr_provider.man» «C:Program Filesnodejs»)
MSI (s) (94:40) [16:50:08:016]: Invoking remote custom action. DLL: C:WindowsInstallerMSIFF01.tmp, Entrypoint: CAQuietExec
MSI (s) (94:9C) [16:50:08:016]: Generating random cookie.
MSI (s) (94:9C) [16:50:08:017]: Created Custom Action Server with PID 1672 (0x688).
MSI (s) (94:30) [16:50:08:036]: Running as a service.
MSI (s) (94:30) [16:50:08:037]: Hello, I’m your 32bit Elevated Non-remapped custom action server.
CAQuietExec:
CAQuietExec: Error 0x8007000d: Command line returned an error.
CAQuietExec: Error 0x8007000d: QuietExec Failed
CAQuietExec: Error 0x8007000d: Failed in ExecCommon method
CustomAction RegisterPerfmonManifest returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 16:50:08: InstallFinalize. Return value 3.
MSI (s) (94:78) [16:50:08:485]: User policy value ‘DisableRollback’ is 0
MSI (s) (94:78) [16:50:08:485]: Machine policy value ‘DisableRollback’ is 0
MSI (s) (94:78) [16:50:08:507]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1228178997,LangId=1033,Platform=589824,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (94:78) [16:50:08:507]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (94:78) [16:50:08:507]: Executing op: DialogInfo(Type=1,Argument=Node.js)
MSI (s) (94:78) [16:50:08:507]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
Action 16:50:08: Rollback. Rolling back action:
Rollback: RegisterPerfmonManifest
MSI (s) (94:78) [16:50:08:510]: Executing op: ActionStart(Name=RegisterPerfmonManifest,,)
MSI (s) (94:78) [16:50:08:510]: Executing op: ProductInfo(ProductKey=,ProductName=Node.js,PackageName=node-v4.5.0-x64.msi,Language=1033,Version=67436544,Assignment=1,ObsoleteArg=0,ProductIcon=NodeIcon,,PackageCode=<57fea546-1c5c-439f-b926-55347378c5f5>. InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)
Rollback: RollbackRegisterPerfmonManifest
MSI (s) (94:78) [16:50:08:511]: Executing op: ActionStart(Name=RollbackRegisterPerfmonManifest,,)
MSI (s) (94:78) [16:50:08:511]: Executing op: CustomActionRollback(Action=RollbackRegisterPerfmonManifest,ActionType=3393,Source=BinaryData,Target=CAQuietExec,CustomActionData=»unlodctr.exe» /m:»C:Program Filesnodejsnode_perfctr_provider.man»)
MSI (s) (94:78) [16:50:08:514]: Invoking remote custom action. DLL: C:WindowsInstallerMSIF5.tmp, Entrypoint: CAQuietExec
CAQuietExec:
CAQuietExec: Warning: From C:Program Filesnodejsnode_perfctr_provider.man, unable to find matched provider <793c9b44-3d6b-4f57-b5d7-4ff80adcf9a2>in system repository, error code is 2.
Rollback: Copying new files
MSI (s) (94:78) [16:50:08:567]: Executing op: ActionStart(Name=InstallFiles,Description=Copying new files,Template=File: [1], Directory: [9], Size: [6])
MSI (s) (94:78) [16:50:08:568]: Executing op: SetTargetFolder(Folder=C:Program Filesnodejs)
MSI (s) (94:78) [16:50:08:568]: Executing op: FileRemove(,FileName=C:Program Filesnodejsnpm,,)
MSI (s) (94:78) [16:50:08:568]: Note: 1: 2318 2:
MSI (s) (94:78) [16:50:08:569]: Executing op: SetTargetFolder(Folder=C:Program Filesnodejsnode_modulesnpm)
MSI (s) (94:78) [16:50:08:569]: Executing op: FileRemove(,FileName=C:Program Filesnodejsnode_modulesnpmnpmrc,,)
MSI (s) (94:78) [16:50:08:570]: Note: 1: 2318 2:
MSI (s) (94:78) [16:50:08:570]: Executing op: SetTargetFolder(Folder=C:Program Filesnodejs)
MSI (s) (94:78) [16:50:08:570]: Executing op: FileRemove(,FileName=C:Program Filesnodejsnpm.cmd,,)
MSI (s) (94:78) [16:50:08:571]: Note: 1: 2318 2:
MSI (s) (94:78) [16:50:08:571]: Executing op: FileRemove(,FileName=C:Program Filesnodejsnodevars.bat,,)
MSI (s) (94:78) [16:50:08:572]: Note: 1: 2318 2:
MSI (s) (94:78) [16:50:08:572]: Executing op: FileRemove(,FileName=C:Program Filesnodejsnode_perfctr_provider.man,,)
MSI (s) (94:78) [16:50:08:572]: Note: 1: 2318 2:
MSI (s) (94:78) [16:50:08:573]: Executing op: FileRemove(,FileName=C:Program Filesnodejsnode_etw_provider.man,,)
MSI (s) (94:78) [16:50:08:574]: Note: 1: 2318 2:
MSI (s) (94:78) [16:50:08:574]: Executing op: FileRemove(,FileName=C:Program Filesnodejsnode.exe,,)
MSI (s) (94:78) [16:50:08:576]: Note: 1: 2318 2:
MSI (s) (94:78) [16:50:08:576]: Executing op: SetTargetFolder(Folder=C:Program Filesnodejsnode_modulesnpmnode_modulesnpm-registry-clientnode_modulesconcat-stream)
MSI (s) (94:78) [16:50:08:576]: Executing op: FileRemove(,FileName=C:Program Filesnodejsnode_modulesnpmnode_modulesnpm-registry-clientnode_modulesconcat-streamindex.js,,)
MSI (s) (94:78) [16:50:08:577]: Note: 1: 2318 2:
MSI (s) (94:78

All above pasted errors are from this log file

@joaocgreis Did you find any solution ?

and share the resulting file here?

I have resolved my Issue by just marking «performance counters» (inside installation setup) to «install this feature when require» during installation.

Источник

NodeJS install problem — Error 1603 #6547

version: any
platform: Windows 7 64 bit
subsystem: none

So yesterday I wanted to update my Node version, unfortunately, even though the update was a success, when checking my Node version it was still displaying an old version. Whatever I tried, there was no way to get Node updated properly. So I decided (I’m on Windows btw) to remove all my Node folders and NPM folders.

Then I downloaded the .msi file from the Node site. However, at the end of installation a rollback was done and the installation ended prematurely.

So I tried a few things, like starting the installation from command line. Starting command line as an administrator and trying the install. Trying older version, .exe files. Also installed Chocolatey and tried to install Node through there. However, it all failed. So even though I googled for hours, tried it all, I have no more clue what to do. Maybe there is something in Registrar from old Node files that is blocking the install? It’s a wild guess. I also removed all temp files and tried the install. No result.

I also logged the installation progress;

CAQuietExec: Error 0x8007000d: Command line returned an error.
CAQuietExec: Error 0x8007000d: QuietExec Failed
CustomAction RegisterPerfmonManifest returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Any suggestions are super welcome!

The text was updated successfully, but these errors were encountered:

Источник

Это может помочь кому-то в будущем. Я получил аналогичное сообщение от установщика и обнаружил, что могу перейти в командную строку и запустить MSI с параметром командной строки, чтобы он создал файл журнала (например, node-v0.10.24-x64.msi /lxv C:LogsNodejs.log), где можно выбрать, как будет называться журнал и куда он пойдет.

В моем случае мы работаем в среде домена Active Directory, и некоторые из наших папок, которые обычно являются локальными, перенаправляются на общий сетевой ресурс, поэтому они всегда там, независимо от того, на какой компьютер мы входим. В основном в пользу нашей папки «Мои документы».

При просмотре журнала я обнаружил фактическую ошибку, которую я получал:

• WixCreateInternetShortcuts: ошибка 0x80070005: не удалось сохранить ярлык ‘ad.localsystemusers Start MenuProgramsNode.jsNode.js Website.url’
• WixCreateInternetShortcuts: Ошибка 0x80070005: не удалось создать ярлык Интернета
• CustomAction WixCreateInternetShortcuts вернул фактический код ошибки 1603 (обратите внимание, что это может быть не на 100% точным, если перевод выполнялся внутри песочницы).

Разрешение (для меня)

Как ни странно, сначала просто запустить расширенную командную строку администратора, а затем запустить MSI, чтобы установить его правильно.

I think разница в том, что когда вы дважды щелкаете MSI и он увеличивается, он запускается как TrustedInstaller и хотя у этой учетной записи есть доступ ко всему в моем ящике, у нее нет доступа к сети. Когда я запускаю эскалированную командную строку, она работает как me, но уже эскалировано (MSI никогда не нужно запрашивать эскалацию), так что это работает.

Заключительное примечание:

По состоянию на 7 команда node.js, наконец, отследила проблему с установщиком, а начиная с 22 и далее это больше не должно быть для нас проблемой. Я протестировал для них раннюю версию программы установки, чтобы убедиться, что она работает у меня и при установке не возникло проблем.

https://github.com/joyent/node/issues/5849#issuecomment-123905214

На момент написания этой статьи, 7, текущая версия все еще была 30, поэтому я думаю, что x.2015 еще не был выпущен в массы.

For the last 3 days I have been trying to figure out how to install node.js. I tried every solution that I found on the internet, like disabling certain components during installation, installing both x86 and x64 etc, none of them worked.
My OS is Windows 10 x64. I tried different versions of node.js and they all return the same error shown in the screenshot below.
I tried installing through the command line and got the log. But I could not find anything useful from the log either. Please help.
The log can be found here: this path : https://drive.google.com/open?id=1OkkK36hlQeBX0xTNuOuilGaNr1u3S55e

MSI (s) (74:88) [20:49:45:955]: Executing op: ActionStart(Name=RegisterEventManifest,,)
MSI (s) (74:88) [20:49:45:961]: Executing op: CustomActionSchedule(Action=RegisterEventManifest,ActionType=3073,Source=BinaryData,Target=CAQuietExec,CustomActionData="wevtutil.exe" im "C:Program Filesnodejsnode_etw_provider.man")
MSI (s) (74:A0) [20:49:45:969]: Invoking remote custom action. DLL: C:WINDOWSInstallerMSI33C1.tmp, Entrypoint: CAQuietExec
CAQuietExec: Error 0xc0000409: Command line returned an error.
This is the relevant part of the log and where the install keels over, noise removed. 0xc0000409 is very, very nasty. STATUS_STACK_BUFFER_OVERRUN is a stack corruption error, triggered by code that protects against viral attacks.
Searching for "nodejs install 0xc0000409" takes you to this bug report, notable from December 2015. This issue has been dogging users for a long time, but they are having trouble finding the root cause. The generic workaround is to disable this install step by disabling the installation of the ETW performance counters.
Which works, but is but a band-aid. I think macario1983's comment points at the real troublemaker. It got a lot of helpful votes in just two days. And points at the kind of viral rootkit that programmer's voluntarily install, the kind that can so easily cause a STATUS_STACK_BUFFER_OVERRUN error with no decent way to identify the code that causes it. Anti-malware has become a cure that is worse than the disease, Avast in particular is a truly awful product and does not belong on a programmer's machine.
So decent advice is to 1: disable the anti-malware product before installing Node. 2: get rid of completely if it is Avast. 3: disable the performance counter registration. 4: try the updated installer, patched 4 days ago.

I disabled the AVG antivirus(version 18.4.3056) but not windows firewall and then i was able to install nodejs.

Possible options to solve this:
1. Removing previous installations traces
If you have previous installations, make sure that they were uninstaled completely. If HKLMSOFTWAREMicrosoftWindows NTCurrentVersionPerflib_V2Providers{1e2e15d7-3760-470e-8699-b9db5248edd5} record exist in your register, remove it.
2. Disabling Performance Counters
If you don't need Performance counters feature, try to install without it (or maybe even without Event Tracing).
3. Disabling security and giving the full permissions
Clean Temp Folder
Disable your antivirus/firewall for the period of installation.
C:/users/$user/AppData/Local/Temp- Right Click on Temp and go to Properties > select Security Tab > give the user permissions by checking Full Control on permission
Install Node.js

I had today the same problem with Windows 10 64 bit and Node.js 8.11.2: disabling completly Avast just for the time of the installation solved the issue.
I was trying to install Node.js through node-v8.11.2-x64.exe, but it was rolling back every time at the end. The error in the event log was about wevtutil.exe, version 10.0.17134.1

I had the same issue on a Windows 2012R2 server installing node-v8.11.2-x64, and disabled the McAfee anti-virus to no avail. When I went to clean out the TEMP folder as suggested in this thread, I noticed that several files and folders were locked and could not be deleted, so I rebooted the machine (with the anti-virus disabled). After the reboot, I noticed that the locked temp files had been deleted, and I was able to install node.js, including the Performance Counters and Event Tracking options.

Related

So I botched an msi installer and deployed it after only testing installation, not uninstall (bad I know, added running of an exe after install, but forgot to specify that it should only occur on install not uninstall).
I found the Windows Installer Cleanup util, and the related msizap that I'll use to automate the process. The problem now is that when a newer version is installed on top afterwards, the advertised shortcut still tries to do a repair (or whatever it's actually doing trying to load the old version) and fails. Running the program directly from the file works fine, but I need to remove the advertised shortcuts in an automated way. It doesn't need to be incredibly robust, fairly small private beta install-base right now, so can assume that shortcuts are in the originally installed locations of desktop and start menu.
Are there any special concerns I need to take into account for an advertised shortcut or can I just treat it as any other file and just remove it?

AFAIK adverited shortcuts are responsible for doing the setup.
Those are special lnk files that have point to the installer with a spicel param that will preform the setup when they are activated (you can see the info with notepad or hex editor).
never the less, MSI zap should have remove all trace of the setup.
Does the setup runs if you do a zap then press the shortcut? or you get an error?

As far as the shortcut is concerned, it's just a normal file that can be deleted.
However I'll caution you about using MSIZAP - it is really a last resort and leaves a lot of information behind, shared DLL counts, registry entries, files, etc. Once removing the Windows Installer information you then need to remove any information related to your program from the registry. SharedDLL ref counts are the worst thing as they'll screw up when you try to reinstall/uninstall with the new MSI.
Rob has a good post up detailing some of the pitfalls of using MSIZAP. It's not something you want to use unless you're prepared to manually hunt down all the registry information it leaves behind.

After going through a windows 10 re-installation due to a windows update crashing my laptop, I was left with re-installing many applications. One of them being node.js. When I tried to install it through the windows installer, I kept getting 'setup wizard ended prematurely because of an error message'. I am not sure what the problem is. I used x64 version which is what my OS is and there is no nodejs folder in program files. When I logged the installation this message popped in a lot of the lines has no eligible binary patches. Before the no eligible lines there were error logs such as:
'WixSchedInternetShortcuts: Error 0x8007000d: failed to add temporary row, dberr: 1, err: Directory_'
'WixSchedInternetShortcuts: Folder 'ApplicationProgramsFolder' already exists in the CreateFolder table; the above error is harmless'
If that is not enough information please advice me on how to send the full logs without spamming huge text in the thread. Thank you.
The MSI log file:
https://gist.github.com/luki2000/ab00476127d54aaf610d8bda84d40a64

Maybe try to search the log for "value 3" as explained by Rob Mensching in his blog. Doing so will find the locations in the log file that describe errors of significance.
Many people use dropbox, gdisk or similar to post logs. Some put it on github (just a sample log for OP, leaving in for reference). Check that last link, is that the same problem you see perhaps? (search for "value 3" as explained above - without the quotes of course). Looks like there is an error creating an Internet shortcut. Perhaps that is a Windows 10 problem? I will take a quick look.
I am betting Bob Arnson knows what this problem is outright. He will probably give us the real answer, see below for my workaround.
The correct thing to do overall, would probably be to communicate the problem back to the Node.js guys so they can fix the problem once and for all.
UPDATE: Maybe see if this answer helps you: node.js installer failing with 'CAQuietExec Failed' and 1603 error code on Windows 7. Essentially un-check Event tracing(ETW) in the setup's feature dialog - or you can try to launch the MSI from an elevated command prompt.
UPDATE: There seem to be two Internet shortcuts configured for this MSI in the WixInternetShortcut table. I would just create a transform to remove these two shortcuts and try a reinstall. If you feel bold and fearless and like to break the law, you can delete the two rows from the table and just save directly to the MSI itself. This is never the right thing to do if you are a deployment specialists. The original MSI is sacred, but if this is for your own system and you need to get something done, that would work. Then you just install the MSI direct afterwards. Otherwise you can install the transform after creating it with a simple command line:
msiexec.exe /i node-v8.11.2-x64.msi TRANSFORMS="C:MyTransform"
You can create the transform using Orca, InstEd or SuperOrca or any commercial tool that supports creating transforms.
In case you don't know, transforms are little database fragments that are applied to the original MSI (which is also a database under the hood). After the transform is applied the in-memory version of the MSI is the MSI + the changes from the transform.

Since upgrading from MAMP 3 to MAMP 4, the GUI hangs on each action. Clicking something like the menu occurs after around 30 seconds of the spinning wheel of death. This happens for any action within the interface. Running 10.12.2
This almost makes the software unusable, as I can't configure the interface to begin development.

My experience was identical. Searching for some errors I ended up running Tools > Verify MySQL Databases... Among tons of OK'ed databases, several had errors - innodb_index_stats, innodb_table_stats, slave_master_info, slave_relay_log_info, and slave_worker_info.
From here a search lead me to mysql error: Table “mysql”.“innodb_table_stats” not found.
So, I deleted all the .frm and .ibd of the tables above and I ran the five-tables.sql file in Terminal: source five-tables.sql
Now MAMP Pro 4 runs smoothly and responsive.
Thanks, Kay Nelson.

I ended up doing a search for MAMP in all parts of the file, and removed every reference to it, after running the uninstaller.
I also removed references to any PHP & memcache not in the /Applications/MAMP folder.
I renamed /Applications/MAMP to /Applications/MAMP-old and reinstalled. This set everything up fresh and appears to be working. Something with a conflict with a system binary or other package was causing the issue.

Due to problems with the windows installer 5 I must rename msi.dll for reinstallation. That's not possible in save mode/as administrator (access denied). Of course the service is stopped. Any hints?
Edit: My problem is that I can't install msi files anymore. Everytime after some dialogs I get an error message that the corresponding msi file can't be read. I have tried any infos I found in the www universe and lost a lot of time already. E. g. I replaced the registry settings, used sfc /scannow without success.
In Windows 7 there is no dllcache, so I really don't know what is preventing renaming.

My problem is that I can't install msi files anymore. Everytime after some dialogs
I get an error message that the corresponding msi file can't be read
This sounds a little bit strange. If you see MSI dialogs and the install fails when you kick it off there must be something else wrong. I assume you have, but have you verified that the problem exists with multiple MSI files? Try with a fresh MSI file, preferably one that you downloaded fresh from the Internet. Try to run from the local disk and from a network disk.
Have you enabled logging for the install? Try to do so with flush to log enabled (the ! character enables continuous flushing to log so that an msiexec.exe crash doesn't leave an empty log file):
msiexec.exe /i C:PathYour.msi /L*vx! C:Your.log
See msifaq.com for more details (logging faq entry). Search for "value 3" in the log file to find errors as explained by Rob Mensching (Wix & Orca author).
Also try to disable any anti virus software and / or desktop security that may be interferring with the file extraction from the MSI's cab file. Is there plenty of disk space? Are there any errors found during a disk scan?

Are you trying to revert to a previous version of Windows Installer? Here is some information: http://support.microsoft.com/?kbid=315346.
I suppose you could use system restore as well, but that would have other side effects.
What is the overall problem? Windows Installer 5 does not seem to introduce anything very controversial: http://msdn.microsoft.com/en-us/library/windows/desktop/dd408114(v=vs.85).aspx

There is a very bad error telling you that another application is installing, when theres no such installation going on actually, and this error keeps coming after restart.
There is a solution but for every install involving deleting the registery key Inprogress, and stopping and starting the installer service, you have to do this which is really bad.
So, is there any permanent solution to this ?
http://www.appdeploy.com/msierrors/detail.asp?id=111

The permanent solution is to apply all the updates for the windows 7. All other solutions need to be applied again and again.
But one must also know this http://www.appdeploy.com/msierrors/detail.asp?id=111

In window 10, Press control + alt+ del
Search Window Installer processes.
End both Processes.
Try to install the application again.
It was due to background downloading and installation/upgradation of other applications by windows.