Package Details: ttf-ms-win11 10.0.26100.2314-1

Git Clone URL: https://aur.archlinux.org/ttf-ms-win11.git (read-only, click to copy)
Package Base: ttf-ms-win11
Description: Microsoft Windows 11 TrueType fonts
Upstream URL: http://www.microsoft.com/typography/fonts/product.aspx?PID=164
Licenses: custom
Conflicts: ttf-ms-fonts, ttf-tahoma, ttf-vista-fonts
Provides: emoji-font, ttf-font, ttf-ms-fonts, ttf-tahoma
Submitter: Vaporeon
Maintainer: Vaporeon (Scimmia)
Last Packager: Scimmia
Votes: 26
Popularity: 0.177302
First Submitted: 2021-10-11 13:33 (UTC)
Last Updated: 2024-11-13 00:49 (UTC)

Dependencies (0)

Required by (307)

Sources (142)

Latest Comments

1 2 3 4 5 6 Next › Last »

Vaporeon commented on 2024-11-20 06:47 (UTC)

This package is intended to track the current font versions installed in a live system. If you want to use fonts from the initial release ISO, you can either check out a commit of this package that tracks those fonts (in this case ef4bb39bb7af), or use another AUR package that explicitly follows ISO releases only.

Hackerpcs commented on 2024-11-15 09:41 (UTC) (edited on 2024-11-15 09:50 (UTC) by Hackerpcs)

Latest official ISO that MS provides from here https://www.microsoft.com/en-us/software-download/windows11 is "Win11_24H2_English_x64.iso", also known as "en-us_windows_11_consumer_editions_version_24h2_x64_dvd_1d5fcad3.iso" in MSDN/Visual Studio Subscription and has ISO SHA512 "4292beb7cd8e3aa75a3e07e3426d49def735cca6b8914456530f9541bf02bd913710117d5bd2492d2002774a13916b951b8ab7012bee5322decacf3c3224a0a7". This ISO is build 1742:


$ 7z e Win11_24H2_English_x64.iso -o. sources/install.wim
$ wimlib-imagex info install.wim 6

Information for Image 6
Index:                  6
Name:                   Windows 11 Pro
Creation Time:          Fri Sep 06 04:21:43 2024 UTC
Last Modification Time: Fri Sep 06 05:09:29 2024 UTC
Architecture:           x86_64
Languages:              en-US
Major Version:          10
Minor Version:          0
Build:                  26100
Service Pack Build:     1742
Service Pack Level:     0

and on this ISO, the sha256 of "SegoeIcons.ttf" is "eca6e631fc5d3bb7369b1e73af062a9b91831d1e1098f230020ab7fee962eb14". I don't get where the sha256 "4832a93d1065a6f0795a7b7f20b2b1f780e6d88efff824d3627dfba1ae3bff2b" for SegoeIcons.ttf comes from which fails verification and in my opinion the only source where the files should be checked against is the official ISO that anyone can freely and legitimately download from Microsoft, not use installed files because they may change at will with updates.

Scimmia commented on 2024-10-08 01:05 (UTC)

Preview updates show up as optional in Windows Update.

https://support.microsoft.com/en-us/topic/windows-11-version-24h2-update-history-0929c747-1815-4543-8461-0160d16f15e5

Sven commented on 2024-10-07 20:05 (UTC)

I am indeed on 10.0.26100.1882. But I installed no preview. I upgraded using a vanilla Win11_24H2_German_x64.iso (sha e6a98903f14931b0f621239157ebbcc00fe1ae19) and installed all available Windows updates.

How would I be able to tell if I was on a preview release? winver.exe doesn't show.

Scimmia commented on 2024-10-06 12:11 (UTC)

Not on my 10.0.26100.1742 system. Maybe you're on 10.0.26100.1882, the current preview version?

Sven commented on 2024-10-06 12:06 (UTC)

Current version fail with checksum error on SegoeIcons.ttf. My SegoeIcons.ttf from a fully updates Windows 11 24H2 install has a sha256 checksum of 45cddf62e8993f4f712fdebfba634a772ff3dc862d2a61d59cb39ec32643c705

mber commented on 2024-06-20 13:02 (UTC)

The SegoeIcons.ttf checksum appears to be out of date again. I got my ISO directly from the link in the PKGBUILD.

Exactly what version of windows you get from the ISO appears to be opaque and they don't let you choose the version, so I don't have much choice here but to skip the checksum.

Scimmia commented on 2024-04-07 12:03 (UTC)

No, use the correct version of the PKGBUILD

ldkxingzhe commented on 2024-04-07 10:53 (UTC)

@whiteman808 can use makepkg --skipchecksums skip the ttf file checksums

Scimmia commented on 2024-02-16 18:10 (UTC)

Because you have the wrong version. Pay attention to the pkgver.

1 2 3 4 5 6 Next › Last »