OneDrive says tnot enough cloud space and asks me to free up space, but there are enough space.
Once I click on the "Free up Space" option, it just shows that I have enough space. I opened a ticket since 11/6 and heard nothing since.Same thing from my phone. The ticket was assigned to an agent on 11/7. No one responded. It has been 11 days since I asked for tech support. The problem persisted more than two weeks. Not even sure how I could get ahold of a human. Is my only option to cancel OneDrive and switch to NAS?
Move files from Account A to Account B 165 GB data
I’ve been using Microsoft Office 365 Family for several years, sharing it with my family members. We have 6 accounts, each with 1 TB of storage. One of my accounts has now reached 985 GB, so I need to transfer files from Account A (my account) to Account B (my wife’s account). These files mainly consist of photos and videos — over 200,000 files in total. I tried transferring a 6 GB wedding shoot (.ISO format), but it took more than an hour. Re-downloading and uploading all the data isn’t feasible as my internet connectivity is limited to 100 mbps only. I’m looking for the best and most efficient way to move these files directly between OneDrive accounts.
Add option to change priority of file sync in the OneDrive app
There is no way to prioritise the download or upload of individual files in OneDrive. This is in contrast to Dropbox which has robust prioritisation features. Where this becomes an issue is if you want to download some files as a priority to allow you to continue work. This lacking feature is especially noticeable if you want to download/upload large files, but need smaller files to download/upload to continue working. It's features like this, and the lack of being able to cancel a download of an individual file that makes OneDrive feel half baked, dare I say, amature.OneDrive for MacOS is Unsuitable for Professional Work
I work for a large wholesaler with 300+ employees. Our two marketing departments of around 35 people are on MacOS while the rest of the business is on Windows 10. We've been assessing different tools to migrate off our physical shared drive to get the entire business working on the cloud. We currently have a SharePoint installation and the teams will be trained to use the OneDrive sync client. However, multiple deficiencies in the MacOS version of the OneDrive sync client are causing us to reconsider our SharePoint/Microsoft implementation. I don't have to share these, but I think it's in Microsoft's best interest to take note of these deficiencies: Downloads started by clicking the cloud icon in Finder cannot be cancelled. We've had multiple instances of users accidentally clicking this icon when selecting the folder and then starting a download for an entire Lifestyle image folder containing hundreds of GB of TIFFs. The only way to rectify this as far as we can tell is to uninstall OneDrive and reinstall it. Not ideal, especially when downloads should be able to be cancelled. In our opinion, a basic necessity for a cloud sync app. There’s no way to prioritise uploads and downloads, meaning if you have lots to upload, you have difficulty downloading working files for other projects. It also means you can't prioritise the upload of critical elements that need to be shared on deadlines etc. It takes up to 10 minutes just to start uploading even just a 1MB file. OneDrive sync client will be stuck on ‘Processing Changes’ or ‘Preparing to Upload’. Not sure if this is a glitch/bug? Seems consistent across all devices. The OneDrive folder cannot be moved, meaning it’s stuck in the ‘Users’ folder in MacOS. This means that any linked files in our design teams working files (InDesign, Illustrator, After Effects etc) will be broken. Microsoft have stated that this is an OS restriction (might be the case?), however I know that other cloud sync services such as Dropbox/Google Drive can be moved without issue. Furthermore, when setting a unique folder in the OneDrive sync app, there's no error or notice that it doesn't work. When you select a unique folder for OneDrive, it seemingly works without issue, but it's not until later if you go searching for that folder that you'll realise that OneDrive is in it's default location. Finder search/spotlight doesn’t work for OneDrive files unless you’ve visited that folder already. Would love to have a discussion on the above points. Cheers.Add option to cancel download of individual files in the OneDrive App
Once a download starts in OneDrive on desktop, there is no way to stop it. This is a huge issue for anyone dealing with working files that link to multiple files. Files should be able to be cancelled on an individual basis. An example of when this lacking feature becomes a problem is if you open a Premiere Pro project that links to multiple videos, these videos will start downloading. If you then close the Premiere Pro project, the files linked within the project will still download. These may be many gigabytes worth of files. Other reasons why you might want to cancel a download: You may no longer need the file to be downloaded You may realise that your internet connection is too slow for the download but still need to download smaller files to continue working
OneDrive Storage Actual Limit
I have recently come across a weird issue. I am from India and I have a OneDrive storage paid subscription for 50GB data which is running since last 2 years without any issues. 2 days back My OneDrive stopped syncing, uploading and saving the files. A red cross was also appearing over the OneDrive icon. Every time I tried saving or uploading file, it was saying storage is full. But When I checked the storage status -it showed 29.7GB (59%) used and about 21GB (41%) is free. How is it possible? Initially I thought its an issue related to my OneDrive application in the Laptop. I unlinked the OneDrive, reset it, Uninstalled and re-installed it. But still the same. I tried uploading file from my android phone OneDrive- again its the same result. I tried through Web Browser -its the same message- storage full, but still showing 41% free. Then I logged a ticket with Microsoft support team. They checked it but could not resolve it. They escalated the case to the OneDrive team- but I am yet to get a call or any support from them. I waited for 2 days, still no call from OneDrive. But since all my working files are saved in cloud only, I was unable to work on files and time was running out. So today I logged in and did a tweak. I deleted few unnecessary files from my storage and almost freed up about 5GB storage space. So now the total used space gone down to 24.5GB. And guess what- the OneDrive started working absolutely fine. Now the question is- then what is the actual storage limit? Is it actually maximum 30GB in a 50GB plan? Or else what could be the reason for this unknown issue? I am still waiting for a support from the Microsoft team, but anyone here can possibly throw some light on this? Thanks.
OneDrive Personal not downloading
Hello, I am trying to download several large files from OneDrive and it is either stopping or taking a long long time. I reduced the number of files to download to my desktop and it is still stuck here: Google photos is so much faster! what is going on? I do use a vpn, the same one Google photos is using, no issues. Thanks, V
OneDrive: High SSD I/O Since Mar 2025 Update, mklink /j Junctions Suspected
Bug Report: Suspected NTFS Junction (mklink /j) Interaction Causing Excessive OneDrive SSD Read/Write Activity on My System Since March 2025, Potentially Linked to Recent OneDrive Update Date: June 2, 2025 Product: Microsoft OneDrive Operating System: Edition: Windows 10 Pro for Workstations Version: 22H2 OS Build: 19045.5917 Installed on: 2024/9/24 Experience Pack: Windows Feature Experience Pack 1000.19061.1000.0 Summary: Since approximately March 3rd/4th, 2025, OneDrive has been causing an extremely high and sustained level of read/write activity on my system's SSD. Notably, I have been utilizing the same configuration, including Git repositories within OneDrive and NTFS junction points (mklink /j), since October 2024 without any such issues. This abrupt change in behavior starting March 2025 strongly suggests that a recent OneDrive update may have introduced a regression or altered its handling of these elements on my system, leading to the current problem. This behavior is significantly impacting my SSD's health and potentially my system's performance. Date First Observed: The issue began noticeably on my system around March 3rd, 2025, with a sharp increase in disk write commands observed from March 4th, 2025, onwards, as evidenced by the "Host Write Commands" graph (see attached picture 1). Problem Description: On my system, OneDrive.exe consistently exhibits high I/O read and write byte counts, leading to excessive disk activity. This is evident from: The long-term graph of "Host Write Commands" (picture 1), which shows a dramatic and sustained increase starting in early March 2025, rising from approximately 3,500,000,000 to over 12,000,000,000 by late May 2025 on my system. Process monitoring tools (picture 3) show OneDrive.exe with significantly higher "I/O Read Bytes" and "I/O Write Bytes" compared to other active processes on my system. For example, OneDrive.exe shows I/O Read Bytes in the hundreds of millions and I/O Write Bytes in the hundreds of millions, far exceeding other applications. Resource Monitor details (picture 2) confirm OneDrive.exe as the process with high disk activity on my system, specifically reading and writing to its operational database files such as SyncEngineDatabase.db-wal and SyncEngineDatabase.db. The screenshot shows these files located at H:\OneDriveINTEL\OneDrive\Settings\Business1\, which is where I have relocated my OneDrive cache or settings using mklink /j. (It is important to note that this relocation is not believed to be related to the cause of the excessive I/O from OneDrive; rather, I performed this relocation because my primary C: drive was already subject to frequent writes and its lifespan was a concern. The excessive I/O from OneDrive simply followed the cache to its new location on drive H:.) Potential Contributing Factors to Observed Behavior on My System: Use of NTFS Junction Points (mklink /j): I utilize mklink /j in conjunction with OneDrive. This involves junction points within my OneDrive folder pointing to other locations, and I also used it as a troubleshooting step (relocating OneDrive's cache, as mentioned above). This is a primary suspected trigger for the excessive I/O. (See "Additional Context Regarding mklink /j Usage" below for specifics). Use of Git Repositories: I store and manage Git repositories within OneDrive-synced folders. The frequent small file changes typical of Git operations might be triggering excessive sync activity, possibly exacerbated by the interaction with junctions. Troubleshooting Steps I Have Already Taken: I identified OneDrive as the primary source of high disk I/O using system monitoring tools. I relocated my OneDrive local cache/settings folder (typically C:\Users\[Username]\AppData\Local\Microsoft\OneDrive) to a different physical drive (Drive H:, path appears to be H:\OneDriveINTEL\) using mklink /j, as detailed in the Problem Description. Despite this relocation, the excessive I/O pattern persists on the drive now hosting these OneDrive operational files. I attempted to reset OneDrive settings and functionality. I performed a full reinstallation of the OneDrive application. Neither resetting nor reinstalling OneDrive resolved the excessive disk I/O issue on my system. I can confirm I have used Git repositories within OneDrive folders and mklink /j for other purposes within my OneDrive setup since October 2024; the problem only manifested in March 2025. Additional Context Regarding mklink /j Usage: It is important to clarify that my use of NTFS junctions (mklink /j) differs from some scenarios discussed in public forums (e.g., the Microsoft Answers thread at https://answers.microsoft.com/en-us/msoffice/forum/all/solved-onedrive-constantly-writing-to-disk-to-the/68958911-1161-4c5e-b920-dee7e55bc0ac). In my case, the junctions are created between locations that reside on the same hard drive. For instance, a typical mklink /j command I use creates a junction within one of my OneDrive-synced folder structures that points to another directory also located on the C: drive. An anonymized example reflecting my usage pattern is: mklink /J "C:\Path\To\My_OneDrive_Business_Account\MainSyncFolder\ProjectX_Vault\Subfolder_A\Notes_Junction" "C:\Another\Local_Path_SameDrive\ProjectX_SourceData\RawNotes_Target" This type of same-drive junction configuration, where the junction link is inside a OneDrive folder and the target is elsewhere on the same drive, was part of my stable setup from October 2024 until the onset of the excessive disk I/O issue in March 2025. Expected Result: OneDrive should synchronize files and perform background operations with reasonable disk I/O that does not lead to constant, excessive read/write activity, especially when my system is idle or with minor changes. Disk activity should not be at a level that significantly impacts SSD lifespan or system responsiveness, even when NTFS junctions (including same-drive junctions as described) are part of the configuration. Actual Result: OneDrive is causing continuous and abnormally high SSD read/write operations on my system, as detailed by the attached screenshots. This has been ongoing since early March 2025, and I strongly suspect it to be related to its handling of NTFS junctions as configured on my system. Impact on My System: Potential reduction in SSD lifespan due to excessive writes (this was already a concern for my C: drive, prompting the cache relocation, and is now a concern for drive H: due to OneDrive's behavior). Possible degradation of overall system performance and responsiveness. Concern over data integrity and system stability. Attachments: picture 1: Graph from my system showing "Host Write Commands (FF_1250)" over time, illustrating the sharp increase in writes since March 2025. picture 3: Screenshot from a process monitoring tool on my system (similar to Process Explorer) showing high I/O activity for OneDrive.exe. picture 2: Screenshot from Resource Monitor on my system (or similar, in Chinese) showing disk activity by process, with OneDrive.exe prominently active and detailing file access to its database files on drive H:. Request: I request an investigation into why OneDrive, particularly after a potential update or change around March 2025, began exhibiting this excessive disk I/O behavior on my system. I ask for a strong focus on its interaction with NTFS junctions (mklink /j), especially same-drive junctions as detailed in my "Additional Context" section, and particularly in environments also using Git. This configuration worked without issue for me from October 2024 to early March 2025. Guidance on how to mitigate this issue or information on a forthcoming fix would be greatly appreciated. Picture 1 Picture 2 Picture 3OneDrive: High SSD I/O Since Mar 2025 Update, mklink /j Junctions Suspected
Bug Report: Suspected NTFS Junction (mklink /j) Interaction Causing Excessive OneDrive SSD Read/Write Activity on My System Since March 2025, Potentially Linked to Recent OneDrive Update Date: June 2, 2025 Product: Microsoft OneDrive Operating System: Edition: Windows 10 Pro for Workstations Version: 22H2 OS Build: 19045.5917 Installed on: 2024/9/24 Experience Pack: Windows Feature Experience Pack 1000.19061.1000.0 Summary: Since approximately March 3rd/4th, 2025, OneDrive has been causing an extremely high and sustained level of read/write activity on my system's SSD. Notably, I have been utilizing the same configuration, including Git repositories within OneDrive and NTFS junction points (mklink /j), since October 2024 without any such issues. This abrupt change in behavior starting March 2025 strongly suggests that a recent OneDrive update may have introduced a regression or altered its handling of these elements on my system, leading to the current problem. This behavior is significantly impacting my SSD's health and potentially my system's performance. Date First Observed: The issue began noticeably on my system around March 3rd, 2025, with a sharp increase in disk write commands observed from March 4th, 2025, onwards, as evidenced by the "Host Write Commands" graph (see attached picture 1). Problem Description: On my system, OneDrive.exe consistently exhibits high I/O read and write byte counts, leading to excessive disk activity. This is evident from: The long-term graph of "Host Write Commands" (picture 1), which shows a dramatic and sustained increase starting in early March 2025, rising from approximately 3,500,000,000 to over 12,000,000,000 by late May 2025 on my system. Process monitoring tools (picture 3) show OneDrive.exe with significantly higher "I/O Read Bytes" and "I/O Write Bytes" compared to other active processes on my system. For example, OneDrive.exe shows I/O Read Bytes in the hundreds of millions and I/O Write Bytes in the hundreds of millions, far exceeding other applications. Resource Monitor details (picture 2) confirm OneDrive.exe as the process with high disk activity on my system, specifically reading and writing to its operational database files such as SyncEngineDatabase.db-wal and SyncEngineDatabase.db. The screenshot shows these files located at H:\OneDriveINTEL\OneDrive\Settings\Business1\, which is where I have relocated my OneDrive cache or settings using mklink /j. (It is important to note that this relocation is not believed to be related to the cause of the excessive I/O from OneDrive; rather, I performed this relocation because my primary C: drive was already subject to frequent writes and its lifespan was a concern. The excessive I/O from OneDrive simply followed the cache to its new location on drive H:.) Potential Contributing Factors to Observed Behavior on My System: Use of NTFS Junction Points (mklink /j): I utilize mklink /j in conjunction with OneDrive. This involves junction points within my OneDrive folder pointing to other locations, and I also used it as a troubleshooting step (relocating OneDrive's cache, as mentioned above). This is a primary suspected trigger for the excessive I/O. (See "Additional Context Regarding mklink /j Usage" below for specifics). Use of Git Repositories: I store and manage Git repositories within OneDrive-synced folders. The frequent small file changes typical of Git operations might be triggering excessive sync activity, possibly exacerbated by the interaction with junctions. Troubleshooting Steps I Have Already Taken: I identified OneDrive as the primary source of high disk I/O using system monitoring tools. I relocated my OneDrive local cache/settings folder (typically C:\Users\[Username]\AppData\Local\Microsoft\OneDrive) to a different physical drive (Drive H:, path appears to be H:\OneDriveINTEL\) using mklink /j, as detailed in the Problem Description. Despite this relocation, the excessive I/O pattern persists on the drive now hosting these OneDrive operational files. I attempted to reset OneDrive settings and functionality. I performed a full reinstallation of the OneDrive application. Neither resetting nor reinstalling OneDrive resolved the excessive disk I/O issue on my system. I can confirm I have used Git repositories within OneDrive folders and mklink /j for other purposes within my OneDrive setup since October 2024; the problem only manifested in March 2025. Additional Context Regarding mklink /j Usage: It is important to clarify that my use of NTFS junctions (mklink /j) differs from some scenarios discussed in public forums (e.g., the Microsoft Answers thread at https://answers.microsoft.com/en-us/msoffice/forum/all/solved-onedrive-constantly-writing-to-disk-to-the/68958911-1161-4c5e-b920-dee7e55bc0ac). In my case, the junctions are created between locations that reside on the same hard drive. For instance, a typical mklink /j command I use creates a junction within one of my OneDrive-synced folder structures that points to another directory also located on the C: drive. An anonymized example reflecting my usage pattern is: mklink /J "C:\Path\To\My_OneDrive_Business_Account\MainSyncFolder\ProjectX_Vault\Subfolder_A\Notes_Junction" "C:\Another\Local_Path_SameDrive\ProjectX_SourceData\RawNotes_Target" This type of same-drive junction configuration, where the junction link is inside a OneDrive folder and the target is elsewhere on the same drive, was part of my stable setup from October 2024 until the onset of the excessive disk I/O issue in March 2025. Expected Result: OneDrive should synchronize files and perform background operations with reasonable disk I/O that does not lead to constant, excessive read/write activity, especially when my system is idle or with minor changes. Disk activity should not be at a level that significantly impacts SSD lifespan or system responsiveness, even when NTFS junctions (including same-drive junctions as described) are part of the configuration. Actual Result: OneDrive is causing continuous and abnormally high SSD read/write operations on my system, as detailed by the attached screenshots. This has been ongoing since early March 2025, and I strongly suspect it to be related to its handling of NTFS junctions as configured on my system. Impact on My System: Potential reduction in SSD lifespan due to excessive writes (this was already a concern for my C: drive, prompting the cache relocation, and is now a concern for drive H: due to OneDrive's behavior). Possible degradation of overall system performance and responsiveness. Concern over data integrity and system stability. Attachments: picture 1: Graph from my system showing "Host Write Commands (FF_1250)" over time, illustrating the sharp increase in writes since March 2025. picture 3: Screenshot from a process monitoring tool on my system (similar to Process Explorer) showing high I/O activity for OneDrive.exe. picture 2: Screenshot from Resource Monitor on my system (or similar, in Chinese) showing disk activity by process, with OneDrive.exe prominently active and detailing file access to its database files on drive H:. Request: I request an investigation into why OneDrive, particularly after a potential update or change around March 2025, began exhibiting this excessive disk I/O behavior on my system. I ask for a strong focus on its interaction with NTFS junctions (mklink /j), especially same-drive junctions as detailed in my "Additional Context" section, and particularly in environments also using Git. This configuration worked without issue for me from October 2024 to early March 2025. Guidance on how to mitigate this issue or information on a forthcoming fix would be greatly appreciated. Picture 1 Picture 2 Picture 3
