🚀 Overview: Legacy File Blocking in Microsoft Visio 2013

In Microsoft Visio 2013 (both Professional and Standard editions), a security feature exists that prevents users from opening or saving specific legacy binary file formats. This behavior is governed by the File Block Settings, a feature introduced to mitigate risks associated with older file structures that may be more vulnerable to security exploits.

When these policies are active—either by default or through administrative enforcement—users will encounter specific error messages stating that the file is blocked by a registry policy or Trust Center configuration. This guide outlines the technical causes, the specific formats affected, and the methodologies for IT Administrators to remediate these restrictions via the UI, Trusted Locations, or Group Policy Objects (GPOs).

⚙️ Key Technical Details

The issue specifically targets legacy binary formats. If a user attempts to interact with these formats, the application cross-references the action against the File Block Settings in the registry.

Blocked File Formats

• Visio 2003-2010 Binary Drawings, Templates and Stencils
• Visio 2000-2002 Binary Drawings, Templates and Stencils
• Visio 5.0 or earlier Binary Drawing, Templates and Stencils

Specific Error Strings

Users will typically trigger one of the following diagnostic messages:

• “You are attempting to open a file type that is blocked by your registry policy setting.”
• “You are attempting to open a file that was created in an earlier version of Microsoft Office. This file type is blocked from opening in this version by your registry policy setting.”
• “You are attempting to open a file type <File_Type> that has been blocked by your File Block settings in the Trust Center.”

Root Cause

Visio 2013 utilizes a new File Block Settings dialog box. By default, certain older formats are restricted to ensure environment security. If these settings are “grayed out” or unavailable for the user to change, it indicates that a Group Policy has been applied at the domain level, overriding local preferences.

🛡️ Impact and Resolution Methodologies

This policy impacts workflow productivity when dealing with archival data. Administrators can resolve this through three primary methods, depending on the scope of the required change.

⚠️ Mandatory Registry Warning

Warning: Incorrectly modifying the registry can result in system instability. It is highly recommended to back up the registry before proceeding with manual edits.

Method 1: Manual Adjustment via Trust Center

For individual workstations where the user has local administrative rights (and no overriding GPO), follow these steps:

1. Navigate to the File tab in Visio 2013 and select Options.
2. Select Trust Center > Trust Center Settings > File Block Settings.
3. Locate the specific file type (e.g., Visio 2003-2010 Binary Drawings, Templates and Stencils) and clear the checkboxes for Open or Save as required.
4. Click OK twice to commit the changes.

Note for Embedded Objects: If Visio drawings are embedded within other Office documents (like Word or Excel), you must clear both the Open and Save checkboxes for the 2003-2010 format to ensure interoperability.

Method 2: Implementing Trusted Locations

Files residing in a designated Trusted Location bypass File Block registry checks. If a file is known to be safe, moving it to a directory defined under Trust Center Settings > Trusted Locations will allow the file to open regardless of the general blocking policy.

Method 3: Enterprise Deployment via Group Policy (GPO)

For domain-wide management, administrators should use the Office 2013 Administrative Template files (ADM, ADMX/ADML).

• Download the templates to the Central Store.
• Use the Office Customization Tool or the Group Policy Management Editor to navigate to the Visio 2013 settings.
• Configure the File Block Settings to permit or restrict specific formats (Visio 5.0, 2000-2002, or 2003-2010) across the entire organizational unit (OU).

📅 Additional Information

Administrators can further restrict file types to harden the environment by using the 2013 Office System Administrative Templates to force specific registry configurations on client machines. For a deeper dive into the governance of these settings, consult the Overview of Group Policy for Office 2013.

---

Official Source: Read the full article on Microsoft.com