MSI fails with CNDL1147
See original GitHub issue- Version: 19.45.4
- Target: msi
msi bundling fails with tons of the following errors:
Error: Exit code: 1147. Command failed: C:\ … \AppData\Local\electron-builder\cache\wix\wix-4.0.0.5512.2\candle.exe -arch x64 -dappDir=C:\ … \packages\win-unpacked -pedantic -wx project.wxs
C:\Users\ ... \packages\__msi-temp-x64\project.wxs(259) : error CNDL1147 : Backslash terminate the Component/@Directory attribute's inline directory value 'resources\app.asar.unpacked\node_modules\ ... _u'. A backslash ensures a directory name will not be mistaken for a direct ory reference.
NSIS builds are running fine. Is this a bug or am I doing something wrong?
Maybe this is related to #2272?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:11 (4 by maintainers)
Top Results From Across the Web
MSI installation error 1603 - Windows Server - Microsoft Learn
This article helps fix the error 1603 that occurs when you install a Microsoft Windows Installer package. Applies to: Windows 10 - all...
Read more >How To Fix Windows Installer Package Problem (.msi issue)
MY WEBSITE: http://kingsleychimezie.weebly.com/My SOCIAL LINKS: ...
Read more >MSI failed with Error Code 1625 - Support - PDQ
Purpose: You received Error Code 1625 when attempting to install an application and want to know what it means and how to get...
Read more >Windows Installer Error 1612 | Desktop App
Whenever a product is installed, a stripped down version of the original .msi file is saved in the Windows Installer cache (%windir%\installer).
Read more >Bookshelf for Windows: Installation failure due to missing MSI ...
This message occurs when there is corruption with the MSI installation file. When this error pops up, installation nor uninstallation of ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@vaibhav6233m put the “msi” key at the same level as “win”, not under it. So:
"build": { "win": { ... }, "msi": { "warningsAsErrors": false } }
Because MSI and WiX sucks, and not so awesome as NSIS, it will take some time until all pitfalls will be catched and workarounds added. I will investigate this issue.