Windows versions and builds: what breaks and when
Why a memory reader depends on the Windows build it reads, what feature updates such as 24H2 and 25H2 change, how to check your build, and why the two machines need different update policies.
Short answer
Windows builds change kernel structure layouts, so a feature update on the game PC can break a memory reader until it is rebuilt. Check builds with winver, hold second-PC updates while a build is known good, and keep the game PC current for anti-cheat.
On this page10
- Why does the Windows build matter to a reader?
- Which machine's Windows version matters?
- How to check your exact Windows build
- Checking the build from the command line
- What does a feature update change?
- How to handle updates on each machine
- How to hold updates and still stay patched
- Problems linked to Windows builds and updates
- Common questions about Windows versions
- Sources
Why does the Windows build matter to a reader?
A memory reader does not ask Windows for data. Instead, it finds kernel structures in physical memory, such as the page tables, the process list and the module list, and walks them by offset. Those structures are internal to the kernel, and Microsoft is free to change their layout in any release. When the layout moves, the offsets the reader was built against point at the wrong thing. The software then fails at the earliest step, because without the page table base it cannot resolve anything else. This is why the Windows version you run has real consequences and is not a matter of preference.
Which machine's Windows version matters?
The kernel structures being resolved live on the machine whose memory is being read, while the software doing the reading runs on the second PC. That software mostly just needs a supported Windows with the right runtimes installed. So a feature update on the game PC changes the shape of what the reader is looking at. A feature update on the second PC is lower-stakes but still a real risk to drivers and runtimes, which is why each machine needs its own update decision.
How to check your exact Windows build
Version, feature update and build are three different numbers, and support tickets go badly when people report only Windows 11, so report all three.
- Press Windows and R, type winver, and press Enter
- Read the edition, the feature update label such as 24H2, and the OS Build line including the number after the dot
- For text you can copy, open Settings, System, About and read Windows specifications
- Note the build and the update revision together, because the revision (the part after the dot) identifies a specific cumulative update
- Record this in the same place you keep your firmware notes, and update it whenever Windows updates
- When opening a ticket, include the full build string for both machines, not just the one you think is broken
Checking the build from the command line
The registry values are the authoritative ones, because Windows Update itself reports from them. DisplayVersion is the feature-update label and CurrentBuild is the build, while UBR is the update revision, the number after the dot in winver.
winver
systeminfo | findstr /B /C:"OS Name" /C:"OS Version"
reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v DisplayVersion
reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild
reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v UBRWhat does a feature update change?
A monthly cumulative update usually patches Windows without moving the structures a reader depends on. Feature updates are different: they are labelled with a year and a half-year, such as 24H2 and 25H2, and each one ships a new kernel. That is where layout changes concentrate, and it explains a familiar pattern. Things work for months, a feature update installs overnight, and the next morning the software cannot find the page table base. Nothing was detected and nothing is broken on the card. The software needs an update built against the new kernel, and the memory map may need regenerating too.
How to handle updates on each machine
Each column is a different risk profile, so applying one update policy to both machines is a mistake.
| Question | Game PC | Second PC |
|---|---|---|
| Keep it up to date? | Yes. Anti-cheats and the game itself expect a current, supported Windows, and an out-of-date game PC causes its own launch failures | Not automatically. Once a build is known good for your software, there is a real argument for holding it there |
| Why | Update compliance is a requirement of the software you are trying to play, and an unsupported build is a security problem on a machine you use normally | It runs one tool. The only thing an update buys you here is risk to the driver and the runtime stack |
| What a feature update risks | Kernel structure layout changes, which is what breaks the reader and is a wait-for-an-update situation | USB controller driver rollbacks, FTDI driver changes, and runtime version changes |
| How to hold updates | Do not hold them beyond a short pause. Use the built-in pause if you need to wait a week for compatibility news | Pause updates, and defer the feature update specifically, using the built-in Windows settings |
| After an update breaks something | Check the status board for your title before changing anything on the machine | Re-check the FTDI driver, the port's negotiated speed and the runtimes before assuming the card degraded |
Neither column means turning updates off permanently, because a Windows build that stops receiving security updates is a liability, even on a tool machine.
Tip
How to hold updates and still stay patched
On a second PC, the sensible approach is to defer updates rather than abandon them. Use the pause and the feature-update deferral that Windows already provides, and let cumulative security updates in. Hold the feature update until your software provider says the new kernel is supported. That keeps the machine patched against the things that matter while avoiding the one class of update that breaks the reader. Turning off Windows Update entirely leaves you on a build that stops receiving fixes, which is a worse trade than a weekend of waiting.
Problems linked to Windows builds and updates
If one of these problems appeared the morning after an update, check these causes before you look at the hardware.
| Symptom | Likely cause | Fix |
|---|---|---|
| Unable to locate valid DTB, immediately after a Windows feature update | Kernel structure layout changed on the machine being read; the software's offsets no longer match | Check the status board and wait for a software build that supports the new kernel, then regenerate the memory map once that build is available |
| Failed to find base address after an update, with no DTB error | A game update rather than a Windows one, or a memory map that predates a system change | Confirm the game build is supported, then regenerate the memory map, but do not change firmware settings for this |
| Read rate dropped sharply after a second-PC update | Windows replaced or rolled back the USB controller or bridge driver | Re-check the FTDI driver version and the port's negotiated speed, then reinstall the driver version shipped with your order |
| Loader will not start after an update, no hardware error | A runtime was replaced or removed — the Visual C++ redistributables or the web view runtime | Reinstall the runtimes listed with your download, reboot, then try again before touching anything else |
| Everything works on one machine and not on a supposedly identical one | The two machines are on different builds or different update revisions | Compare the full build plus UBR strings from both machines, because they are rarely as identical as people assume |
Common questions about Windows versions
Which Windows version should I install on the second PC?
Install a 64-bit Windows build that still receives security updates and that your software's current requirements list as supported. Check the software's own documentation before you install, instead of installing the newest release and hoping it works.
Will a 24H2 or 25H2 class update definitely break my setup?
Not definitely, but feature updates are where kernel layout changes concentrate, so they are the type of update most likely to break it. Check your provider's status before installing one on the machine being read.
Should I turn Windows Update off completely?
No. Defer feature updates but let security updates in, because a build that has stopped receiving fixes is a real risk. Nothing in this setup is worth running an unpatched machine for.
Can I roll back after an update broke things?
Windows offers a limited rollback window after a feature update, and it sometimes works, but treat it as a short-term recovery rather than a plan. Read your provider's status notes before you decide.
Does the second PC need the same Windows version as the game PC?
No, the two are independent. The game PC's build is what the reader has to understand, while the second PC's build only has to run the software and its runtimes.
Sources
Apart from the linked source, this is bench work: the team watched feature updates break readers and wrote down which builds worked. Microsoft does not publish the kernel layout a reader depends on.
- 01Windows Update and FTDI drivers (Hackaday, 2014)
the case where an FTDI driver shipped by Windows Update broke working devices
hackaday.com
Read next
- BIOS settings for DMA on the game PC
- Secure Boot: what it does and what turning it off costs
- How to generate a memory map (MMAP)
- Clean Windows before a spoofer
- DMA troubleshooting: fixes for common issues
- How a wrong system clock breaks TLS and licence checks
- Setting up Windows on the second PC for reliable reads
Still stuck? Open a ticket on Discord
All guides