volatility
volatility copied to clipboard
Why not use NtBuildNumber?
NtBuildNumber located in KUSER_SHARED_DATA for Windows 10, contains the build number.
I don't see volatility using this anywhere. Instead it scans the memory to find KDBG for it, which seems a lot slower and more error prone.
KUSER_SHARED_DATA is trivial to find, it's at a static offset.
Anything I'm missing?