After upgrading to Monterey MS Onedrive folder got inside iCloud

I have the same issue, OneDrive 21.210.1010.0001.

OneDrive on Big Sur no issues and location was $HOME/OneDrive.

After Monterey install, the location is now $HOME/Library/CloudStorage/OneDrive and $HOME/OneDrive is a link to the first.

As CloudStorage seems to be this magic-handled folder by Monterey, I can't move it.

It looks as if icloud sees all the files as cloud only.

opening a folder comes up emtpy, then the content comes seconds later.

OneDrive is synchronizing files that were not touched and it takes forever.

It really looks as if icloud sees all as cloud and when onedrive or Finder access, it does an on-demand download. which would explain why OneDrive takes forever.

As OneDrive has file history that I don't want to lose, how do I turn off the icloud magic or how do I move the onedrive folder out of CloudStorage and into the former original location?

Same issue here.

Files were initially cloud based which caused errors on regular backup, which is how I discovered this change. I had to manually set them to remain on my device.

I unlinked one of my accounts and now cannot delete the folder created by OneDrive.

I can't find anything on Microsoft support about this.

This is what I found at Microsoft:

https://support.microsoft.com/en-us/office/save-disk-space-with-onedrive-files-on-demand-for-mac-529f6d53-e572-4922-a585-e7a318c135f0#Category=For_Insiders

You can right-click on any folder and select "Always keep on this device". Works fine except for some large keynote-files for which permission-errors are reported. Most annoying.

I have a similar problem.

I upgraded my home iMac 2020 to Monterey a few days ago.

I use a work / institutional OneDrive account to keep my work synched between home & office Macs.

After the upgrade, on my home iMac, I started having problems with not being able to open files/documents located in my OneDrive folder. Initially I thought this was a permissions problem as when I tried to open a file from within MS Office apps I got an error message along the lines of "user doesn't have access permission". I rebooted but the problem persisted. I then noticed that my sidebar shortcut to OneDrive was gone, along with shortcuts to various OneDrive subfolders, and that OneDrive had not automatically restarted. I manually started OneDrive and found the preference "open at login" was unchecked. I corrected this and rebooted. Unfortunately that was not the end of the problem, as my OneDrive files now all appear to be located solely in the cloud, and are NOT accessible from local HDD storage. Strangely, this includes files that I generated in the past day or two and which I believed I had saved in my local OneDrive folder.

The OneDrive files which are no longer accessible locally amount to hundreds of Gb of data.

When I browse my OneDrive folder there are lengthy pauses as it attempts to populate the file menu from the cloud. When I try and open files, they do indeed have to be downloaded from the cloud. This is a marked change from before.

My OneDrive folder in my user folder is also now an alias. In my case this points to:

Interestingly, a quick check of my HDD storage suggests that my OneDrive files likely do still exist on the local drive - as >400Gb of "systems data" - they are just not accessible as user documents any longer.

This is a major degradation of OneDrive function.

I would love to get this problem fixed ASAP. It would take days to download all of these files from the cloud again, and there might be issues with file versions. I also previously had some files stored locally that had naming issues (illegal characters etc) that had prevented synching to the cloud, so these would be lost if I relied solely on restoring from cloud files. (I had always meant to fix the file names but there were many files, and was waiting for a tool to be developed that would do it for me)

Any ideas?

Thanks,

Rodger

Problem partly solved, .. thanks to time on the phone / screen share with apple support (and graduating from junior->midlevel->senior advisor). Thanks Apple!

For some reason, after the upgrade to Monterey, there was a new conflict between OneDrive and iCloudDrive. As a result, as previously noted, all of my OneDrive files (>400Gb) that previously were stored locally showed in finder as only being stored in the Cloud and not locally. And, in fact the oneDrive behaviour had changed - when I browsed through the OneDrive folders the menus lagged as they populated from cloud data, and when I opened a file it also had to download from cloud storage. When I tried to open a recent file from Word it was not found, as the the OS now indicated that the file was stored in the cloud and not locally.

