“Project is Unviewable”: Solving errors when trying to open protected VBA projects

The message “Project is Unviewable” appears in the Visual Basic for Applications (VBA) editor when Excel blocks access to a macro project’s code tree. Unlike a standard password prompt that asks for your credentials, this alert stops you from entering a password entirely. It occurs when a workbook is locked under conditions where the VBA engine cannot safely initialize the project structure.

Fast Fix:

If the workbook is currently shared or co-authored, unshare it. Go to the Review tab, select Unshare Workbook (or disable legacy workbook sharing), and save the file. If you are opening an add-in (.xlam) or a digitally signed project, close all Excel instances via Task Manager, reopen Excel, and open the source file directly using File > Open.

Why the Project Is Locked

VBA projects become unviewable when Excel enters a state where loading the module hierarchy would risk project corruption or violate a security lock.

The three primary causes are:

• Legacy Shared Workbook mode (.xls / .xlsm): When multiple users share a workbook via Excel’s legacy sharing feature, VBA locks the project permanently to prevent simultaneous code modifications.
• Add-in or Protected View session conflicts: An add-in (.xlam) or compiled binary loaded read-only in the background may refuse UI expansion in the Project Explorer.
• Corrupted VBA project stream (vbaProject.bin): If a workbook suffers an incomplete save or binary header mismatch, Excel can still run the compiled p-code while marking the source module tree unviewable.

Diagnostic Flowchart: Distinguishing the Cause

Can you click the project in VBA Project Explorer?
  │
  ├── Pop-up: "Project is Unviewable" (No password field appears)
  │     │
  │     ├── Check Excel Title Bar: Does it say "[Shared]"?
  │     │     └── YES ──► Turn off Legacy Sharing (Review > Unshare Workbook).
  │     │
  │     ├── Is the file an Add-in (.xlam / .xla) or marked Read-Only?
  │     │     └── YES ──► Check Workbook Properties & IsAddin status.
  │     │
  │     └── Is the file from an external source or email?
  │           └── YES ──► File is blocked by Windows Security (Mark of the Web).
  │
  └── Pop-up: "Password" dialog box appears
        └── Project is functioning normally; it only requires the correct password.

Primary Solutions

1. Turn Off Legacy Shared Workbook Mode

The most frequent cause of an unviewable project is the legacy “Shared Workbook” feature. When active, [Shared] appears next to the file name in the top title bar.

1. Open the workbook in Excel.
2. Go to the Review tab on the Ribbon.
3. Look for the Protect or Share group.
4. Click Unshare Workbook (or click Share Workbook (Legacy) and uncheck “Use the old shared workbooks feature”).
5. When prompted that this will make the file exclusive to you, click Yes.
6. Save and close the file, then reopen it.
7. Press Alt + F11 to open the VBA Editor. The project will now accept password entry or display its modules normally.

If your team relies on multi-user editing, note that legacy sharing is incompatible with macro maintenance. For a detailed breakdown of shared-state locking issues, see VBA Project Locked: Fixing “Project is unviewable” in Shared Workbooks.

2. Unlock Add-Ins (.xlam / .xla) via the Properties Window

When editing an Excel Add-in, the file does not display standard worksheet windows. If the add-in project was locked during distribution, clicking it in the Project Explorer may throw the “Project is Unviewable” error if the host workbook context is hidden.

1. In Excel, press Alt + F11.
2. In the Project Explorer (Ctrl + R), click the add-in project name.
3. In the Properties Window (F4), locate the IsAddin property of the ThisWorkbook object.
4. Temporarily change IsAddin from True to False.
5. Return to the Excel application window; a visible sheet will appear.
6. Save the file, return to the VBA editor, and expand the project tree.
7. After finishing your code edits, set IsAddin back to True before saving the final version.

3. Unblock “Mark of the Web” on Downloaded Files

If the workbook was downloaded from a web browser, SharePoint, or an email client, Windows may block access to the underlying macro container to protect the system.

1. Close Excel completely.
2. Open File Explorer and browse to the saved .xlsm or .xlsb file.
3. Right-click the file and select Properties.
4. At the bottom of the General tab, look for the Security section: “This file came from another computer and might be blocked to help protect this computer.”
5. Check the Unblock box and click Apply > OK.
6. Reopen the file.

If your macros are blocked from running even after unblocking the file, you may need to add the folder path to Excel’s Trust Center. See “Macros have been disabled”: Troubleshooting the “Trusted Locations” security block for proper folder setup.

4. Clearing “Ghost” Excel Processes from Memory

Sometimes Excel keeps a phantom process open after a macro crash. This orphan process holds a file lock on the VBA storage stream, causing subsequent attempts to view the project to fail.

1. Press Ctrl + Shift + Esc to open Windows Task Manager.
2. Select the Details tab.
3. Sort by Name and locate all entries named EXCEL.EXE.
4. Right-click each background instance and select End Task.
5. Launch Excel fresh and open your file.

If macro crashes frequently leave orphaned processes running in the background, review Excel Crashing on Close: How to properly clear Object variables from memory.

Recovering a Corrupted VBA Project Stream

If the steps above do not clear the error and the file was never shared, the internal binary stream (vbaProject.bin) inside the workbook archive may be damaged.

Hard Stop & Safety:

Always make a duplicate copy of the .xlsm or .xlsb file before attempting extraction or binary modifications. Do not perform recovery steps directly on your primary working copy.

To extract your code from a corrupt project structure:

1. Make a copy of the workbook and change its file extension from .xlsm to .zip.
2. Open the .zip folder and navigate to the xl subfolder.
3. Locate the vbaProject.bin file.
4. Extract vbaProject.bin to your desktop.
5. Open a fresh, clean Excel workbook, save it as a new .xlsm file, and close it.
6. Open the new .xlsm file as a .zip archive, drop the extracted vbaProject.bin into its xl folder (replacing the empty one), and rename the file back to .xlsm.
7. Launch the new file.

If the file structure itself prevents extraction, refer to How to recover a “Corrupt” Excel file using the XML extraction method for manual XML repair steps.

Summary Checklist

• Shared Workbook status removed? Ensure [Shared] does not appear in the title bar.
• IsAddin toggle tested? Switch IsAddin to False on .xlam files to expose the UI.
• File unblocked? Ensure Windows File Properties does not have an active security block.
• All Excel tasks reset? Clear lingering EXCEL.EXE tasks from Task Manager.