Inefficient OneDrive Synchronization Causes Windows Explorer Slowdowns
OneDrive has become a significant performance bottleneck in daily Windows usage. Its synchronization process frequently consumes excessive disk resources, directly impacting Windows Explorer performance and making file browsing noticeably slow, regardless of the desktop PC's hardware specifications. What is even more concerning is that this issue has persisted for years. Many users have reported the same problem, yet the recurring response is simply that the team is "aware of the issue." Despite these acknowledgments, there have been no meaningful improvements, no clear action plan, and little transparency regarding progress or future fixes. The lack of communication and visible progress creates the impression that the user experience is not receiving the attention it deserves. For a service as important and deeply integrated into the Windows ecosystem as OneDrive, users expect greater transparency, stronger commitment, and continuous improvements to performance and reliability. At this point, OneDrive is becoming less of a practical productivity solution and more of a source of frustration for many users. We hope Microsoft will give these concerns the priority they deserve and provide a clearer roadmap for improving both the performance and overall reliability of the service. --- Sincronização ineficiente do OneDrive causa lentidão no Windows Explorer O OneDrive tem se tornado um gargalo significativo no uso diário do Windows. A sincronização frequentemente consome recursos de disco de forma excessiva, afetando diretamente o desempenho do Windows Explorer e tornando a navegação de arquivos lenta, independentemente da configuração do computador utilizado. O mais preocupante é que essa situação persiste há anos. Muitos usuários relatam o mesmo problema e, apesar das respostas recorrentes de que a equipe está "ciente da situação", não percebemos melhorias concretas, um plano de ação claro ou atualizações transparentes sobre o andamento das correções. A falta de comunicação e de avanços visíveis passa a impressão de que a experiência do usuário não está recebendo a atenção necessária. Para um serviço tão importante e amplamente integrado ao ecossistema Windows, seria fundamental haver mais transparência, comprometimento e evolução contínua da plataforma. Atualmente, o OneDrive está deixando de ser uma solução prática para muitos usuários e se tornando uma fonte constante de frustração. Esperamos que a Microsoft trate essas questões com a prioridade que merecem e forneça um posicionamento mais claro sobre os planos futuros para melhorar o desempenho e a confiabilidade do serviço.
Problem with Docusign inn
Hello, I have been using Microsoft 365 Family with Word Online and OneDrive for a long time, and the "Request Signature" feature worked perfectly until the last three months. Now, every time I click Request Signature, I receive the following error: "We couldn't connect to the ‘{0}’ catalog server for this add-in." I found your announcement about the retirement of the Legacy DocuSign for SharePoint integration, and I'm trying to determine whether this is the cause of the issue. My questions are: Is Microsoft 365 Family still supported for the Request Signature feature in Word Online? Do I need to migrate to Microsoft 365 Business to continue using this feature? If so, which Microsoft 365 Business plan do you recommend, and will my current DocuSign account continue to work after the migration? I have already cleared my browser cache, signed out and back in, and tested different browsers, but the issue persists. Thank you for your assistance.
The latest mobile apps killed mobile first when working with files
Hi, I really enjoyed working only with mobile devices when we started with M365. On iOS the OneDrive app was paramount when organising files in SharePoint/Teams Sites. Easy up- and downloads, drag‘n drop. Move and copy all was there to manage a companies files on mobile devices even when only on mobile network connections. But the upgrades that happened over the last 1-2 years completely break this kind of workflows. There is no really mobile-first paradigm visible anymore. The OneDrive app was worst. All the pretty well integration file management stuff is gone. No drag‘n drop. No useful integration into iOS Files app. Copying between OneDrive and SharePoint got a pain. Bulk operation just silently fail. Files get renamed without any warning (numbers get added to the name or are just increased so no one will ever find the file again). So just two simple usability examples that are a mess: to select multiple files in a folder you have to press the word ‚Select‘ that is not a button or something. This shows up like a column heading in the file view. Right beside ‚Name‘ and ‚Date Modified‘. Why are active user elements placed in table headings? If you browse into some SharePoint folders and quickly want to go back to your OneDrive files you either have to press the back button over and over again until your back to the top level view or you can press-hold the back button and then select ‚Files‘. Butthe latter brings you to the top level Library view and you still have to manually go to ‚Files‘. The old app design just had a top menu bar where views could easily be switched. Am I the only one who wants to work on mobile devices? Does Microsoft still expect everyone to use a laptop and run desktop apps? Annoying.
Sort by Name not proper for numbered files.
Just trying to understand the logic of OneDrive's "Sort by Name" when it comes to numbers. Take a look at the below. "9-26" shouldn't be coming before "9-3". The number 26 should be perceived as after 3. I cannot honestly say I've seen that issue with other storage services.
URGENT: Tenant Linked & New Licenses Active, Need Manual Sync Triggered (Ticket #2606160040010375)
Hello Community Managers and Microsoft Moderators, I am writing to request an urgent escalation to a Data Protection and Billing Supervisor regarding our open case: TicketID#2606160040010375 for our nonprofit, R. Fathers M.A.D., Inc. Our legacy grant subscription lapsed on May 27, and we purchased our new active subscription on June 15—a lapse of exactly 19 days. Current Status: The Data Protection Team has successfully linked our accounts. Our new June 15 subscription is confirmed Active in our Billing dashboard. All new licenses have been successfully assigned to our active users. Frontline support ran an eDiscovery search that came back empty because the metadata indexing pointers were severed during the grant decommissioning. Because we acted within the initial 30-day window, our data sits well within the 90-day retention threshold. We have completed 100% of the front-end setup steps on our end. We need a Community Manager to internally flag TicketID#2606160040010375 so a Tier-3 engineer can manually trigger the backend data re-index. This will reconnect our intact SharePoint and OneDrive files to our newly mapped user profiles. Our nonprofit operations are completely halted until this sync is pushed. Thank you for your immediate help.Making Mac OneDrive Faster and More Reliable
OneDrive on macOS is getting a major update to how it syncs! The Native Sync Engine is rolling out to Insiders today with version 26.098. It's up to 2x faster on initial sync and on-disk state changes, uses less CPU, memory, and battery, and removes the hidden cache folder that's been the source of most reliability issues since 2022. It's the latest in an ongoing effort to make OneDrive feel native on Mac. Earlier this year we shipped a redesigned Activity Center with Liquid Glass and native dialogs, and the Native Sync Engine is a major step in that journey. The cache folder problem When we moved OneDrive to Apple's File Provider platform in 2022, we needed a way to bridge the existing sync engine with how File Provider expected things to work. Broadly, there are two parts to OneDrive sync: the sync engine itself, and the code that OneDrive uses to work with files. To support File Provider, we had to change how OneDrive interacted with the file system. However, to reduce risk, we decided to use a hidden cache folder that mirrored your OneDrive contents, so the sync engine could remain largely unchanged. That cache folder solved the immediate problem and unlocked features like Known Folder Move. Over time, however, feedback and telemetry showed us that it was root cause of many of the reliability and performance issues users have reported since. The Native Sync Engine removes it. What’s changed Over the past several years, we’ve been working behind the scenes on the Native Sync Engine. Building it required us to completely rebuild large portions of our code and build a new sync platform that allows OneDrive to work better with the File Provider system. The Native Sync Engine provides the fastest, most reliable experience we’ve ever delivered on the Mac. It has a simplified architecture, eliminates entire classes of errors, and integrates more deeply with macOS. In our performance testing, the new system is about 2x faster for initial sync and on-disk state changes. It also uses fewer system resources, helping preserve your Mac’s battery life while improving overall responsiveness. We’ve also put the new system through multiple tests that simulate usage well beyond what the average user would ever do, and it has held up extremely well in those scenarios. It’s a massive improvement, and one we are very excited to bring to you. On the surface, the Native Sync Engine looks and feels very similar to what we had before, but there are a few important changes. Let’s walk through a few of them. Hidden folders no longer hold data OneDrive's hidden folders now contain metadata only. Your file data only lives in the OneDrive folder you interact with directly. There are a few cases where a copy of file data will exist in the hidden folder: Files you've created or changed that haven't uploaded yet. The copy is removed once the file has fully synced to the cloud. OneNote shortcuts and similar "link" file types. These are typically a few hundred bytes at most, and we retain them in the hidden folder indefinitely. Some kinds of macOS packages, such as GarageBand files, .app bundles, and certain older iWork files. Copies of these files are retained for longer than most files. Files and folders are always browsable Files in a folder used to be created on disk only the first time the folder was accessed. That led to Finder showing "Loading..." while you browsed and apps hanging while they waited for folders to materialize. Now, every folder and file is always browsable on disk. Navigating your OneDrive folder feels like navigating any other folder. It’s snappy, responsive, and just works. Note that Files On-Demand is unchanged with the Native Sync Engine. Files you haven't opened remain online-only unless you either open them or mark them Always On This Device. External drive support The Native Sync Engine also supports external drives, such as USB drives you can plug into your Mac. If your system and your external drive meet the requirements, all of your files and OneDrive's metadata folder will be placed on this drive. On older versions of macOS and on drives that don't meet the requirements, your files and OneDrive metadata will be stored on the home volume. Syncing shared folders and libraries If your organization has disabled the “Sync” button on SharePoint and your users are using “Add shortcut to My Files”, you can skip this section, as you are already in the ideal state! If you are still using synced libraries, each synced library now appears as its own root in the Finder sidebar, instead of nested under a single tenant entry. Add shortcut to OneDrive remains the modern way to access shared content. Admins can hide the Sync button via aka.ms/HideSyncButton. Identifying the Native Sync Engine You can identify whether your Mac is using the Native Sync Engine by inspecting the OneDrive version in the Preferences dialog: If the version ends with a value such as "(26K)", you are running the Native Sync Engine. If the version ends with the version of macOS, you are not yet running the Native Sync Engine. Rollout Starting today, we’ll be gradually rolling out this new experience to our Insiders audience. This rollout will take several weeks to complete. If you aren't already in Insiders and want to try the new update, simply open OneDrive preferences, click on the About tab, and check the box to join the Insiders program. Your Mac will upgrade to the Native Sync Engine automatically when it receives the update. It might take a couple of minutes for OneDrive to complete the upgrade, and a little while longer for File Provider to finish with the upgrade, but you can still use your OneDrive while this is taking place. We would love to hear your feedback, good or bad. Just click “Send Feedback” in the OneDrive Activity Center and share your thoughts! To learn more, watch the latest Sync Up podcast below:
one drive mapped network drive Win 10
I want to use my onedrive CID number to connect to a mapped network drive in windows explorer. But, as soon as I type my microsoft account credentials at the login prompt, it doesn't log in but just loops back to the login screen window. What should I do ? Has microsoft stopped allowing onedrive mapped network drive on windows 10 explorer ?NOW ON DEMAND | OneDrive Office Hours | June 2026
Get ready for the June OneDrive Customer Office Hours! This session creates space for open conversation around the latest updates and how they support the way you use your files every day. In this month’s session, we’ll walk through what’s new and open the floor for questions, feedback, and shared experiences.I built a free, open-source M365 security assessment tool - looking for feedback
I work as an IT consultant, and a good chunk of my time is spent assessing Microsoft 365 environments for small and mid-sized businesses. Every engagement started the same way: connect to five different PowerShell modules, run dozens of commands across Entra ID, Exchange Online, Defender, SharePoint, and Teams, manually compare each setting against CIS benchmarks, then spend hours assembling everything into a report the client could actually read. The tools that automate this either cost thousands per year, require standing up Azure infrastructure just to run, or only cover one service area. I wanted something simpler: one command that connects, assesses, and produces a client-ready deliverable. So I built it. What M365 Assess does https://github.com/Daren9m/M365-Assess is a PowerShell-based security assessment tool that runs against a Microsoft 365 tenant and produces a comprehensive set of reports. Here is what you get from a single run: 57 automated security checks aligned to the CIS Microsoft 365 Foundations Benchmark v6.0.1, covering Entra ID, Exchange Online, Defender for Office 365, SharePoint Online, and Teams 12 compliance frameworks mapped simultaneously -- every finding is cross-referenced against NIST 800-53, NIST CSF 2.0, ISO 27001:2022, SOC 2, HIPAA, PCI DSS v4.0.1, CMMC 2.0, CISA SCuBA, and DISA STIG (plus CIS profiles for E3 L1/L2 and E5 L1/L2) 20+ CSV exports covering users, mailboxes, MFA status, admin roles, conditional access policies, mail flow rules, device compliance, and more A self-contained HTML report with an executive summary, severity badges, sortable tables, and a compliance overview dashboard -- no external dependencies, fully base64-encoded, just open it in any browser or email it directly The entire assessment is read-only. It never modifies tenant settings. Only Get-* cmdlets are used. A few things I'm proud of Real-time progress in the console. As the assessment runs, you see each check complete with live status indicators and timing. No staring at a blank terminal wondering if it hung. The HTML report is a single file. Logos, backgrounds, fonts -- everything is embedded. You can email the report as an attachment and it renders perfectly. It supports dark mode (auto-detects system preference), and all tables are sortable by clicking column headers. Compliance framework mapping. This was the feature that took the most work. The compliance overview shows coverage percentages across all 12 frameworks, with drill-down to individual controls. Each finding links back to its CIS control ID and maps to every applicable framework control. Pass/Fail detail tables. Each security check shows the CIS control reference, what was checked, what the expected value is, what the actual value is, and a clear Pass/Fail/Warning status. Findings include remediation descriptions to help prioritize fixes. Quick start If you want to try it out, it takes about 5 minutes to get running: # Install prerequisites (if you don't have them already) Install-Module Microsoft.Graph, ExchangeOnlineManagement -Scope CurrentUser Clone and run git clone https://github.com/Daren9m/M365-Assess.git cd M365-Assess .\Invoke-M365Assessment.ps1 The interactive wizard walks you through selecting assessment sections, entering your tenant ID, and choosing an authentication method (interactive browser login, certificate-based, or pre-existing connections). Results land in a timestamped folder with all CSVs and the HTML report. Requires PowerShell 7.x and runs on Windows (macOS and Linux are experimental -- I would love help testing those platforms). Cloud support M365 Assess works with: Commercial (global) tenants GCC, GCC High, and DoD environments If you work in government cloud, the tool handles the different endpoint URIs automatically. What is next This is actively maintained and I have a roadmap of improvements: More automated checks -- 140 CIS v6.0.1 controls are tracked in the registry, with 57 automated today. Expanding coverage is the top priority. Remediation commands -- PowerShell snippets and portal steps for each finding, so you can fix issues directly from the report. XLSX compliance matrix -- A spreadsheet export for audit teams who need to work in Excel. Standalone report regeneration -- Re-run the report from existing CSV data without re-assessing the tenant. I would love your feedback I have been building this for my own consulting work, but I think it could be useful to the broader community. If you try it, I would genuinely appreciate hearing: What checks should I prioritize next? Which security controls matter most in your environment? What compliance frameworks are most requested by your clients or auditors? How does the report land with non-technical stakeholders? Is the executive summary useful, or does it need work? macOS/Linux users -- does it run? What breaks? I have tested it on macOS, but not extensively. Bug reports, feature requests, and contributions are all welcome on GitHub. Repository: https://github.com/Daren9m/M365-Assess License: MIT (free for commercial and personal use) Runtime: PowerShell 7.x Thanks for reading. Happy to answer any questions in the comments.
