Publisher (2.5.6) not responding when I try to replace documents in Resource Manager

[AnnaO]

1. What Application are you using? [Designer/Photo/Publisher] - Publisher
2. Are you using the latest release version? Yes, 2.5.6
   (here's how to check)
3. Can you reproduce it? Every time I open up Resource Manager and click on one of the files to replace Affinity Publisher shows "not responding" and I have to right click to close the program. I've tried waiting it out but it never moves on from this screen. 
   (if you cannot then we may struggle to also, making it even harder to fix)
4. Does it happen for a new document? If not can you upload a document that shows the problem?  Yes, I've tried multiple documents.
5. If you cannot provide a sample document then please give an accurate description of the problem for example it should include most of the following:

•    What is your operating system and version (Windows 11, OSX Ventura, iOS 16 etc)? Windows 11
•    Is hardware acceleration (in Preferences > Performance) ON or OFF ? (and have you tried the other setting?) Yes, I've tried both.
•    What happened for you (and what you expected to happen)
•    Provide a recipe for creating the problem (step-by-step what you did). My file is open, I go to Windows - Resource Manager then click on the document I want to replace then click on "replace". Nothing happens. If I click on the document again, Affinity stops responding.
•    Screenshots (very handy) or a screen capture/video.
•    Any unusual hardware (like tablets or external monitors or drives that may affect things) or relevant other applications like font managers or display managers. - None
•    Did this same thing used to work and if so have you changed anything recently? (software or hardware) - It used to work. No hardware changes, I've updated to Windows 11 24H2 and the problem persists. 

[GarryP]

Welcome to the forums @AnnaO

This might have something to do with one or more images being in a folder which is ‘linked’ to OneDrive storage (see the file path in the screenshot).

The Affinity applications don’t always ‘play well’ with resources that aren’t stored on local storage.

I don’t have a solution to the problem but what I’ve said might give you some idea of where the problem might be coming from.

If it were me, and it was easy enough to do, I would delete the existing ‘problem images’, copy the image to local storage, and then place it into the document again. Maybe lots of work but it should get you going again.

[AnnaO]

That worked! I copied the files to my D Drive, deleted them from my OneDrive and relinked them. Thank you @GarryP!

[GarryP]

You're welcome.