All this, despite the oneDrive files also still being stored locally. From About this Mac>Storage I could see that the OneDrive files were still on the local HDD - amounting to >400Gb of HD usage. These were classified as "System Data" and not immediately accessible from Manage Storage.

We were able to follow that huge amount of data in finder and located the original local OneDrive files in:

Macintosh HD>users>[user name]>Library>Group Containers>XXXXXXXXXX.OneDriveStandaloneSuite>OneDrive - [account name].noindex>OneDrive - [account name]

In this folder I found all of my original files, and these showed as locally stored files rather than cloud based.

(to follow the data in finder, start at your user account and ensure the finder window is set to list view, then find the circle with 3 dots at top right corner and >show view options>calculate all sizes - you need to do this for every subfolder).

Unfortunately finding the original local OneDrive files does not solve the problem that the OneDrive app is not using these, but is continually looking to the cloud for files/menus. To try and resolve this, the only solution that was suggested was to disable iCloudDrive (or disable oneDrive). Disable iCloudDrive by going to Apple>System Preferences>iCloud>uncheck iCloud Drive --> and agree to store an archived version locally and disable. This does mean that iCloud won't synch documents with my local iMac, but I don't use that function much anyways on this iMac - I mainly using OneDrive to synch files from home and work, as that's what my institution requires. And I still have Keychain / contacts /reminders etc synched via iCloud, so I shouldn't loose any other functionality. Unfortunately after making this adjustment, the OneDrive folder located in the Finder sidebar still shows the cloud icon beside all of the subfolders and documents. Despite this, it initially appeared as the files were being used locally (and I let the apple support guy go) but subsequently I realized that we'd only been checking files/ folders in a folder that he had had me download from the cloud -- so of course it was working fine. Other folders still appear to be functions from the cloud, and not accessing the local files stored at the location above. So unless i get this sorted I am soon going to have 2 copies of these 450Gb files stored on my 1Tb drive. Will keep working on it. Worst case scenario is I turn off OneDrive synching, copy the original local folders/files (stored locally in the folder above) into the current OneDrive folder to replace the shadow folders currently there, ensure the OneDrive preference for storing the files locally is enabled, and then re-enable OneDrive synching. Will save me downloading the 400Gb and will ensure that I dont loose any files that previously had not synched to the cloud..

Am grateful to Apple for the support, but wish this problem hadn't occurred in the first place.. previously had no issues.

One further update:

The original local OneDrive folder, which is now located in:

Macintosh HD>users>[user name]>Library>Group Containers>XXXXXXXXXX.OneDriveStandaloneSuite>OneDrive - [account name].noindex>OneDrive - [account name]

continues to function as an active OneDrive folder, and contains all of my original data stored locally.

I added a test folder to this folder and it immediately synched to my online OneDrive folder. Files also synched in the reverse direction. Interestingly, this new test folder also showed up in the 'new' (post-Monterey) OneDrive folder listed in the Finder sidebar under 'Locations'. In this folder however the test folder appears as an online folder rather than as a locally stored file.

So it appears that the new (post-Monterey) OneDrive folder listed in the Finder sidebar under 'Locations' provides a synched connection to the files stored in the cloud, but ignores all of the OneDrive files that I previously stored/generated locally, whereas the local OneDrive folder located within >Library>Group Containers contains the full files that I previously stored/generated locally. Both folders now work as OneDrive folders, but if I download files from the cloud into the new (post-Monterey) OneDrive folder, I'm guessing that I would probably end up storing 2 copies of the same file on my local HDD.

The bottom line: The Monterey upgrade seems to have buried my original local OneDrive folder, containing locally-stored data (in my case >400Gb data), 5 layers down in a dark corner of the user folder tree, and instead provided a sidebar OneDrive folder under "Locations" with a different functionality - a folder that looks only to the data stored on the OneDrive cloud, significantly reducing oneDrive performance. Making OneDrive access large amounts of data from the cloud when it is stored locally is bizarre.

