Arch Linux User Repository

For reference, Windows 11 25H2 is the same core base as 24H2 with an "enablement package" applied. What this means is that the fonts from 26100.XXXX and 26200.XXXX should be the same, provided the XXXX part is equal (or later). This should be true for at least the life of 25H2, provided your 24H2 SKU is still getting updates. So keep this in mind if staying on the 24H2 branch for any reason.

THE INTENTION OF THIS PACKAGE IS TO EASILY INTEGRATE THE LATEST FONTS FROM A FULLY UPDATED WINDOWS 11 INSTALL INTO AN ARCH LINUX SYSTEM.

PLEASE DO NOT COMPLAIN IF THE FONTS MISMATCH OLDER VERSIONS FROM SOME RANDOM ISO.

PLEASE DO NOT FILE A REQUEST TO MERGE THIS PACKAGE WITH ONE THAT PULLS OLDER VERSIONS FROM SOME RANDOM ISO.

THANK YOU.

Updated Windows 11 to 10.0.26200.8524, four fonts updated:

b3658eadae55e682b5f69eb64c439c1ecc8f196c0bb8d4756d145d13bc86476a  arial.ttf
e8f4e3baf6cc35fed6fcce3a540e8b39e8f6cda1d22a28f2ec8f526fef7a43f5  arialbd.ttf
86b32db9a06f9694e2a3760c42e5117bcdc5cc1255bb5186ca8ce0305e22f288  ariali.ttf
267a411525980d648f10a7222a6ff1ebe4d4feeefbf9b3100cae2b5cfab5594a  arialbi.ttf

OK I am simply curious, why would updates to fonts be part of a Microsoft security update? Can fonts be used for malicious purposes? Or is this simply too sophisticated a question to ask of MS?

Confirmed a handful of fonts fail the checksum from the latest ISO, but succeed after replacing those files from a fully up-to-date installation of Windows 11.

The PKGBUILD readme should probably mention that the checksums intend to track an actual installation and not the ISO that's linked in that file. (This isn't "some random ISO," this is the file that is linked in the build instructions.) The (mostly complete) instructions for extracting from the ISO aren't entirely pointless, since people who don't care about their fonts being up-to-date can just ignore the checksums, but it's a little misleading as-is, imo.

Some fonts (e.g. Times New Roman) do not pass the checksum verification for the latest version of the system image downloaded from the link in PKGBUILD.

So the error tells you to read the PKGBUILD, and instead of reading the PKGBUILD, you post here? Really?

Unable to install this package:

[cryptodan@alphacentauri ttf-ms-win11]$ makepkg -si ==> Making package: ttf-ms-win11 10.0.26200.7171-1 (Thu Dec 4 20:15:13 2025) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Downloading arial.ttf... Unable to find file://arial.ttf, please read the PKGBUILD -> Downloading arialbd.ttf... Unable to find file://arialbd.ttf, please read the PKGBUILD -> Downloading ariali.ttf... Unable to find file://ariali.ttf, please read the PKGBUILD -> Downloading arialbi.ttf... Unable to find file://arialbi.ttf, please read the PKGBUILD -> Downloading ariblk.ttf... Unable to find file://ariblk.ttf, please read the PKGBUILD -> Downloading bahnschrift.ttf... Unable to find file://bahnschrift.ttf, please read the PKGBUILD

And many other errors like the above.

For reference, Windows 11 25H2 is the same core base as 24H2 with an "enablement package" applied. What this means is that the fonts from 26100.XXXX and 26200.XXXX should be the same, provided the XXXX part is equal (or later). This should be true for at least the life of 25H2, provided your 24H2 SKU is still getting updates. So keep this in mind if staying on the 24H2 branch for any reason.

I can reproduce Ketchup901's issue here. winver shows "Version 24H2 (Build 26100.6725)". 6725 is currently a preview, so I think it's perfectly fine that the checksums of this package do not match the fonts of this version.

For everyone affected, I suggest to modify the PKGBUILD manually, adjust the version to 26200.6725 and to build the package via makepkg --skipchecksums.

I just pushed a commit for 26200.6584. There are no font differences from 26100.6584, but this creates a reference for people using the ISO.

"my updated Windows 11 installation" What version, exactly?