Windows Server 2008 Build 6003 Patched · Genuine

Following the end of extended support (Jan 2020), Microsoft released an emergency out-of-band security update in April 2020 to patch a remote code execution vulnerability in SMBv3 (CVE-2020-0796, aka "SMBGhost") for certain still-supported products like Windows 10. As part of the servicing stack update for Windows Server 2008, Microsoft also backported a fix that incremented the CurrentBuild registry key from 6002 to 6003.

The change occurs in:

The kernel file (ntoskrnl.exe) version remained 6.0.6002.xxxxx. Thus, 6003 is not a true kernel build but a versioning inconsistency.

False. This is still the Windows 6.0 kernel. DirectX 12, WDDM 2.0, UWP apps, and modern power management are not present. What you get is better time zone data, stronger cryptography, and continued update support. windows server 2008 build 6003 patched

Command line (registry read):

reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild

Or PowerShell:

Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion" | Select CurrentBuild

Systeminfo command will incorrectly show 6002 if the patch manifest is not updated; rely on registry instead. Following the end of extended support (Jan 2020),

If you are still managing a Windows Server 2008 build 6003 patched system, you have three paths forward:

Windows Server 2008 (build 6003) corresponds to Windows Server 2008 with Service Pack 2 (SP2) — the SP2 build number is commonly associated with 6002/6003 depending on revision. A patched build 6003 indicates a system running the Server 2008 SP2 baseline that has received subsequent security updates and hotfixes. Below is a concise, technical overview covering context, likely security posture, attack surface implications, and recommended next steps.

After a reboot, run winver. You will see Version 6.0 (Build 6003). The kernel file ( ntoskrnl

Warning: Attempting to install ESU updates without a valid license will result in activation errors. Third-party "patching tools" that bypass ESU checks exist but violate Microsoft licensing and may introduce instability.

Open PowerShell or CMD as Administrator and run:

reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild

Or in PowerShell:

(Get-ItemProperty "HKLM:SOFTWARE\Microsoft\Windows NT\CurrentVersion").CurrentBuild

If it returns 6003, you are patched to the final kernel.