For now, as the old local OneDrive folder within >Library>Group Containers seems to be functioning, I have re-added a shortcut to it to my sidebar and will use it as my local OneDrive folder.

Sorry for the long story. Hope it helps someone.

Hi Diasleo,

yes, I agree, the Apple support suggestion of disabling iCloudDrive does not appear to fix the OneDrive issue. And the OneDrive folder at:

Macintosh HD>users>[user name]>Library>Group Containers>XXXXXXXXXX.OneDriveStandaloneSuite>OneDrive - [account name].noindex>OneDrive - [account name]

does lack the function of identifying whether or not the file is stored locally or only in the cloud - though, in my case, most of the files are local. I guess thats the "noindex" part of the file name?

Hopefully MS support can help, but if not an alternative may be to try: turning off OneDrive synching, copy the original local folders/files (stored locally in the folder above) into the new (post Monterey) OneDrive folder to replace the shadow/cloud-based files/folders currently there (without deleting any files/folders that aren't replaced), ensure the OneDrive preference for storing the files locally is enabled for the root folder, and then re-enable OneDrive synching. Also make sure that the OneDrive preference "open at login" is on. In theory, this should ensure that you have a local copy of your OneDrive files, and that the files previously stored locally dont need to be downloaded again. The files should be in a folder with location indexing (local vs cloud). However I haven't tried this yet, and would probably back up my important files before trying..

Would be good to hear what MS support has to say.

Rodger

Thanks for sharing, I'm feeling fortunate that I found this post. I'm suffering the same as Rodger1970 and diasleo – similar experiences and issues with MS OneDrive and a post-Monterey (12.0.1) install.

I am also at an institution (Sweden) – admin personnel, not research – not sharing OD data with colleagues.

I sync my files/folders between my work iMac (Retina 5K, 27" 2019), my work MacBookPro (mid-2015) with Big Sur 11.5.2 and my private MBPro (mid-2014) with Big Sur 11.5.2. Luckily I've not even tried to update my MBPros.

My issues seem to originate with my post-Monterey iMac. Problems consist of the inability of opening any OD-based files locally, regardless of application, new files/folders not syncing, botched icons and functions.

Sad to say that I've tried several times deleting everything and reinstalling OD, including long manual uninstall and finally killing supposed corrupted .DS_Store files with Terminal with I cannot recommend as a solution.

I'm down to my last 94GB on my private MBPro (1TB), so I'm not prepared to download my entire OD files/folders collection. Instead, I plan to cool down and work using MS SharePoint apps, manually uploading/downloading my daily files until a solution is presented here.

Keep posting Rodger1970 and diasleo!

Hi Leonardo,

Thanks for taking this up with MS Support. You did a nice job of highlighting the issues with the images and screen recordings. Hopefully they will come back with a sensible response. I'm still hoping for a fix to be released.

Although I had hoped to use the local folder :

Macintosh HD>users>[user name]>Library>Group Containers>XXXXXXXXXX.OneDriveStandaloneSuite>OneDrive - [account name].noindex>OneDrive - [account name]

..as my permanent OneDrive folder - since it contains my locally stored files, the lack of indexing is problematic. Many files at this location - presumably the files that were originally stored locally - open normally from here, without needing to download from the cloud. However other files within this folder do not function - probably because they were originally stored in the cloud?. When browsing this folder and subfolders, there is no way to tell which file will work, until you attempt to open it. And although the folder synchs with the cloud OneDrive, it doesn't seem to know to download a functional version of a non-functional ghost/alias file even when you try and open it - it just gives an error message.

Interestingly, I think my OneDrive updated at least twice, if not more, today (v21.225.1031.0001->1.0002->1.0005):

However I rebooted and restarted OneDrive twice but there was no apparent fix to the problem :-(

Rodger

Thanks Leonardo

I rather foolishly followed the Microsoft OneDrive Support recommendation offered to you by Kumar S. to reset my OneDrive.

I was lulled into complacency by the fact that we have an identical problem and by the MS statement "You will not lose any data by resetting or uninstalling OneDrive."

Technically, this may be close to true, as resetting OneDrive did not wipe my data stored in the cloud, but it did erase most of my locally stored data, which was what I'd been trying to avoid and was the reason for seeking support in the first place. I did have some locally stored files that may not have synched to the cloud due to file name irregularities.

I followed the instructions to Quit OneDrive and double-click: ResetOneDriveAppStandalone.command

Immediately the local files in Macintosh HD>users>[user name]>Library>Group Containers>XXXXXXXXXX.OneDriveStandaloneSuite>OneDrive - [account name].noindex>OneDrive - [account name] vanished, although the folder/file structure subsequently rebuilt itself in a slow staggered fashion (from the cloud?). However the locally stored data from this folder is gone and files now contained within are non-functional shells.

At the same time a new folder was created: Users>rodger>OneDrive-UHN (Archive). However, this folder only contains some (20%?) and not all of the files previously stored locally in the folder above. Why some files were selected for archiving and others were not seems random. As least I could not identify a logical basis. This further fragmentation of my data into yet another folder is really annoying.

I previously had 400Gb of data stored locally in Macintosh HD>users>[user name]>Library>Group Containers>XXXXXXXXXX.OneDriveStandaloneSuite>OneDrive - [account name].noindex>OneDrive - [account name] (vs 600-700Gb in cloud), and now only have 70Gb in the Archive folder.

Fortunately I have a back up of my OneDrive from home and work iMacs (I need both, as I don't synch all folders to either computer).

At this point I'm going to set the new OneDrive (post Monterey) folder (or at least most of the subfolders), stored under "Locations" on the sidebar, to "always keep on this device" and have OneDrive download my cloud data to generate a local version of the files. This will mean downloading the 400Gb again, which may take quite some time. At least now I don't have to worry about having 2 local copies of these files on my HDD now, as the OneDrive restore deleted the previous copy (or 80% of it). I definitely need a local version of the files to keep my work efficient. I also need a local copy of the files in order to back-up these files up to an external HDD. I'll likely be missing a few files that hadn't synched from the previous local folder to the Cloud, and will have to hunt through my OneDrive back-ups for these.

I'll probably leave the Archive files lying around for a bit, in case there is a reason that this folder was created. But as many files will be duplicates of files that are downloaded into the new OneDrive folder, and as 80% of the files are missing from this Archive, and as it appears to be a non synching folder, I expect that at some point I'll need to delete it. It is using 70Gb of space.

NB. I thought about trying to merge my old and new OneDrive folders, to save me downloading so much data and to restore the local files that hadn't previously synched to the Cloud back to their proper place in my directory, but the behaviour of OneDrive is not transparent enough for me to know if this would work or create more problems - I might end up replacing some good working files stored in the Cloud with nonfunctioning shells files that OneDrive previously created and which appear in my back-up from OneDrive - [account name].noindex>OneDrive - [account name].

So for me the bottom line was:

Upgrading from BigSur to Monterey unexpectedly resulted in me having to restore my OneDrive folder from the cloud, and potentially loose local data that had not synched to the cloud. Fortunately, I likely do have back-ups of the non-synched local data on an external HDD; but these files (which were previously identified as having synch issues due to file names containing spaces or irregular characters) represent hundreds of files, distributed over hundreds of folders, and will now no longer be present in my active OneDrive account. As these files are scattered throughout my back-up data, its hard for to isolate them and just retain them, without retaining a full back-up of all the data. So my data is now fragmented across a new ONeDrive folder and a back-up, and in order to avoid data loss my data is duplicated. Not a good result from Monterey update / ONeDrive teams. Not sure who to blame.