How to fix Runtime error 76 "Path not found" in Windows?

Run-time error '76' with the text Path not found comes from Visual Basic: a macro in Excel, Word or Access, or an older program, asked Windows for a folder or drive that does not exist. The file name is not the problem; a folder in front of it is. Press Debug, read the full path, and check whether that folder opens in File Explorer.

Facts checked on 15 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What run-time error 76 "Path not found" means

The message box is titled Microsoft Visual Basic and says Run-time error '76': with Path not found on the next line. Microsoft's VBA reference explains it in one sentence: during a file-access or disk-access operation, for example Open, MkDir, ChDir or RmDir, the operating system was unable to find the specified path.

A path is the drive plus every folder that leads to a file. Error 76 means one of those parts is missing, so Windows never even looks for the file. That is why reinstalling Windows components, as many pages suggest, does not touch it: the fix is always in the path.

• 76 path not found and runtime error 76 are the same error. People also type it as run time error 76, run-time error 76 and Microsoft Visual Basic run time error 76.
• The code is the same in Excel, Word, Access, Outlook and old programs built with Visual Basic 6, because they share the same language.
• A message that says only Path not found, without the number 76, can come from other programs too. This page is about the Visual Basic one.

Why error 76 path not found appears

Most often the macro was written on another PC or before a change, and a folder in its path no longer exists on this PC. Less often the folder exists but is out of reach: a drive is not connected, or the macro runs with other rights. Rarely the program itself was installed badly.

How to fix run-time error 76 path not found

Fix 1 finds the exact path and solves most cases on its own. Fixes 2 to 5 cover the four ways a path breaks. Fixes 6 and 7 are for a protected folder and for programs whose code you cannot see.

Fix 1. Find the exact path with Debug and check it in File Explorer

5 minutesNo riskEveryone with the Debug button, which is anyone running a macro in Excel, Word, Access or Outlook.

Microsoft's reference gives one solution for error 76: respecify the path. You can only do that once you see the exact path the code used, and the debugger shows it.

1. In the error box, select Debug. The Visual Basic editor opens with the failing line marked in yellow.
2. Hover the mouse over the variable that holds the path, for example strPath, to see its value in a small tooltip.
3. If the path is built from several parts, press Ctrl + G to open the Immediate window, type the line below with your own variable name and press Enter.

   ? strPath

4. Copy the path without the file name at the end.
5. Press Win + E, click the address bar, paste the path and press Enter.
6. If Windows says it cannot find it, delete the last folder from the address and press Enter again. Repeat until a folder opens: the part you just removed is the missing one.
7. Correct that part in the code, or create the folder, then select Run > Reset and run the macro again.

Fix 2. Point the macro to the real Documents or Desktop folder after OneDrive backup

5 minutesLow riskThe path goes to Desktop, Documents or Pictures under C:\Users\<name>, and OneDrive is signed in.

OneDrive folder backup moves Desktop, Documents, Pictures, Music and Videos into your OneDrive folder. A macro with the old fixed path then asks for a folder that is empty or gone.

1. Open File Explorer, right-click Documents (or Desktop) in the left pane and select Properties.
2. Select the Location tab and read the path in the box. If it contains OneDrive, the folder was moved.
3. Copy that path and use it in the macro instead of the old one, or open the file's folder from there.
4. To see which folders OneDrive backs up, select the OneDrive cloud icon in the taskbar, then the gear, Settings.
5. Select Sync and backup and then Manage backup to see each folder's switch.

Fix 3. Reconnect the network or USB drive, or use the full network path

5 minutesNo riskThe path starts with a drive letter such as Z:, S: or E: that belongs to a server share or a removable drive.

A drive letter is only a shortcut. When the share is not connected after sign-in, or the USB stick got another letter, every path that starts with that letter fails with error 76.

1. Press Win + E and select This PC. Look for the drive letter from the path under Network locations or Devices and drives.
2. If a network drive is shown as disconnected, double-click it and sign in when asked.
3. For a USB drive, plug it in and read the letter Windows gives it. If it is a different letter, change the path in the macro.
4. To see every mapped drive and the full network path behind it, press Win + R, type cmd, press Enter and run:

   net use

