How to Download & Install Jenkins on Windows

Jenkins may be installed on either Windows or Unix platforms, but this walkthrough focuses on the Windows installation only. The Windows MSI installer registers Jenkins as a Windows service and selects a 64-bit Java runtime for you, which makes it the fastest route to a working automation server. Before opening the installer, confirm that your machine meets the requirements listed in the next section.

Jenkins Prerequisites and System Requirements

Jenkins is lightweight at rest but grows quickly once build history, workspaces, and plugins accumulate. Sizing the machine correctly at the start avoids a painful migration later.

Hardware requirements:

Software requirements:

• Jenkins runs on Java, so a supported Java Development Kit (JDK) or Java Runtime Environment (JRE) must be present. Current Jenkins releases require Java 21 or later; Java 8, 11, and 17 are no longer supported by the newest Long-Term Support line.
• A modern web browser is needed to reach the Jenkins dashboard.
• An account with administrative rights on the Windows machine is needed to register the Jenkins service.

Confirm the installed Java version from Command Prompt before you continue. If the command fails or reports a version below 21, install a supported JDK first.

:: Check the Java version available on the machine
java -version

:: Expected output resembles the following
openjdk version "21.0.5" 2024-10-15 LTS
OpenJDK Runtime Environment Temurin-21.0.5+11 (build 21.0.5+11-LTS)
OpenJDK 64-Bit Server VM Temurin-21.0.5+11 (build 21.0.5+11-LTS, mixed mode)

Release types

Jenkins publishes two release lines, and the choice affects how often you upgrade.

This walkthrough uses the LTS release, though the installation process is identical for the weekly release. With the prerequisites in place, the download can begin.

How to Download Jenkins?

Follow the steps below to obtain the Windows installer and complete a successful installation:

Step 1) Go to https://www.jenkins.io/download/ and select the platform. In our case, Windows.

Step 2) Go to the download location on your local computer and unzip the downloaded package. Double-click the unzipped jenkins.msi file. Jenkins can also run from a WAR (Web application ARchive) file, but that route is not recommended on Windows because it skips the service registration handled by the installer.

Note: Windows SmartScreen may report that it prevented an unrecognized application from starting. Select More info, then Run anyway, to continue with the signed Jenkins installer.

Step 3) In the Jenkins Setup screen, click Next.

Step 4) Choose the location where the Jenkins instance should be installed. The default location on current 64-bit installers is C:\Program Files\Jenkins. Note this path, because the initial administrator password is stored inside it. Click Next.

Step 5) The installer then asks for the service logon credentials and the port number. Supply a dedicated local or domain account and click Test Credentials, then set the port and click Test Port. Port 8080 is the default. Running Jenkins under a named service account is safer than the LocalSystem option, which grants Jenkins full access to the machine.

Step 6) Confirm the Java home directory that the installer detects, review the custom setup options, and click the Install button. Once the installation is complete, click Finish.

Step 7) During the installation process, an info panel may appear to inform you that a reboot is required at the end of the current installation. Click the OK button when the info panel appears.

The files are now on disk and the service is registered. The next stage unlocks the web interface.

How to Unblock Jenkins?

After completing the Jenkins installation phase, the controller is locked until you supply an automatically generated password. The steps below explain how to unblock the Jenkins application:

Step 1) After the installation process finishes, a browser tab opens and asks for the initial administrator password. To reach Jenkins, browse to the following path in your web browser.
http://localhost:8080

If the address above loads, the installation succeeded and the service is running.

Step 2) The initial administrator password is stored under the Jenkins installation path that you set in Step 4 of the installation. For the default location C:\Program Files\Jenkins, a file called initialAdminPassword is found under C:\Program Files\Jenkins\secrets. If a custom path was selected, check that location instead. The same value is also written to the jenkins.err.log file in the Jenkins home directory.

Step 3) Open the highlighted file and copy the contents of the initialAdminPassword file.

Step 4) Paste the password into the Administrator password field on the Unlock Jenkins page in your browser and click the Continue button.

With the controller unlocked, the setup wizard moves on to plugins and the first user account.

Customize Jenkins

You can also customize your Jenkins environment using the steps given below:

