Fix file, folder, permission, and disk errors
For:All users
No technical knowledge required.These messages concern a selected source, the receiver's destination, browser-granted access, available disk space, or a path that cannot be written safely. Open the question matching your problem, or find the exact code shown by WolfP2P. Each answer quotes the current English message.
Read Why WolfP2P Asks for File and Folder Access to understand the browser safety boundary. For prompt recovery, use Browser Folder Permissions; for browser feature differences, check Browser and OS Compatibility.
Preserve the source and destination
These errors occur while choosing files, preparing a destination, or writing received data. Avoid deleting partial files, replacing destination content, or weakening browser security unless the specific explanation requires that action.
Choosing files and granting access
Did anything go wrong when I closed the file chooser? PICKER_CANCELLED
The file or folder chooser was closed without a selection.
You did not select a file or folder. Open the chooser again when you are ready and select the intended source or destination. Cancelling the chooser is not evidence of a damaged file.
What if my selected file or folder is no longer available? FS_LOCATION_GONE
The selected file or folder is no longer available to this browser.
Check whether the drive disconnected or the entry was moved, renamed, or deleted. Reconnect the drive or select the intended location again. For recovery, preserve and reselect the source and destination belonging to that transfer.
How do I restore access to my selected files? FS_PERMISSION_BLOCKED
The browser does not currently allow WolfP2P to use this file or folder.
Use the access or folder-selection action offered in the panel and grant access if you intend to continue. If the browser refuses without prompting, check this site’s permissions. This message means access is not currently allowed; it does not necessarily mean permission was permanently blocked. See browser folder permissions.
Why can’t I open the file or folder chooser? FS_PICKER_UNAVAILABLE
This browser cannot open the required file or folder chooser here.
Open the official WolfP2P HTTPS site directly, then try the selection action. If the required chooser is still unavailable, check browser compatibility. Changing a folder permission cannot add a browser feature that is missing.
Why does the browser block this file location? FS_SECURITY_BLOCKED
The browser blocked this file operation for security reasons.
Choose an ordinary folder you control rather than a protected system location. If the browser refuses Documents with a system-files message, create a subfolder inside it and select that instead. Do not weaken browser or operating-system security to bypass the block. See protected-folder guidance.
Why can’t the transfer use my selected source anymore? TRANSFER_SOURCE_INVALID
The selected source no longer matches the active transfer.
Check that the selected files still exist, are readable, and have not changed. If the source changed, create a new offer of the intended current files. Do not force saved progress from an older version onto changed content.
Why couldn’t WolfP2P read content for verification? CONTENT_HASH_READ_INVALID
WolfP2P could not read the requested file content for verification.
Keep the source and destination available and restore browser access if requested. Check for a disconnected drive or a file changed by another program. Do not treat the file as verified until WolfP2P confirms it.
Preparing the receiver’s destination
What if a file exists where a folder is needed, or the reverse? FS_ENTRY_TYPE_MISMATCH
A destination entry is not the expected file or folder type.
Inspect the named destination entry. Preserve anything you need and choose another destination or resolve the file-versus-folder conflict deliberately. Do not delete an unfamiliar entry just to proceed.
Why did the browser refuse a destination change? FS_INVALID_MODIFICATION
The browser refused a requested change to the destination.
Check the affected location and any existing content before retrying. Choose a writable destination you control if the operation remains unavailable. Do not assume existing files must be deleted.
What if the browser blocks a required destination change? FS_MODIFICATION_BLOCKED
The browser blocked a required destination change.
Confirm destination access and whether the folder or drive is read-only or protected. Choose a suitable writable destination if needed. Do not disable security controls to force the change.
Will WolfP2P overwrite a different file already there? TRANSFER_DESTINATION_CONFLICT
Existing destination content differs from the offered source content.
Existing destination content differs from the source. Review the conflict and use the choice offered by the panel only if you intend it. Preserve the existing file or choose another destination if you need both versions; do not assume matching names mean matching content.
Why can’t I apply my destination-conflict choice? TRANSFER_CONFLICT_NOT_ACTIVE
There is no active destination conflict to resolve.
There is no longer an active conflict awaiting that choice. Read the updated transfer panel and continue with its available action; do not repeat a stale replacement decision.
What must the receiver do before files can arrive? TRANSFER_DESTINATION_NOT_READY
The destination is not ready to receive this transfer.
On the receiving computer, choose the intended destination, grant requested access, and resolve any conflict shown. If Documents is refused with a system-files message, create a subfolder inside it and select that instead; see folder permissions. Continue only when the panel says the destination is ready.
Why can’t WolfP2P create or open a destination folder? TRANSFER_DESTINATION_DIRECTORY_FAILED
The browser could not open or create a required destination folder.
Check that the drive is connected, the parent folder is writable, and no file occupies the required folder path. Restore access or choose another destination if needed.
Why can’t WolfP2P access the destination file? TRANSFER_DESTINATION_FILE_HANDLE_FAILED
The browser could not obtain a usable handle for a destination file.
Check the destination folder and browser access. If another application is using the file, let its work finish before retrying. Choose another destination if access cannot be restored.
Why couldn’t WolfP2P check existing destination files? TRANSFER_DESTINATION_INSPECTION_FAILED
WolfP2P could not inspect the destination safely.
WolfP2P could not safely inspect the destination before deciding what to write or reuse. Check drive availability and access, then retry the action offered. Do not approve replacement without reviewing the existing content.
What if the destination file won’t open? TRANSFER_DESTINATION_OPEN_FAILED
The browser could not open the destination file.
Check that the destination still exists and the browser can access it. Let other applications finish using the file, then use the offered retry action or choose another destination.
Why can’t a file or folder name be recreated? TRANSFER_DESTINATION_PATH_INVALID
A destination path cannot be recreated safely by this browser.
The offered path cannot be recreated safely in this browser or destination. Check the affected name with the sender and, if necessary, rename the source entry and create a new offer. Do not bypass path validation.
Why couldn’t an approved replacement be prepared? TRANSFER_DESTINATION_TRUNCATE_FAILED
The browser could not prepare the destination file for replacement.
The browser could not prepare the destination for replacement. Check access, available storage, and whether another application is using it. Inspect the existing destination before retrying; do not assume the old content is intact or the new file complete.
Why can’t WolfP2P start writing the destination file? TRANSFER_DESTINATION_WRITABLE_FAILED
The browser could not open a writable destination stream.
Confirm write access and available space, and let other applications finish using the file. Retry only through the action offered, or choose another writable destination.
Writing, storage, and saving a checkpoint
Is the destination full, or is the browser out of storage? FS_QUOTA_EXCEEDED
The destination does not have enough available storage for this operation.
Check free space on the destination drive and any browser storage limit. The message can mean a storage quota, not just a full physical disk. Make space without deleting this transfer’s recoverable files, or choose another destination. Safe and Quick modes have different space and recovery needs.
Why did a destination file stop accepting writes? FS_STREAM_INVALID_STATE
The destination file stream was no longer in a writable state.
The browser’s write stream is no longer usable. Check the drive and browser access, keep the files, and use the recovery action offered. Progress that was not durably saved may need sending again.
What should I check after a write fails? TRANSFER_DESTINATION_WRITE_FAILED
The browser could not write the current data to the destination.
On the receiving computer, check free space, drive connection, and write access. Let other programs finish using the destination. Keep both tabs open while the panel offers recovery, and do not count unsaved progress as complete.
The file reached the end—why couldn’t it be saved? TRANSFER_DESTINATION_COMMIT_FAILED
The browser could not commit the completed file to the destination.
Receiving the bytes is not the same as committing them to the destination. Check storage, destination access, and drive availability, then follow the offered recovery action. Keep the original source until durable completion is confirmed.
What if a recovery checkpoint could not be saved? TRANSFER_CHECKPOINT_FAILED
WolfP2P could not create a durable checkpoint for the current file.
Check destination space, access, and drive availability. Keep the files and follow the panel’s recovery action. Only the last confirmed durable checkpoint is a recovery point; more recent progress may need sending again.
How do I find which file operation failed? TRANSFER_IO_FAILED
A browser file operation failed during the transfer.
Read the more specific message on each computer. The sender may need to restore source access; the receiver may need to restore destination access or space. Keep both tabs open and use the available recovery action after correcting that issue.
- Complete folder preservation and disk-backed large-file handling require a Compatible Browser, such as current Chrome, Edge, or Brave, with the required capabilities confirmed by WolfP2P's live check.
- Mid-file checkpoint resume requires the receiver to use Safe mode. Safe mode may need about twice the file's size in free disk space, and an interruption can require retransferring up to approximately 256 MB of the current large file.
- Quick mode uses about the file's own size in free disk space and avoids checkpoint-copy overhead, but an interrupted current file restarts from its beginning.
- An interrupted browser write may leave browser-managed temporary files. WolfP2P does not implement a separate temporary-file cleanup operation; use browser and operating-system guidance before removing unfamiliar files.