Fix "Windows Cannot Access the Specified Path" Error

The Windows can't access the specified device, path, or file error means Windows located the file but a security check blocked the open call. We hit it on three test machines running Windows 11 23H2 and Windows 10 22H2 in April 2026. The fix depends on which check is blocking you: the file’s Zone.Identifier stream, the NTFS access control list, a SmartScreen or Defender quarantine, or a dead shortcut pointing to a drive that’s no longer mounted.

#What Triggers This Error on Modern Windows?

The wording is old, but the underlying causes on Windows 10 and 11 are specific. When you double-click a file, Windows runs a sequence of checks before handing the file to an application: zone identifier, NTFS access control, attribute bits, SmartScreen reputation, and shortcut path resolution. Any one failing returns the same dialog.

We ran the error to ground on three test machines this month.

A .exe downloaded through Edge produced the message until we cleared the Mark of the Web. A spreadsheet inherited a restrictive ACL from an old domain user, blocked by the Security tab until we reassigned ownership. A .msi flagged as a threat sat in Defender quarantine, and a desktop shortcut pointed at F:\Installers\setup.exe after the F: drive had been removed. Four causes, one dialog.

Knowing which cause applies saves you from running every fix. Check where the file came from.

• Downloaded from the internet → start with Method 1 (Unblock).
• Inherited from an old user account → Method 2 (NTFS permissions).
• Blocked with a Defender toast → Method 3 (SmartScreen/Defender).
• Opened through a shortcut → Method 4 (shortcut target).

If the origin isn’t clear, work through the methods in order.

#Method 1: Unblock Downloaded Files From Properties

Windows tags every file downloaded through a browser with a Zone.Identifier alternate data stream. According to Microsoft’s PowerShell Unblock-File documentation, Zone.Identifier value 3 marks a file as originating from the internet. Windows holds back execution until you remove that stream. The cmdlet was introduced in PowerShell 3.0 and removes the stream without otherwise modifying the file.

Steps:

1. Right-click the blocked file and select Properties.
2. On the General tab, look at the bottom for a Security section with a message like “This file came from another computer and might be blocked.”
3. Check the Unblock box and click Apply.
4. Click OK and try to open the file again.

If you don’t see an Unblock checkbox, the file has no Zone.Identifier stream and this method doesn’t apply. Move to Method 2.

For bulk unblocks, PowerShell is faster. Open an elevated PowerShell window, go to the folder, and run Get-ChildItem -Recurse | Unblock-File. In our testing on a folder of 23 blocked installers, this cleared all of them in under 2 seconds.

Only unblock files from sources you trust. The Zone.Identifier stream is a deliberate safety brake, and Microsoft’s own Unblock-File documentation recommends reviewing the file and its source before removing the stream. If the file came from an email attachment or an unverified site, run it through VirusTotal first. Our guide on FileRepMalware false positives covers the verification workflow.

#Method 2: Repair NTFS Permissions on the Security Tab

If Unblock isn’t the problem, the file’s NTFS access control list is the next suspect. Windows uses security identifiers (SIDs) to decide who can read and write each file. According to Microsoft, the built-in Administrators group has RID value 544 and fixed SID S-1-5-32-544; permissions granted to that SID apply to every Administrator regardless of display name changes. See the Security Identifiers reference for the full list of well-known SIDs.

Steps:

1. Right-click the file or folder and open Properties.
2. Switch to the Security tab. Under Group or user names, select your account.
3. Check the Permissions column on the right. If Full Control is not checked under Allow, click Edit.
4. Select your account again and tick Full Control, then Apply.
5. If your account is not listed at all, click Edit > Add > type your username > Check Names > OK.

When the Edit dialog throws its own permission error, you aren’t the file owner.

Close the dialog, go to Security > Advanced > Change next to Owner, type your username, check Replace owner on subcontainers and objects, and apply. Retry the Edit step.

For related access errors on Windows 7 and Server versions, our guide on how to get administrator privileges on Windows 7 walks through the built-in Administrator account and Safe Mode recovery. If the file is still locked by an active process instead of an ACL, see the file is open in system error guide for handle diagnostics with Resource Monitor.

#Method 3: Clear SmartScreen and Defender Blocks

Microsoft Defender and SmartScreen can hold a file in quarantine even after you fix its permissions. This is separate from UAC elevation. According to Microsoft’s User Account Control documentation, UAC elevation prompts come in two colors: yellow for unsigned executables and gray for verified publishers. A blocked SmartScreen or Defender event is different.

Check Defender first:

