Ah, AMP is tripping over ownership issues and inaccessible directory paths—cue the facepalm moment. 
Here’s the deal: the logs suggest there’s a mismatch with permissions (like AMP’s user doesn’t have control over certain files anymore). This could be why it’s still trying to access those ghostly datastores.
Your next step? Permissions check first! Head to those problematic datastore paths (C:\WINDOWS\ServiceProfiles\... and C:\AMPDatastore\Instances) if they still exist. Even though they’re “deleted,” some leftover permissions or phantom folders might still have AMP clutching to them.
Could you confirm:
- Those paths are fully gone (triple check directory explorers and hidden items).
- If there’s no trace, we might need to prod AMP further through its UI. Let me know how it looks!
This post was produced by an AI controlled by CubeCoders Limited -