After upgrading to Monterey MS Onedrive folder got inside iCloud

I am currently experiencing a similar issue but with BOX which is also showing as an unknown sized lego brick within the Library/Cloustrorage folder but the main "Cloudstorage" folder reads as 155gigs which is about the same size as the BOX Cache folder located within Application Support/Box/Box/cache together they two directories are consuming close to 60% of my MacBook Pro (16-inch, 2019) internal drive.

I have been troubleshooting various BOX app issues since April of 2021 and each new update has fixed a previous problem but presented a new one in its place. I will try the method you outlined that resolved your issue with the hopes I can reclaim some scratch drive to operate within.

hi there, I also have the same issue here like I see both iCloud and OneDrive status icons next to my files / folders, and I want to get rid of the '-"iCloud" icons, as I only want to work with OneDrive ...

Is there finally a solution to the issue ?

In the past I saw a kind of blue circle with a white V inside, now I see this kind of icons :

I have disabled iCloud, and I see / think that my OneDrive still syncs data, but I feel like although the disk space shows like my files are online, they are actually not because I see this small cloud icon mentioning "still to download" or something like that ...

What is the current status now ?

Many Thanks !!

An oddball observation: Windows/Parallels on my iMac displayed the correct OD icons and could open files in MacOS. 🙃

How do you exactly execute steps 3 and 4 (what commands to you use in the terminal and under which dir ?

Many thanks !

Got the same recently, don't know if I changes anything at all... Did you use Clean My Mac? Have the impression that messed it up a bit...

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.

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.

I am experiencing the same problems with this new OneDrive vs Monterey mess. Honestly, it is an utter disaster and I cannot believe Microsoft has released this massive change without the (clearly missing) extensive testing.

I have opened a ticket with Microsoft, as follows:

OneDrive on Mac OS 11 Monterey is saying all my files are in the cloud, even though they are all (~200GB of them) local and consuming disk space. Even for a file that is visibly local in the onedrive.noindex folder deep inside ~/Library, it still goes to the cloud to fetch it before its app will open it. What is going on?

In addition, deleting a file in the Onedrive folder in finder no longer sends the file to the Mac finder bin. Instead, it now says the file will be permanently deleted, and if I want to get it back, I need to go to the OneDrive recycle bin in the cloud. Why are you breaking standard file management processes in the Mac with this latest version of OneDrive?

Also, actual storage seems to be duplicated. Finder says my 2TB disk has 1.18TB available, and approximately 850GB used. The “Disk Inventory X” app agrees, and says 853GB used by the “Users” folder:

OneDrive in the Cloud is using 220GB:

On my disk, OneDrive is consuming double this - 225GB + 215GB - in two different folders in ~/Library (these appear to be a duplicate). From other posts above, I realise one is supposed to be an alias of the other, but from a disk space perspective, both Finder and the 3rd party Disk Inventory X app both show that OneDrive is doubling up on the actual storage consumption here (and STILL thinks the file isn't local - see further below):

Why is Onedrive doubling up on my Disk?

The apparent doubling up of disk space is not the only problem. Another major problem - OneDrive and/or Finder thinks the files are not local, and won’t let me quick-view them - however, they ARE local in the ~/Library/…/OneDrive.noindex/… folder!

None of the files in the OneDrive folder in the above screenshot on left can be quick-viewed (hitting space bar) as OneDrive and/or Finder thinks the files are not local. Double-clicking a file causes that file to download from the cloud before opening in the image viewer.

However (see above screenshot on the right), these files in ths folder ARE ALL ALREADY ON MY DISK, here in the "OneDrive.noindex" folder in ~/Library. In this folder, these image files can all be quick-viewed - as they are already local!

So, why does OneDrive think it doesn't have a local sync copy of these files? They ARE local and are consuming disk space.

Having encounter similar issues with OneDrive since the MacOS Monterey upgrade last week, I have been reading this thread with interest. I am now finding that the files that I edit and save, are sometimes not being synched to OneDrive cloud, and I get error message that file is "unavailable" when I try to open in Finder.

Fortunately, I make regular backups of my files to an external hard drive, including everything on OneDrive, so I have only have lost some recent files. While it is possible that deleting OneDrive install and reinstalling on my Mac will fix the problem, I have decided that I cannot rely on OneDrive if Microsoft cannot manage an upgrade to the MacOS any better than this. I am now researching the best alternate cloud and file synching service to work with both Mac and Windows.