Build Instructions (Windows)
Follow the guidelines below for building Electron itself on Windows, for the purposes of creating custom Electron binaries. For bundling and distributing your app code with the prebuilt Electron binaries, see the application distribution guide.
- Windows 10 / Server 2012 R2 or higher
- Visual Studio 2019 (>=16.0.0) to build, but Visual Studio 2022 (>=17.0.0) is preferred - download VS 2022 Community Edition for free
- See the Chromium build documentation for more details on which Visual Studio components are required.
- If your Visual Studio is installed in a directory other than the default, you'll need to
set a few environment variables to point the toolchains to your installation path.
vs2022_install = DRIVE:\path\to\Microsoft Visual Studio\2022\Community, replacing
Communitywith your installed versions and replacing
DRIVE:with the drive that Visual Studio is on. Often, this will be
WINDOWSSDKDIR = DRIVE:\path\to\Windows Kits\10, replacing
DRIVE:with the drive that Windows Kits is on. Often, this will be
- Debugging Tools for Windows of Windows SDK 10.0.15063.468 if you plan on
creating a full distribution since
symstore.exeis used for creating a symbol store from
- Different versions of the SDK can be installed side by side. To install the
SDK, open Visual Studio Installer, select
Individual Components, scroll down and select the appropriate Windows SDK to install. Another option would be to look at the Windows SDK and emulator archive and download the standalone version of the SDK respectively.
- The SDK Debugging Tools must also be installed. If the Windows 10 SDK was installed
via the Visual Studio installer, then they can be installed by going to:
Programs and Features→ Select the "Windows Software Development Kit" →
Change→ Check "Debugging Tools For Windows" →
Change. Or, you can download the standalone SDK installer and use it to install the Debugging Tools.
- Different versions of the SDK can be installed side by side. To install the SDK, open Visual Studio Installer, select
If you don't currently have a Windows installation, dev.microsoftedge.com has timebombed versions of Windows that you can use to build Electron.
Building Electron is done entirely with command-line scripts and cannot be done with Visual Studio. You can develop Electron with any editor but support for building with Visual Studio will come in the future.
Note: Even though Visual Studio is not used for building, it's still required because we need the build toolchains it provides.
Exclude source tree from Windows Security
Windows Security doesn't like one of the files in the Chromium source code
(see https://crbug.com/441184), so it will constantly delete it, causing
gclient sync issues.
You can exclude the source tree from being monitored by Windows Security by
following these instructions.
To build for the 32bit target, you need to pass
target_cpu = "x86" as a GN
arg. You can build the 32bit target alongside the 64bit target by using a
different output directory for GN, e.g.
out/Release-x86, with different
$ gn gen out/Release-x86 --args="import(\"//electron/build/args/release.gn\") target_cpu=\"x86\""
The other building steps are exactly the same.
Visual Studio project
To generate a Visual Studio project, you can pass the
$ gn gen out/Testing --ide=vs2017
Command xxxx not found
If you encountered an error like
Command xxxx not found, you may try to use
VS2015 Command Prompt console to execute the build scripts.
Fatal internal compiler error: C1001
Make sure you have the latest Visual Studio update installed.
LNK1181: cannot open input file 'kernel32.lib'
Try reinstalling 32bit Node.js.
Error: ENOENT, stat 'C:\Users\USERNAME\AppData\Roaming\npm'
Creating that directory should fix the problem:
$ mkdir ~\AppData\Roaming\npm
node-gyp is not recognized as an internal or external command
You may get this error if you are using Git Bash for building, you should use PowerShell or VS2015 Command Prompt instead.
cannot create directory at '...': Filename too long
node.js has some extremely long pathnames, and by default git on windows doesn't handle long pathnames correctly (even though windows supports them). This should fix it:
$ git config --system core.longpaths true
error: use of undeclared identifier 'DefaultDelegateCheckMode'
This can happen during build, when Debugging Tools for Windows has been installed with Windows Driver Kit. Uninstall Windows Driver Kit and install Debugging Tools with steps described above.
Build Scripts Hang Until Keypress
This bug is a "feature" of Windows' command prompt. It happens when clicking inside the prompt window with
QuickEdit enabled and is intended to allow selecting and copying output text easily.
Since each accidental click will pause the build process, you might want to disable this
feature in the command prompt properties.