Runtime Error 76 in VBA: “Path not found,” explained and fixed

Error 76 — “Path not found” — is error 53's close relative: the file may be fine, but a folder in the path doesn't exist. Somewhere between the drive letter and the file name, one level of the path is missing, misspelled, or was never created.

What it means

Operations that save, copy, create, or change into a folder — SaveAs, FileCopy, MkDir, ChDir — all need every folder in the path to exist. VBA does not create intermediate folders as it goes. If any level is missing, the whole operation stops with 76.

The usual causes, most common first

The output folder doesn't exist yet — the macro saves into a folder (often dated, like Reports\2026-11) that nothing created first.
MkDir asked to create nested folders at once. MkDir "C:\a\b\c" fails if b doesn't exist — MkDir makes exactly one level.
A network share or drive isn't connected — the mapped drive shows a red X, or the VPN is down, so the path's root itself is unreachable.
A folder name is built wrong — a date formatted with slashes (11/05/2026) turns one folder name into three path levels.
The path is too long — very deep folders plus long names can exceed Windows' classic 260-character path limit.

The fix

Create folders one level at a time, testing as you go:

Dim p As String
p = "C:\Reports"
If Dir(p, vbDirectory) = "" Then MkDir p
p = p & "\2026-11"
If Dir(p, vbDirectory) = "" Then MkDir p

Sanitise names built from dates or cells: replace / and \ in values used as folder names — Format(Date, "yyyy-mm-dd") is safe; CStr(Date) usually is not.
Check the root is alive: click the drive in File Explorer. If the share won't open there, it won't open for the macro — reconnect the drive or the VPN first.
Shorten the path if it's extreme: save closer to the drive root or shorten folder names.

Do not download anything for this error. A folder is missing or misnamed. Creating it (or fixing the name) is the entire cure.

If it still happens

Print the full path with Debug.Print, then walk it in File Explorer one folder at a time. The first level that doesn't open is the culprit — it's misspelled, uncreated, or on a share that isn't connected. Every 76 ends at exactly one such level.

Common questions

What's the difference between error 53 and error 76? 53 is about the file; 76 is about the folder path leading to it. Both mean “not there” — at different levels of the path.

Why does the dated folder fail at month-end? Because the new month's folder doesn't exist yet and nothing created it. The one-level-at-a-time creation pattern above is the permanent fix.