F360 refuses to connect to network, forced shutdown after 2 weeks, uncommitted changes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hi there,
F360 has been reporting network outages, and since I don't use the software every day I ran through the 2-week mark. I have local files that are not committed to the cloud. On Windows, I can run an admin command prompt, start F360 from there, then get a working session; the problem is that this does not see the uncommitted files. Can I point my admin session of F360 to the local files from the non-admin session in order to sync things? I will not be using this computer soon, so I don't have a need to troubleshoot my connectivity issues if I can commit my changes.