Why NativeActions refuses a path
To avoid writing somewhere you did not intend, NativeActions only works with ordinary files and folders on this computer. It stops with a clear message instead of following a path it cannot use safely.
Common causes and fixes
- Names that end with a space or a dot, or reserved Windows names such as CON or NUL: rename the file in File Explorer.
- Symbolic links and junctions: open the real folder the link points to and select the file there.
- Very deep folders with long names: move the file closer to the top of the drive, for example into a folder in Documents.
- Online-only cloud files: make the file available on this device first, as described in the OneDrive guide.
OneDrive and synced folders
Folders synced by OneDrive, such as a synced Desktop or Documents folder, are supported. Only files that are still online-only need to be downloaded before an operation reads them.
You’re all set.Back to the help center