Forum Discussion
MacOS Monterey - Disable Files on Demand
- That sounds strange. I would expect it to be one or the other as you say. On my own Mac running Monterey I cannot duplicate your issue. As you say, you can't disable FOD from the OneDrive client settings but you should be able to do this with a PList as per https://docs.microsoft.com/en-us/onedrive/deploy-and-configure-on-macos#filesondemandenabled
I updated OD on my M1 MackBook yesterday and discovered the above problem today. However I updated Monterey to V12.2 a couple of days before so I don’t know if this is an Apple or MS issue. Because the option to NOT use files On-Demand is no longer in OD preferences my bet would be it‘s an MS issue. I do know that even though there is a little cloud beside each folder and file in Finder the files are actually still on the hard drive. When I clicked on the cloud in the highest level OD folder OD started to “download” all the files, in fact it was just recognising them as there already because the operation took a couple of minutes instead of the couple of hours a full download would have taken. So, I am safely back to where I was pre-updates.
As and old mainframe sysprog I can only say no matter how wonderful one may think the cloud is, always keep up to date physical backups. 🙂
- For me reinstalling did last in a "sorry, onedrive can't add your folder right now"-error. I had to reinstall the previous version.
This is a real pain because it disturbes any workflow: All my tags (and I rely on them) are gone, although I chose the „keep always on drive"-option there is always some delay and it seems that every file has to be downloaded. The preview-function doesn't work. This is pretty useless.Hokey78 exactly the same for me with M1, Monterey 12.1, impossible to install the Microsoft download version because it couldn't sync the directory so had to resort to the App Store where AutoSave is dead in the water.
The slow and ugly way around this is to go to OneDrive on the browser, then "Open in app" so AutoSave is enabled when the file opens. Opening a "local" file has AutoSave disabled and if you attempt to enable, you can only copy or move the file to a library that should already be syncing.
Lost most of the day looking for solutions only to discover that this is a classic "not a bug, it's a feature". Pleading this can be sorted out quickly.
