FILETYPEATTRIBUTEFLAGS
[This documentation is preliminary and is subject to change.]
Applies to: desktop apps only
Indicates FILETYPEATTRIBUTEFLAGS constants that are used in the EditFlags value of a file association PROGID registry key.
| Constant/value | Description |
|---|---|
|
Excludes the file type. |
|
Shows file types, such as folders, that are not associated with a file name extension. |
|
Indicates that the file type has a file name extension. |
|
Prohibits editing of the registry entries associated with this file type, the addition of new entries, and the deletion or modification of existing entries. |
|
Prohibits deletion of the registry entries associated with this file type. |
|
Prohibits the addition of new verbs to the file type. |
|
Prohibits the modification or deletion of canonical verbs such as open and print. |
|
Prohibits the deletion of canonical verbs such as open and print. |
|
Prohibits the modification or deletion of the description of the file type. |
|
Prohibits the modification or deletion of the icon assigned to the file type. |
|
Prohibits the modification of the default verb. |
|
Prohibits the modification of the commands associated with verbs. |
|
Prohibits the modification or deletion of verbs. |
|
Prohibits the modification or deletion of the entries related to DDE. |
|
Prohibits the modification or deletion of the content type and default extension entries. |
|
Indicates that the file type's open verb can be safely invoked for downloaded files. This flag only applies to safe file types as identified by AssocIsDangerous. |
|
Prevents the Never ask me check box from being enabled. The user can override this attribute through the File Type dialog box. Use of this flag means FTA_OpenIsSafe is not respected. |
|
Causes the file type's file name extension to be always shown, even if the user has selected the Hide extensions for known file types option. |
|
Prohibits the addition of members of this file type to the Recent Documents folder. Additionally, in Windows 7 and later, prohibits the addition of members of this file type to the automatic Recent or Frequent category of an application's Jump List. This flag does not restrict members of this file type from being added to a custom Jump List. It also places no restriction on the file type being added to the automatic Jump Lists of other applications in the case that other applications use this file type. |
|
Introduced in Windows 8. Marks the file as safe to be passed from a low trust application to a full trust application. Files that originate from the Internet or an app container are examples where the file is considered untrusted. Untrusted files that contain code are especially dangerous, and appropriate security mitigations must be applied if the file is to be opened by a full trust application. File type owners for file formats that have the ability to execute code should specify this flag only if their program mitigates elevation-of-privilege threats that are associated with running code at a higher integrity level. Mitigations include prompting the user before code is executed or executing the code with reduced privileges. By specifying this flag for an entire file type, an app running within an app container can pass files of this type to a program running at full trust. Some file types are recognized as inherently dangerous due to their ability to execute code and will be blocked if you don't specify this value. |
|
Introduced in Windows 8. Ensures that the verbs for the file type are invoked with a URI instead of a downloaded version of the file. Use this flag only if you've registered the file type's verb to support DirectInvoke through the SupportedProtocols or UseUrl registration. |
Remarks
These flags represent possible attributes stored in the EditFlags value of a ProgID registration. The EditFlags data is a single REG_DWORD.
The following example shows the FTA_NoRemove (0x00000010) and FTA_NoNewVerb (0x00000020) attributes assigned to the .myp file type.
HKEY_CLASSES_ROOT .myp (Default) = MyProgram.1 MyProgram.1 (Default) = MyProgram Application EditFlags = 0x00000030
APIs such as IQueryAssociations::GetData can retrieve that EditFlags data. Compare the numerical equivalents of these FILETYPEATTRIBUTEFLAGS flags against that retrived value to determine which flags are set.
The following example demonstrates the use of IQueryAssociations::GetData to determine if those values are set.
IQueryAssociations *passoc;
HRESULT hr = AssocCreate(CLSID_QueryAssociations, IID_PPV_ARGS(&passoc));
if (SUCCEEDED(hr))
{
hr = passoc->Init(NULL, pszType, NULL, NULL);
if (SUCCEEDED(hr))
{
DWORD dwEditFlags;
ULONG cb = sizeof(dwEditFlags);
hr = passoc->GetData(NULL, ASSOCDATA_EDITFLAGS, NULL, &dwEditFlags, &cb);
if (SUCCEEDED(hr))
{
if (dwEditFlags & 0x00000010) // FTA_NoRemove
{
// ...
}
if (dwEditFlags & 0x00000020) // FTA_NoNewVerb
{
// ...
}
}
}
passoc->Release();
}
To set an EditFlags attribute, you can use the RegSetValueEx or SHSetValue functions. First use IQueryAssociations::GetData to retrieve the current set of attributes as shown in the example above, add the desired FILETYPEATTRIBUTEFLAGS to that value, then write that value back to the registry using one of the two set functions.
Requirements
|
Minimum supported client | Windows XP, Windows 2000 Professional, Windows Vista |
|---|---|
|
Minimum supported server | Windows Server 2008 |
Build date: 3/7/2012
Marks the file as dangerous (unsafe) and will result in
AssocIsDangerous
() returning TRUE for the file type. The ShellExecute() API
provides security mitigations for dangerous files that originate from the
untrusted sources (using zone identifiers stored on the file using the MOTW).
This includes producing warning prompts and in Win8 using a reputation checking
service to identify known good or known bad files.
File type owners for file formats that have the ability to execute
code should either identify these file types as dangerous by setting this flag
or mitigate threats, ensuring that the handlers for the file type implements
mitigations, for example producing warning prompts before running the code.
- 7/19/2011
- Chris_Guzak
- 4/17/2012
- Chris_Guzak
