The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
The quickest way to check the version of ntoskrnl.exe is to open PowerShell and run:
(Get-Item "$env:windirSystem32ntoskrnl.exe").VersionInfo.FileVersionThis reports the version of the ntoskrnl.exe file currently stored on disk. It is not necessarily the same thing as the broader Windows version, OS build, or kernel image recorded in an older crash dump.
Check ntoskrnl.exe with File Explorer
- Open File Explorer.
- Enter
%windir%System32ntoskrnl.exein the address bar. On many computers this resolves toC:WindowsSystem32ntoskrnl.exe, but using%windir%also works when Windows is installed on another drive. - Right-click
ntoskrnl.exeand select Properties. - Open the Details tab.
Check these fields:
- File version: the version assigned to this individual executable.
- Product version: the product version associated with the file. It often resembles the file version, but the fields have different meanings.
- Product name: usually identifies the Microsoft Windows operating system.
- File description: normally identifies the component as NT Kernel & System.
- Original filename: normally
ntoskrnl.exe.
These values come from the executable’s version-information resource, rather than from its modified date. Microsoft documents the available version fields in its version-information documentation.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsUse PowerShell for an exact, repeatable result
For troubleshooting or support documentation, PowerShell is usually more useful than the graphical method:
#1 Best Overall
- STREAMLIMED AND INTUITIVE UI | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- JOIN YOUR BUSINESS OR SCHOOL DOMAIN for easy access to network files, servers, and printers.
- OEM IS TO BE INSTALLED ON A NEW PC WITH NO PRIOR VERSION of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE PRODUCT SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
$path = Join-Path $env:windir 'System32ntoskrnl.exe'
(Get-Item -LiteralPath $path).VersionInfo |
Select-Object FileName, FileVersion, ProductVersion, ProductName, FileDescription, OriginalFilenameA typical result may look like 10.0.22621.XXXX. That is only an illustration; the value depends on the Windows release and servicing level installed on the computer.
To print only the file version:
(Get-Item -LiteralPath (Join-Path $env:windir 'System32ntoskrnl.exe')).VersionInfo.FileVersionTo print the product version instead:
(Get-Item -LiteralPath (Join-Path $env:windir 'System32ntoskrnl.exe')).VersionInfo.ProductVersionYou can also create a compact diagnostic record containing the path, version, product version, and timestamp:
$path = Join-Path $env:windir 'System32ntoskrnl.exe'
$file = Get-Item -LiteralPath $path
[pscustomobject]@{
Path = $file.FullName
FileVersion = $file.VersionInfo.FileVersion
ProductVersion = $file.VersionInfo.ProductVersion
LastWriteTime = $file.LastWriteTime
}The timestamp can provide useful context, but it is not a substitute for the version metadata.
Rank #2
- Instantly productive. Simpler, more intuitive UI and effortless navigation. New features like snap layouts help you manage multiple tasks with ease.
- Smarter collaboration. Have effective online meetings. Share content and mute/unmute right from the taskbar (1) Stay focused with intelligent noise cancelling and background blur.(2)
- Reassuringly consistent. Have confidence that your applications will work. Familiar deployment and update tools. Accelerate adoption with expanded deployment policies.
- Powerful security. Safeguard data and access anywhere with hardware-based isolation, encryption, and malware protection built in.
Compare the file with the Windows OS build
If you need to know which Windows build is installed, check that separately. Press Win + R, type winver, and press Enter. You can also use Settings > System > About. Microsoft distinguishes the Windows edition, version, and OS build in its Windows version guidance.
PowerShell can display the operating-system information alongside its architecture:
Get-CimInstance -ClassName Win32_OperatingSystem |
Select-Object Caption, Version, BuildNumber, OSArchitectureTo compare both values in one result:
$kernel = Get-Item -LiteralPath (Join-Path $env:windir 'System32ntoskrnl.exe')
$os = Get-CimInstance -ClassName Win32_OperatingSystem
[pscustomobject]@{
KernelPath = $kernel.FullName
KernelFileVersion = $kernel.VersionInfo.FileVersion
KernelProductVersion = $kernel.VersionInfo.ProductVersion
WindowsCaption = $os.Caption
WindowsVersion = $os.Version
BuildNumber = $os.BuildNumber
Architecture = $os.OSArchitecture
}The kernel file version generally reflects the build from which that file came, but servicing updates and build-branch metadata can affect the exact value. It does not, by itself, identify every installed cumulative update or prove that the whole operating system is healthy.
Rank #3
- MICROSOFT WINDOWS 11 PRO (INGLES) FPP 64-BIT ENG INTL USB FLASH DRIVE
What Command Prompt commands do—and do not—show
From Command Prompt, you can invoke PowerShell directly:
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallpowershell -NoProfile -Command "(Get-Item $env:windirSystem32ntoskrnl.exe).VersionInfo | Select-Object FileVersion,ProductVersion,FileName"The command ver reports the Windows operating-system version, not the version metadata of ntoskrnl.exe. Similarly, systeminfo reports broad operating-system and hardware details. Neither directly answers the file-version question.
Verify the digital signature
To check whether Windows recognizes the file’s Authenticode signature, run:
Rank #4
- DIGITAL OEM ACTIVATION KEY – Digital activation key compatible with Windows 11 Pro for one PC. This is an OEM-type license intended for activation on a compatible Windows PC.
- FAST DIGITAL DELIVERY – Activation key and setup information are delivered electronically through Amazon Buyer-Seller Messaging after purchase. Maximum delivery time is 4 hours.
- FOR WINDOWS 11 PRO – Designed for compatible PCs running or installing Windows 11 Pro. Internet access is required during the activation process.
- OEM LICENSE FOR 1 PC – This OEM license is intended for a single computer and becomes associated with the device on which it is activated. It is not intended for transfer between multiple PCs.
- CUSTOMER SUPPORT INCLUDED – DEOY Market provides assistance with activation and basic setup questions. Digital product only; no physical box, DVD, USB drive, or physical shipment is included.
Get-AuthenticodeSignature (Join-Path $env:windir 'System32ntoskrnl.exe') |
Format-List Status, StatusMessage, SignerCertificateAn intact Microsoft system file will normally show a valid signature and a Microsoft signer certificate. However, a valid signature does not prove that the file is the correct version for the installed build, and the displayed status can also be affected by trust or certificate-access problems.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.If the version looks wrong or the file may be damaged
Do not download a replacement ntoskrnl.exe from a third-party DLL site. It is a protected Windows component and should be repaired through Windows servicing tools or trusted installation media.
Open an elevated Command Prompt or PowerShell window and run:
Best Value
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
sfc /scannowSystem File Checker checks protected system files and attempts repairs. If it reports that some files could not be repaired, follow Microsoft’s standard servicing workflow with DISM rather than manually replacing the kernel file.
Troubleshoot access and path problems
- Access denied: open File Explorer or PowerShell with appropriate administrative privileges.
- The path does not exist: run
$env:windirand use the Windows directory it returns. - Recovery Environment: the active Windows installation may not be mounted as
C:. Identify the correct Windows volume before inspecting itsSystem32directory. - 32-bit PowerShell on 64-bit Windows: filesystem redirection can complicate access to system directories. Use 64-bit PowerShell when architecture-specific inspection matters.
- The file is locked: reading its metadata normally does not require stopping Windows. Do not try to delete or overwrite it while the operating system is running.
On-disk file versus loaded kernel in a crash dump
The PowerShell and File Explorer methods inspect the copy of ntoskrnl.exe on disk. They do not independently prove which binary image is loaded in memory or which exact kernel image was used in a crash dump.
This distinction matters when investigating an old blue-screen dump after Windows has been updated. Compare the installed file version with the kernel module and image information recorded by your debugger, along with the appropriate symbols. The current on-disk file and the dump’s kernel can legitimately be different.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Quick Recap
Which method should you use?
| Need | Best method |
|---|---|
| Quick visual check | File Explorer > Properties > Details |
| Exact result for support or scripts | PowerShell and VersionInfo |
| Windows edition and build | winver, Settings, or Get-CimInstance Win32_OperatingSystem |
| Signing status | Get-AuthenticodeSignature |
| Suspected corruption | sfc /scannow, followed by appropriate DISM repair if needed |
| Crash-dump investigation | Debugger module and image information |
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