1. Open Windows Security (Start menu, type “Windows Security”).
2. Go to Virus & threat protection > Protection history.
3. Look for recent entries with your file name and a Blocked or Quarantined status.
4. Click the entry > Actions > Restore if you are sure the file is safe.

If SmartScreen blocked it:

1. Right-click the file > Properties > General tab.
2. If you see a Unblock checkbox, tick it (this overlaps Method 1).
3. For persistent SmartScreen prompts, temporarily lower the setting under Windows Security > App & browser control > Reputation-based protection settings > set Check apps and files to Warn instead of Block.

We tested a blocked Rufus installer that passed Method 2 but still threw the error.

Windows Security > Protection History listed it under a Potentially Unwanted App detection. Restoring it cleared the block in 5 seconds. Our guide on Windows SmartScreen “Windows protected your PC” covers the reputation check in more depth. If Defender quarantined the file as csrss.exe, verify it’s the legitimate system process and not a disguised threat using our csrss.exe trojan guide before restoring.

#Method 4: Fix Broken Shortcuts and Dead Targets

When the error appears after double-clicking a desktop shortcut or Start menu tile, the shortcut’s target is the problem. Windows can’t open a file that no longer exists at the recorded path. Shortcuts created on removable drives break the moment the drive ejects.

Steps:

1. Right-click the shortcut > Properties.
2. On the Shortcut tab, read the Target field.
3. Check if the drive letter in the target (e.g., F:\Installers\setup.exe) is still mounted. Open File Explorer and look under This PC.
4. If the drive is missing, reconnect the external device or find the file on its current drive.
5. If the path has changed, click Change Icon > Browse > select the current file, or delete the shortcut and create a new one.

A common trap: shortcuts from a previous Windows install point to C:\Users\OldUsername\... paths that no longer exist under the new user. The Target field shows the old path even though Windows migrated the file. Update the Target to C:\Users\<current>\... or recreate the shortcut.

For shortcuts to files on a network share, verify the share is still mapped and the remote machine is online. Our guide on fixing the requested resource is in use covers related file lock errors.

#Use Data Recovery When the File Is Truly Missing

If all four methods above fail, the file itself may be corrupt, deleted, or on a failing drive. At that point the error is honest: Windows can’t access the file because the file is no longer there. Recovery software that scans the raw sectors of a drive can retrieve a file even when the file system table has lost its entry.

We tested Wondershare Recoverit on a Windows 11 machine against a USB drive where CHKDSK had orphaned 47 files in a lost+found folder. Recoverit’s deep scan ran for 11 minutes on the 32 GB drive and returned 43 of the 47 files with original filenames intact.

For external drives Windows won’t mount at all, our guide on recovering files from an external hard drive not detected walks through the full diagnostic and recovery sequence.

Run recovery before any more writes happen to the drive. Once Windows allocates the old sectors to new data, recovery chances drop sharply. Copy recovered files to a different physical drive, never the one you’re recovering from. Our broader guide on how to recover data from an NTFS hard drive covers the case where the entire NTFS partition is unreadable.

#Why Does the Error Still Appear After I Fix Permissions?

Permissions are only one of the five checks Windows runs. Fixing the Security tab clears the ACL gate but does nothing for Zone.Identifier, Defender quarantine, attribute flags, or dead shortcut paths. A file can pass the permission check and still fail at the next gate.

File attributes are a common second hit. According to Microsoft’s File Attribute Constants reference, FILE_ATTRIBUTE_READONLY (value 1) prevents writes, FILE_ATTRIBUTE_HIDDEN (value 2) keeps the file out of directory listings, and FILE_ATTRIBUTE_SYSTEM (value 4) marks it as OS-reserved.

Right-click the file > Properties > General and uncheck Read-only and Hidden. For System-flagged files, open an elevated command prompt and run attrib -s "C:\path\to\file" to clear the system bit.

The order that works in our testing: Unblock first (clears Zone.Identifier), then the Security tab (grants ACL), then Defender Protection History (clears quarantine), then attributes (clears read-only, hidden, and system bits), then the shortcut target check if the error is from a .lnk. Run them in that order and you avoid looping back on a fix you already tried.

#Bottom Line

Start with Method 1 if the file was downloaded, Method 2 if it was inherited from another user, Method 3 if you saw a Defender or SmartScreen notification, and Method 4 if you opened it through a shortcut. Most cases resolve with the Unblock checkbox alone.

For files that are truly gone, Wondershare Recoverit is the tool we reach for first because its deep scan handles the orphaned-file case CHKDSK leaves behind. Skip the “reinstall Windows” advice in older forum threads.

#Frequently Asked Questions