In certain language versions of Windows 7, %windir%\Globalization\MCT contains one or more "MCT-XX" folders, with XX being a country code. They contain a theme and 6 wallpapers of scenery in that country. They're not installed by language packs, so the only way to get them is from installation media of the corresponding languages. (Windows Wallpaper Wiki page)
Windows XP Starter also has exclusive wallpapers. (Lost Media Wiki forum thread, My Digital Life forum thread, Windows Wallpaper Wiki page)
Windows NT 4 has a "Pan-Chinese Edition" with language code CHP. It's made for Hong Kong which needs to process both simplified and traditional Chinese characters. It's based on the Simplified Chinese edition, with the UI de-translated back to English. It's the only version of Windows as of 2024 to have a Jyutping IME builtin. (Microsoft did later provide a Jyutping IME in the zh-TW Office 2010 IME package.) The Jyutping IME is the only IME available during setup. It also contains "traditional Chinese Cangjie" (繁体仓颉) IME; both are by 北京中易电子公司, the same company as other Simplified Chinese input methods, and are made using the same framework as them as well. All input methods are under the zh-CN locale; there is none under zh-HK or zh-TW. (Chinese article, Official website)
Microsoft's own KB article suggests that NT 3.51 also has a Pan-Chinese edition, but I can't find any evidence of it actually existing.
Windows 95 RTM zh-CN contained Cangjie and Bopomofo IMEs, but they were removed in OSR1 and subsequent versions, because the tables of these IMEs contained taboo words. (Zhihu answer, BetaArchive forum post)
To enable Aero in Windows Vista guests in VMWare Workstation, the hardware compatibility level must be set to 8.x or greater.
List of Microsoft Knowledge Base article archives:
By default, Windows uses the RTC (realtime clock, hardware clock) as local time. Unix-likes, including Hackintosh and Linux, use the RTC as UTC. This causes a conflict. The recommended solution is to set Windows to use the RTC as UTC, by setting the RealTimeIsUniversal registry value at HKLM\SYSTEM\CurrentControlSet\Control\TimeZoneInformation. However, that comes with its own disadvantages, especially for older Windows before Windows 10 (exact cutoff unknown).
At least in Windows 7 (according to my own experience), the NTP sync functionality would write local time to RTC even when RealTimeIsUniversal is 1. When this happens, at next boot the time in Windows will be UTC with offset applied twice (with RTC being in local time). If this happens, the NTP sync functionality must be disabled, either by disabling the W32Time aka "Windows Time" service, or by running the w32tm /unregister command to remove the service entirely. After that, either use a third-party NTP client, or only rely on a Unix-like OS to sync time. According to ArchWiki: "The Windows clock synchronization routine is quite inaccurate to start with, requiring even extra work to reach one-second accuracy, so disabling it should not be much of a loss."