Closed barribarrier closed 1 year ago
While the installer is still running, the temporary file C:\Users\barri\AppData\Local\Temp\nsuF46A.tmp\nsis_tauri_utils.dll
does actually exist too.
I think this happens when the target system doesn't have VCRUNTIME140.dll
available.
Ran the nsis_tauri_utils.dll
file through https://github.com/lucasg/Dependencies
and it said I'm missing VCRUNTIME140.dll
.
My currently installed redistributables:
It would be awesome to have a statically linked nsis_tauri_utils.dll
(if even possible)
hmm, iirc vcruntime140 should be part of that last one in the list in your screenshot. (still, it should be statically linked like in tauri itself too)
Installing the x86 version of the latest vc_redist fixed it. Even though I'm on x64 system.
oh right, that makes sense since nsis installers are 32bit. I totally forgot about that...
Describe the bug
When running the NSIS installer, it throws the following error: Could not load: C:\Users\barri\AppData\Local\Temp\nsuF46A.tmp\nsis_tauri_utils.dll
Calls to
nsis_tauri_utils::FindProcess
ininstaller.nsi
doesn't work as a resultReproduction
npm create tauri-app@latest
Could not load: C:\Users\barri\AppData\Local\Temp\nsuF46A.tmp\nsis_tauri_utils.dll
nsis_tauri_utils::FindProcess
command didn't work.Expected behavior
Shouldn't throw any error
Platform and versions
Stack trace
No response
Additional context
No response