Subject: Excel Page Layout Row Height Mismatch - 18pt (Web/Office) vs 0.64cm (Home PC) causing pagination issues
I’m facing a persistent rendering issue with Excel files hosted on SharePoint. The file looks perfect on Excel Web and on all computers at my office/business location (which do not use a VPN). However, on my home desktop PC, the layout "breaks" and rows jump to the next page.
The Core Issue:
In Excel Web and on the office PCs, the row height is exactly 18 points.
On my home PC, Excel forces the row height to 0.64cm (or 0.66cm when changing scaling). This slight rounding difference (18pt should be 0.635cm) accumulates over many rows, causing the layout to shift and ruin the page breaks in Page Layout View.
System Specs (Home PC):
OS: Windows 11 Pro.
Office: Microsoft 365 (Version 2305 / Build 16501).
Security/Network: Bitdefender and Surfshark VPN installed (VPN is NOT present on the working office PCs).
What I’ve already tried (None worked):
Office Version: Upgraded from Office 2021 to Microsoft 365 (Clean install).
Display Scaling: Tried 100%, 125%, and 150%. At 100%, the row height increased to 0.66cm.
Excel Settings: Enabled "Optimize for compatibility". Note: The "Disable Hardware Graphics Acceleration" toggle is missing in this version, so it was not changed.
Windows Settings: Changed Measurement System from Metric to U.S. in Region settings. Turned off ClearType.
Printer: Set "Microsoft Print to PDF" as default.
Compatibility: Tried High DPI override settings (System/System Enhanced) via EXCEL.EXE properties.
Units: In "Normal View", the height correctly shows as 18, but switching to "Page Layout" forces it back to cm/inches with rounding errors (0.64cm).
Observation:
The issue is specific to the desktop app on my home PC. Excel Web is unaffected. I suspect a conflict between Windows 11 DPI scaling, the monitor, or potentially the VPN/Region settings.
Does anyone know how to force Excel Desktop to respect the exact Point (pt) value in Page Layout view without rounding it based on local monitor DPI?
[link] [comments]
Want to read more?
Check out the full article on the original site