New File Naming Schema for Microsoft Windows Software Update Packages
For additional information about the standard terminology that Microsoft is adopting to describe software updates, click the following article number to view the article in the Microsoft Knowledge Base:
Microsoft has adopted this file-naming schema for software update packages for the following reasons:
- It creates consistency across Microsoft software update packages.
- It makes it easier to search for software update packages and their associated Microsoft Knowledge Base articles.
- It clearly identifies the language of a software update package and the intended operating system, when applicable.
New Schema for Naming Windows Software Update PackagesMicrosoft uses the following schema to name Windows software update packages:
The full product name, including the product version information. For Windows software updates, this attribute is one of the following:
Indicates that an article exists in the Microsoft Knowledge Base that is associated with the software update.
The ID number of the Microsoft Knowledge Base article that is associated with the software update.
- Option (Optional attribute)
Used to differentiate software update packages that address the same issue but are designed for different processor platforms. These options include:
- x86 (for 32-bit processors)
- AMD64 (for x86-64bit AMD processors)
- IA64 (for 64-bit Intel Processors)
The standard language name abbreviation that represents the language the software update package is intended for. For example, ENU (for English), RUS (for Russian), JPN (for Japanese).
Note The abbreviation INTL is used in cases where the software update package applies to multiple languages. In cases where the software update package applies to all languages, no standard language name abbreviation is used.
For a complete list of standard language name abbreviations, visit the following Microsoft Web site:
Exceptions to New Naming SchemaMicrosoft Windows NT 4.0 software updates will continue to use the earlier naming schema. For example, Windows NT 4.0 hotfixes will continue to use a naming schema with the following format:
Article ID: 816915 - Last Review: 04/20/2012 05:51:00 - Revision: 7.0