5. Write down the Remote column for your drive letter, for example \\server\share.
6. In the macro, replace the drive letter with that full network path, so the code no longer depends on the letter being connected.

Fix 4. Start the program without administrator rights, or let elevated programs see mapped drives

10 minutesRead the warningThe macro works when Excel or the program is started normally, and fails when it is started with Run as administrator or always runs elevated.

Microsoft explains that with User Account Control on, Windows creates two linked sign-in sessions, and drive letters made in one are not shared with the other. The EnableLinkedConnections registry value makes Windows write them to both.

First try the simple way: start the program normally. Right-click its shortcut, select Properties, then the Compatibility tab, and clear Run this program as an administrator if it is selected. Select OK and run the macro again.

1. Open Registry Editor. Press Windows key + R, type the command below and select OK. Select Yes when Windows asks for permission.

   regedit

2. Select the key. In the left pane, go to the key your guide will change, or paste its path into the address bar under the menu and press Enter.
3. Export it. Select File > Export.
4. Save the backup. Under Export range, keep Selected branch to save only that key, or choose All for the whole registry. Pick a folder, type a file name and select Save.

   

These steps were written for Windows 11 and Windows 10 (the steps are the same). The full page with the other versions and what each result means: Back up the registry before editing it

1. In Registry Editor, paste HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System into the address bar and press Enter.
2. Right-click an empty area in the right pane and select New > DWORD (32-bit) Value.
3. Name it EnableLinkedConnections and press Enter.
4. Double-click EnableLinkedConnections, type 1 in Value data and select OK.
5. Close Registry Editor and restart the PC.

Fix 5. Create the missing folders before the code saves into them

5 minutesNo riskThe highlighted line uses MkDir, ChDir, SaveAs or Open with a folder that does not exist yet.

MkDir creates one folder at a time. When it is asked for C:\Reports\2026 and C:\Reports does not exist, Windows cannot find the path and VBA stops with error 76.

1. Look at the highlighted line and the path in it. Note every folder that does not exist yet.
2. For a one-off fix, create the folders by hand in File Explorer with New > Folder, in the right order.
3. For a macro that runs every month or year, make it create each folder level before it saves. The code below checks each level and creates only the missing ones.
4. Run the macro again.

Create every missing folder in a path (VBA)