Step 1) Click the Install suggested plugins button so that Jenkins retrieves and installs the essential plugins.

Jenkins starts to download and install all the plugins needed to create new Jenkins jobs.

Note: You can choose the option Select plugins to install and pick only the plugins you want. Plugins can be added or removed later from Manage Jenkins > Plugins, so this choice is not permanent.

Step 2) After all suggested plugins are installed, the Create First Admin User panel appears. Fill in all the fields with the desired account details and click the Save and Finish button.

Step 3) Jenkins finally asks for the URL where the instance will be reached. Leave the default value to avoid confusion later. If another application already uses port 8080, supply a different port here, then click the Save and Continue button.

Congratulations! A new Jenkins server is now installed. Click the Start using Jenkins button.

The Jenkins instance is up and running, ready for your first job. A short Jenkins tutorial for beginners explains how to create that job.

How to Verify the Jenkins Installation and Manage the Service

A dashboard that loads once is not proof of a healthy installation. Because the MSI installer registers Jenkins as a Windows service, the service must survive a reboot and restart cleanly on demand. Work through the checks below immediately after the setup wizard closes.

1. Confirm the service exists. Press Win + R, type services.msc, and press Enter. Locate the entry named Jenkins and confirm that the status reads Running and the startup type reads Automatic.
2. Check the account in use. Open the properties of the Jenkins service and review the Log On tab. A dedicated service account is preferable to LocalSystem for anything beyond local experimentation.
3. Verify the listening port. Run netstat -ano | findstr :8080 from Command Prompt. A LISTENING entry confirms that Jenkins holds the port.
4. Read the version banner. Sign in at http://localhost:8080 and read the version number in the bottom-right corner of the dashboard. Compare it with the release you downloaded.
5. Reboot once. Restart Windows and browse to the dashboard again without starting anything manually. If the page loads, the service is genuinely automatic.

The service can also be controlled from an elevated Command Prompt, which is faster than the graphical console and works well inside deployment scripts:

:: Stop, start, and query the Jenkins Windows service
net stop "Jenkins"
net start "Jenkins"
sc query "Jenkins"

:: Install Jenkins silently on a fleet of machines
msiexec.exe /i "C:\installers\jenkins.msi" /qn /norestart ^
  INSTALLDIR="D:\Jenkins" ^
  PORT=8080 ^
  /L*v "C:\logs\jenkins-install.txt"

💡 Tip: The silent installer accepts INSTALLDIR, PORT, JAVA_HOME, SERVICE_USERNAME, and SERVICE_PASSWORD as property overrides. Anything you do not pass falls back to its default value, and in silent mode the service runs as LocalSystem unless a service account is supplied.

If any of these checks fail, the causes are usually predictable, as the next section shows.

Common Jenkins Installation Errors on Windows and How to Fix Them

Most failed Windows installations trace back to a small set of causes: an unsupported Java runtime, an occupied port, or a service account that lacks the right to log on as a service. Each one produces a distinct symptom, so the fix is usually quick once the message is read carefully.

• Invalid service logon credentials: The installer rejects the account during the Test Credentials step. Open secpol.msc, expand Local Policies > User Rights Assignment, open Log on as a service, and add the account. Then retry the credential test.
• Port 8080 already in use: The Test Port button turns red because another application, often a local Tomcat or a development server, already holds the port. Choose a free port such as 8081, or stop the conflicting process identified by netstat -ano.
• Unsupported or missing Java: The installer cannot prefill the Java home directory, or the service starts and immediately stops. Install a 64-bit JDK 21 or later, then point the installer at its home directory.
• SmartScreen blocks the installer: Windows reports an unrecognized application. Select More info, then Run anyway, after confirming that the file came from the official Jenkins download page.
• initialAdminPassword file not found: A custom installation directory was chosen. Look inside the secrets folder of that directory, or read the password from jenkins.err.log in the Jenkins home directory.

Once Jenkins runs reliably, the natural next step is connecting it to a source repository and a build pipeline. The walkthroughs on Jenkins GitHub integration and the CI/CD pipeline explain how continuous integration is assembled around this installation.

FAQs