question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

The specified module could not be found

See original GitHub issue

I’m attempting to upgrade my app from Electron v3 to v7. macOS and Linux works fine, but I’m getting the following errors on Windows:

32-bit:

Uncaught Error: The specified module could not be found.
\\?\C:\Program Files\Tidepool Uploader\resources\app.asar.unpacked\node_modules\lzo-decompress\prebuilds\win32-ia32\electron.napi.node

64-bit:

Uncaught Error: The specified module could not be found.
\\?\C:\Program Files\Tidepool Uploader\resources\app.asar.unpacked\node_modules\lzo-decompress\prebuilds\win32-x64\electron.napi.node

I’ve found some threads relating to that error appearing when some .dll’s cannot be found. I’m still using the same .dll’s that worked under Electron v3, so I thought it may be due to https://electronjs.org/docs/tutorial/using-native-node-modules#a-note-about-win_delay_load_hook, but my understanding is that win_delay_load_hook is handled by node-gyp-build?

The module’s source code can be found here: https://github.com/tidepool-org/lzo-decompress/tree/update-deps

Notes:

  • I’ve updated to the latest versions of prebuildify, node-gyp-build and napi-macros.
  • I’m using prebuildify --napi and prebuildify --arch=ia32 --napi to generate the prebuilds
  • Obviously the .node files in question are actually there

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:18 (11 by maintainers)

github_iconTop GitHub Comments

1reaction
gniezencommented, Jan 21, 2020

I was thinking maybe just another footnote in the options table, next to the --napi flag. As in, “***** Using prebuildify --napi will only support Electron v3 if not targeting a specific Electron or Node version. Use prebuildify -t 8.14.0 --napi to produce a runtime-agnostic prebuild that works in both Node v8 (and higher) and Electron v4 (and higher).”

Breaking the footnotes into a FAQ/Caveats section could also work.

1reaction
vweeverscommented, Jan 20, 2020

I remember that leveldown had issues with electron v3 and we ended up requiring a minimum of electron v4, and it was related to the delayed load hook mess. Lemme see if I can find it in GH history.

Read more comments on GitHub >

github_iconTop Results From Across the Web

How To Fix The specified module could not be found
Fixes for The specified module could not be found · Fix 1: Run the SFC scan · Fix 2: Update your device drivers...
Read more >
4 Ways to Solve the Specified Module Could Not Be Found
The specified module could not be found error is a DLL error. It usually shows on the Windows startup or warming up. This...
Read more >
The specified module could not be found | 3 Ways to Fix It
"The specified module could not be found" error often occurs on Windows startup or when launching a particular program.
Read more >
7 Ways To Fix “The Specified Module Could Not Be Found” Error
“The specified module could not be found” is a common error that usually occurs when your system tries to access missing DLL files....
Read more >
5 ways to Fix "The specified module could not be found"
How to Fix “The specified module could not be found” on Windows 11/10? · 1. Install or Repair Microsoft DirectX · 2. Download...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found