How can I find out which app is using a file before I try to move it?

Start with the apps and windows you can identify, rather than trying to force the move. Check open documents, previews, media players, and any app where you recently worked with that file. If you find it, bring that app forward, save your work, and close the file in the app’s usual way. Then retry the move.

Microsoft recommends saving and closing an open file before trying again in its OneDrive folder-backup troubleshooting context. [S1] That guidance supports this cautious first step; it is not a general method for identifying every process that may hold a file, and it does not establish how every move operation behaves.

Don’t close unknown processes or end apps abruptly just to make the move work. First, check any other visible windows or apps where the file might be open, including a separate window that may be behind the one you’re using. Save other work before closing an app you recognize, and close it normally if appropriate. If you’re unsure whether an app has unsaved changes, leave it open and ask for help rather than guessing.

The cited Microsoft guidance does not explain a general process-identification tool, so I can’t point to one as a verified solution for every computer. The safest approach here is to use apps you recognize and avoid forceful workarounds.

Save the file using the editor, check that you have finished any changes you want to keep, and close that file normally. Then try the move again. For the specific OneDrive folder-backup troubleshooting context, Microsoft says to save and close a file that is open and cannot be moved, then try again. [S1]

If the message returns, don’t assume you found or closed every possible user of the file. Check visible apps once more, and note the exact message and what you had open. If the file is in a work-managed location, contact your organization’s support or device administrator; otherwise, use the support channel for your device or app. The source does not establish the cause of a recurring message or a universal fix.

Use this checklist:

1. Note the file name and the exact in-use message.
2. Check apps and windows you recognize for that file.
3. If you find it, save your work and close the file normally.
4. Retry the move once the file is closed.
5. If the message persists, avoid ending unknown processes; record what you tried and ask the appropriate support person.

For example, if a document editor visibly has the file open, save and close the document, then retry the move. If you don’t find it in a visible app, stop short of force-closing unfamiliar items and get help. This is a cautious workflow, not a guarantee that it will identify every cause.