There's a quiet war happening inside Excel, and it's being fought over a single point. Eighteen points, to be exact. The user at the center of this story has done everything right: clean installs, updated Office versions, toggled display scaling, even switched their entire regional measurement system. And still, the row height on their home PC refuses to stay at 18 points. It becomes 0.64 centimeters, then 0.66 when they adjust scaling. The file itself is fine. The office computers render it perfectly. Excel Web is flawless. But on their machine, the layout breaks, rows jump to the next page, and page breaks scatter like startled birds.
Here's what's actually happening: Excel isn't ignoring the point value. It's converting it, and the conversion is where things go sideways. Eighteen points equals 0.635 centimeters, but the desktop app is rounding up to 0.64, and that rounding error compounds across dozens of rows. The user suspects DPI scaling, the monitor, or possibly the VPN and security software. They're probably not wrong to look at the system level. The fact that the "Disable Hardware Graphics Acceleration" toggle is missing from their build is a clue. The fact that the issue follows them across clean installs means it's not the app itself. It's the environment. Windows is telling Excel how to interpret physical units, and Excel is obeying, even when the result is a broken layout.
The practical takeaway here is uncomfortable but important: Excel's desktop app is not a pure arithmetic engine for page layout. It's a rendering environment, and rendering depends on the system it runs on. That means two users can open the same file, on the same version of Office, and see different results. The spreadsheet isn't broken. The file isn't corrupt. The machine is the variable. This is the kind of issue that makes people abandon tools out of frustration, not because the tool is bad, but because it's unpredictable. And that unpredictability is a real cost. When your home machine can't trust the page breaks that your office machine handles without thinking, you lose time, confidence, and the ability to collaborate without second-guessing.
The missing toggle for hardware acceleration is a telling detail. It suggests Microsoft has started removing or hiding compatibility options in newer builds, which means users have fewer levers to pull when things go wrong. The user has already exhausted the visible settings. They've done the upgrade, the clean install, the region changes. The next step isn't another setting. It's recognizing that this is a system-level rendering conflict, and the fix may require changing the display driver, testing a different monitor, or disabling the VPN to see if network-level interference is somehow affecting the rendering pipeline. The fact that the office PCs don't use a VPN is a strong lead. That's not a theory. It's a difference between the working and non-working environments. Start there. And if that doesn't work, consider this: the real solution might be to stop fighting the desktop app entirely and default to Excel Web for any file where precise page breaks matter. It's not a retreat. It's a smarter use of the tool. The point value should be the source of truth. When the desktop app won't respect it, the answer isn't more configuration. It's finding the environment that will.