Windows 11 26H1 step by step: install and confirm it worked

To install Windows 11 26H1, first check whether your PC is eligible, back up your important files, and use the official update path Microsoft offers on that device. If the update appears in Windows Update, that is usually the simplest route; if it does not, use only the approved Microsoft installation method for the exact build you need. After the install finishes, confirm success by checking the version and build number in Windows.

What you need before you start

Before you try to install Windows 11 26H1, make sure you have the basics in place:

• A current backup of your important files. Use a backup you can restore from, not just files sitting on the same drive.
• Stable power. If you’re on a laptop, plug it in. If you’re on a desktop, avoid starting the update when a power loss is likely.
• Enough free storage space for the update to unpack and finish.
• A device that is eligible for the 26H1 path you plan to use. Eligibility can depend on the exact build, release channel, hardware, and rollout rules Microsoft is using at the time.
• The current official installation path for your device. Start with Windows Update, then use only Microsoft’s approved installer or media if Windows Update does not offer the update.

If you’re not sure whether your PC qualifies, check Microsoft’s current support information for Windows 11 26H1 before you start. Don’t assume the path is the same as a previous release, because rollout rules can change.

Install Windows 11 26H1 step by step

1. Open Settings and go to Windows Update.

Settings > Windows Update

Look for a feature update or update offer for Windows 11 26H1. If it appears, that is usually the approved path for your device.

2. Click Check for updates and wait for Windows to finish scanning.

If 26H1 is available, Windows should start offering it or show it in the list of available updates. If nothing appears right away, wait for the scan to finish before you assume the update is missing.

3. Start the 26H1 download if Windows Update offers it.

Let the download finish without switching pages or closing Settings. Interrupting the process can delay the install or force it to restart later.

4. Follow the on-screen prompts in the order Windows gives them.

You may see prompts about license terms, restart timing, or finishing setup. Accept them in sequence and don’t skip ahead. If Windows asks for a restart, do it when prompted instead of postponing it repeatedly.

Do not force a shutdown during the install or skip a restart that Windows says is required. That can trigger a rollback or leave the update incomplete.

5. Let the PC restart and finish the update.

After the first restart, Windows may continue configuring the update before you get back to the desktop. If you see a message about working on updates, leave the computer alone until it finishes.

6. If Windows Update does not offer 26H1, use the official installation method Microsoft provides for that release.

That could be an approved installer, update assistant, or installation media, depending on how Microsoft is distributing 26H1 at the time you read this. Use only the method described in the current Microsoft documentation for the exact build you need.

7. Run the installer and choose the default upgrade option unless Microsoft’s instructions say otherwise.

Read each prompt carefully. If the installer asks whether to keep personal files and apps, choose the option that matches your goal. For an in-place update, keeping files and apps is usually the normal path.

8. Finish the install and restart when asked.

The last restart matters. Once Windows asks for it, let it happen and wait for the system to return to the desktop before you check anything else.

How to tell it worked

The quickest way to confirm success is to check the version and build number after the final restart.

Open Settings and go to System > About, then look under Windows specifications. You should see the edition, version, and OS build listed there.

Settings > System > About

A successful update usually looks like this:

• The version field matches the 26H1 release information you were aiming for, if Microsoft labels it that way on your device.
• The build number matches the 26H1 build you meant to install.
• Windows signs you in normally and your apps and files are still there, if you chose an in-place upgrade that keeps them.

For a second check, press Win + R, type winver, and press Enter. The About Windows box should show the current version and build information. Use that to compare what Windows thinks is installed with the release you expected.

If both places match the 26H1 release information you expected, the update worked.

If 26H1 does not show up or fails

If Windows 11 26H1 does not appear in Windows Update, start with the most common blockers first:

• Check eligibility again. The device may not be in the rollout yet, may not meet the hardware requirements, or may be on a channel that does not get that build.
• Make sure you have enough free space.
• Confirm your internet connection is stable.
• Restart the PC and check Windows Update again.
• Install any smaller pending updates first, then return to the feature update.

If the install starts and then rolls back, Windows usually hit a compatibility problem, storage problem, or install error during the upgrade. If that happens:

• Let the PC finish the rollback.
• Check that your files are still present.
• Review Windows Update history for the failure state.
• Try again only after you have more free space, a stable connection, and the latest prerequisite updates installed.

If the same failure repeats, stop and use Microsoft’s current support material for the exact 26H1 build. Build-specific issues are usually handled through release notes, known-issues pages, or support articles that change as Microsoft updates the rollout.

If you used a Microsoft-approved installer and it still failed, the installer may not be the right method for your device or channel. Check the official 26H1 guidance for the current installation path rather than forcing a workaround from an older Windows release.