Sub MakeFolders(ByVal fullPath As String)
    Dim parts() As String, p As String, i As Long
    parts = Split(fullPath, "\")
    p = parts(0)
    For i = 1 To UBound(parts)
        If parts(i) <> "" Then
            p = p & "\" & parts(i)
            If Dir(p, vbDirectory) = "" Then MkDir p
        End If
    Next i
End Sub

Call it before the save, for example MakeFolders "C:\Reports\2026". It works for local paths that start with a drive letter. For a \\server\share path, the share itself must already exist.

Fix 6. Check that your account can open the protected folder

5 minutesNo riskThe folder is on a server, another user's profile or a drive with restricted permissions.

A program can only use folders that your account can open. When the account has no access, the program may report the path as not found instead of a permission error.

1. Paste the path into the File Explorer address bar, as in Fix 1.
2. If Windows says you do not have permission, note the exact message.
3. For a folder on your own PC, right-click it, select Properties and open the Security tab to see which accounts have access.
4. For a folder on a server or a work share, send the full path and the message to the person who manages that share and ask for access.
5. After access is granted, sign out and sign in again, then run the macro.

Fix 7. Check the program's data folder setting, then reinstall the program

15 minutesLow riskA finished program, not your own macro, shows the error, and there is no code to read.

Older programs built with Visual Basic keep a data or export folder in their settings. If that folder was moved, deleted or was on a drive that is gone, the program stops with error 76. A clean install recreates its own folders.

1. Open the program's Options, Settings or Preferences and look for a data, database, export or backup folder.
2. Check that folder in File Explorer. If it is missing, choose an existing folder or create it.
3. If there is no such setting, or it did not help, uninstall the program. Step by step: Uninstall a program or app in Windows.
4. Restart the PC.
5. Install the program again from its maker's site or the original installer, into the folder it suggests.

If error 76 is still there

Error 76 has no log file. The debugger line and the path are the whole record, so collect them before you ask for help.

• The exact text of the yellow line in the editor and the value of the path from the Immediate window.
• What File Explorer says when you paste that path into the address bar.
• Whether the file lives in OneDrive, on a network share or on a USB drive.
• Whether the program runs as administrator.
• Your Office version, from File > Account in Excel.

With these five facts the macro's author, or anyone on the Microsoft Q&A forum, can usually spot the broken part at once. Windows 10 left support on 14 October 2025, but error 76 is not tied to the Windows version: it behaves the same on Windows 10 and Windows 11.

How to stop error 76 from coming back

Frequently asked questions

What does run-time error 76 path not found mean?

It means a Visual Basic macro or program asked Windows for a path that does not exist. Microsoft's VBA reference says the operating system was unable to find the specified path during a file or disk operation such as Open, MkDir, ChDir or RmDir. The problem is the drive or a folder in the path, not the file itself. Select Debug, read the path in the highlighted line and paste it into File Explorer to find the missing part.

Why do I get Microsoft Visual Basic run time error 76 in Excel?

Excel shows it when a macro in the workbook tries to open, save or create something in a folder that is not there on your PC. The window is titled Microsoft Visual Basic because Excel macros run in VBA. The most common reasons are a path written on another PC, Documents or Desktop moved into OneDrive, and a network drive letter that is not connected. Fixes 1 to 3 cover these cases.

How do I fix run time error 76 path not found in an Excel macro?

Select Debug, read the path in the yellow line and check it in File Explorer, as Fix 1 explains. Then correct the part that does not exist. If the macro saves into a new folder each month, add the small MakeFolders routine from Fix 5 so that every folder level is created before saving. If you did not write the macro, send its author the path and the line.

Is error 76 the same as error 53 File not found?

No. Error 76 means the drive or a folder in the path is missing. Error 53 File not found means the folder exists but the file in it does not. If you get error 53, check the file name and its extension. If you get error 76, check the folders first, from the drive letter forward, until one does not open.

Can running the program as administrator fix error 76?

Usually not, and it can cause it. Microsoft explains that mapped network drive letters belong to one sign-in session, while an elevated program runs in another. So a macro in Excel started with Run as administrator may not see drive Z: at all. Start the program normally first. If it must run elevated, use the EnableLinkedConnections value from Fix 4 or the full network path from Fix 3.

Does Windows Update, SFC or a Visual C++ reinstall fix error 76?

We found nothing that links them. Error 76 is raised by Visual Basic when a path cannot be found, and Microsoft's only advice for it is to respecify the path. System file repair, Visual C++ packages and Windows updates do not change the folders a macro points to. Spend the time on Fix 1 instead.

What does path not found mean when there is no error number?

Other programs and Windows dialogs also say path not found when a folder or drive is missing, for example a shortcut that points to a moved folder. The cause is the same idea: something in the path is gone. This page covers the Visual Basic message with the number 76, but checking the path in File Explorer, as in Fix 1, helps in those cases too.

Is error 76 always about a path?

In Visual Basic, yes: error 76 is always Path not found. Other software uses the number 76 for unrelated problems, such as a key sync error 76 in some apps or a device error code 76. Those are not covered here. If your message does not say Path not found and does not come from Microsoft Visual Basic, search for the exact text of that message.

What is the difference between error 75 and error 76?

Error 75 is Path/File access error: the path exists, but the operation is not allowed, for example writing to a read-only file or a folder you may not change. Error 76 means the path itself is missing. If you fix error 76 and then get error 75, the folder is now found but your account cannot write to it. Check the permissions as in Fix 6.