[BUG] Flowise WIll Not Install Correctly - Does it run natively on Windows 11 ARM-64 machines?

[myonlinematters]

I have been trying to install flowise into a Microsoft Surface 7 ARM-64 laptop running Windows 11 without success. I have exited all non-essential applications and have turned off my antivirus (Bitdefender). Updated node.js and nvm to latest versions as well.

Install command and response shown below. The important elements are probably the last ~50 lines of the error message It is obvious several directories are not being installed - the question is why? Is it because the machine is an ARM64 machine?

---

C:\Windows\System32>npm install -g flowise --legacy-peer-deps --unsafe-perm

npm warn deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs
npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated @oclif/[email protected]: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Use your platform's native atob() and btoa() methods instead
npm warn deprecated @aws-sdk/[email protected]: This package has moved to @smithy/signature-v4
npm warn deprecated @aws-sdk/[email protected]: This package has moved to @smithy/protocol-http
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: Package is no longer maintained
npm warn deprecated [email protected]: Use your platform's native DOMException instead
npm warn deprecated [email protected]: cross-spawn no longer requires a build toolchain, use it instead
npm warn deprecated [email protected]: Use mz or fs-extra^3.0 with Promise Support
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: This package is no longer supported.
npm warn deprecated [email protected]: < 22.8.2 is no longer supported
npm warn deprecated [email protected]: Version no longer supported. Upgrade to @latest
npm warn cleanup Failed to remove some directories [
npm warn cleanup [
npm warn cleanup '\\?\C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\sharp',
npm warn cleanup [Error: EBUSY: resource busy or locked, rmdir 'C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\sharp'] {
npm warn cleanup errno: -4082,
npm warn cleanup code: 'EBUSY',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\sharp'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup '\\?\C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\couchbase',
npm warn cleanup [Error: EBUSY: resource busy or locked, rmdir 'C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\couchbase'] {
npm warn cleanup errno: -4082,
npm warn cleanup code: 'EBUSY',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\couchbase'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup '\\?\C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\faiss-node',
npm warn cleanup [Error: EBUSY: resource busy or locked, rmdir 'C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\faiss-node'] {
npm warn cleanup errno: -4082,
npm warn cleanup code: 'EBUSY',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\faiss-node'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup '\\?\C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\canvas',
npm warn cleanup [Error: EBUSY: resource busy or locked, rmdir 'C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\canvas'] {
npm warn cleanup errno: -4082,
npm warn cleanup code: 'EBUSY',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\canvas'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup '\\?\C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules',
npm warn cleanup [Error: EBUSY: resource busy or locked, rmdir 'C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\canvas'] {
npm warn cleanup errno: -4082,
npm warn cleanup code: 'EBUSY',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\canvas'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup '\\?\C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise',
npm warn cleanup [Error: EBUSY: resource busy or locked, rmdir 'C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\faiss-node'] {
npm warn cleanup errno: -4082,
npm warn cleanup code: 'EBUSY',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\faiss-node'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup '\\?\C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\@smithy',
npm warn cleanup [Error: EPERM: operation not permitted, rmdir 'C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules@smithy\hash-blob-browser\node_modules'] {
npm warn cleanup errno: -4048,
npm warn cleanup code: 'EPERM',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\@smithy\hash-blob-browser\node_modules'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup '\\?\C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\llamaindex\node_modules',
npm warn cleanup [Error: EPERM: operation not permitted, rmdir 'C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\llamaindex\node_modules\cohere-ai\dist'] {
npm warn cleanup errno: -4048,
npm warn cleanup code: 'EPERM',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\llamaindex\node_modules\cohere-ai\dist'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup '\\?\C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\@opentelemetry\otlp-transformer',
npm warn cleanup [Error: EPERM: operation not permitted, rmdir 'C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules@opentelemetry\otlp-transformer\node_modules@opentelemetry'] {
npm warn cleanup errno: -4048,
npm warn cleanup code: 'EPERM',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\@opentelemetry\otlp-transformer\node_modules\@opentelemetry'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup '\\?\C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\@opentelemetry\sdk-trace-base',
npm warn cleanup [Error: EPERM: operation not permitted, rmdir 'C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules@opentelemetry\sdk-trace-base'] {
npm warn cleanup errno: -4048,
npm warn cleanup code: 'EPERM',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\@opentelemetry\sdk-trace-base'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup '\\?\C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\mathjax-full',
npm warn cleanup [Error: EPERM: operation not permitted, rmdir 'C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\mathjax-full\components\src\output\chtml'] {
npm warn cleanup errno: -4048,
npm warn cleanup code: 'EPERM',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\mathjax-full\components\src\output\chtml'
npm warn cleanup }
npm warn cleanup ]
npm warn cleanup ]
npm error code 1
npm error path C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\grpc-tools
npm error command failed
npm error command C:\WINDOWS\system32\cmd.exe /d /s /c node-pre-gyp install
npm error response status 404 Not Found on https://node-precompiled-binaries.grpc.io/grpc-tools/v1.12.4/win32-arm64.tar.gz
npm error node-pre-gyp info it worked if it ends with ok
npm error node-pre-gyp info using [email protected]
npm error node-pre-gyp info using [email protected] | win32 | arm64
npm error (node:5724) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
npm error (Use node --trace-deprecation ... to show where the warning was created)
npm error node-pre-gyp info check checked for "C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\grpc-tools\bin\grpc_tools.node" (not found)
npm error node-pre-gyp http GET https://node-precompiled-binaries.grpc.io/grpc-tools/v1.12.4/win32-arm64.tar.gz
npm error node-pre-gyp ERR! install response status 404 Not Found on https://node-precompiled-binaries.grpc.io/grpc-tools/v1.12.4/win32-arm64.tar.gz
npm error node-pre-gyp ERR! install error
npm error node-pre-gyp ERR! stack Error: response status 404 Not Found on https://node-precompiled-binaries.grpc.io/grpc-tools/v1.12.4/win32-arm64.tar.gz
npm error node-pre-gyp ERR! stack at C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules@mapbox\node-pre-gyp\lib\install.js:67:15
npm error node-pre-gyp ERR! stack at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
npm error node-pre-gyp ERR! System Windows_NT 10.0.26120
npm error node-pre-gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\@mapbox\node-pre-gyp\bin\node-pre-gyp" "install"
npm error node-pre-gyp ERR! cwd C:\Users\arthu\AppData\Roaming\npm\node_modules\flowise\node_modules\grpc-tools
npm error node-pre-gyp ERR! node -v v23.6.0
npm error node-pre-gyp ERR! node-pre-gyp -v v1.0.11
npm error node-pre-gyp ERR! not ok

[HenryHengZJ]

can you try node 20 or 18?

[myonlinematters]

When I get back to my computer I will

…

On Wed, Jan 15, 2025 at 11:28 AM Henry Heng ***@***.***> wrote: can you try node 20 or 18? — Reply to this email directly, view it on GitHub <#3869 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANZLTICLIKBMJV5IKKPXFO32KYZ4LAVCNFSM6AAAAABVFQHCW6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJSGI2TKMJTGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[isaachoo]

I tried on my surface pro 11 with snapdragon cpu with node 23. But still got the same error

[myonlinematters]

Well, I see where I can get prior versions of node (I am also running on 23), but I have never had to downgrade a package this complex and I prefer not to engage in what could be hours of work just to test. I have actually downloaded docker and installed flowise into that as described in the readme and that is working (although it is not playing well with natively installed apps like Ollama from what I can tell). So I'll leave it to the flowise folks to figure this out, since I am not the only one who seems to have this problem.