Moving files out of unlinked, unsynced and disabled onedrive
I am out of storage space on my PC -Windows 11 and get reminders of that everyday. To help solve that problem I would like to move MyDocuments (a huge file) to Drive D. Here is the potential problem. I unlinked, unsynced and removed OneDrive in 2020, or so I thought. I still see the OneDrive symbol in Microsoft Explorer above the line from Drive C and other drives. Most of my files are accessible in Drive C, but not MyDocuments, Desktop, and some others. They can only be opened thru OneDrive. This always puzzled me, but since all my files are accessible to me, I haven't worried about it. Now I'm concerned that OneDrive still has its tentacles around some of my files. MyDocuments and Desktop are being updated, but my files in the cloud are seriously out of date. What does that tell me? If they are still tied to OneDrive somehow, does that complicate the removal of those files to Drive D?
Windows Crash During NVMe Over TCP Disk Disconnect
While evaluating the Windows NVMe Initiator, we have observed that disconnecting an NVMe disk frequently results in a Windows system crash. This occurs during the disconnect operation and appears to be reproducible in our test environment. Questions: Has anyone else encountered similar behavior? Are there any known issues related to NVMe/TCP disconnect handling? Are there recommended troubleshooting steps, logs, or diagnostics that we should collect to help identify the root cause? Any insights would be greatly appreciated.Multiple Namespace Detection in Windows NVMe Over TCP Initiator
We are evaluating the Windows NVMe Initiator and have observed an issue with namespace handling. Our NVMe subsystem contains multiple namespaces. When we connect to the subsystem over TCP and establish connections to all namespaces, they are all shown as connected under the controller. However, only one namespace (shared block device) is exposed and accessible within Windows. Based on our testing, it appears that the initiator may be mapping only the first namespace associated with a given Friendly Name. We were able to connect another subsystem, whose friendly name was different. Questions: Is support for multiple namespaces within a single subsystem currently available in the Windows NVMe Initiator? If so, are there any configuration requirements or known limitations related to namespace discovery and mapping? Is the initiator expected to expose all connected namespaces as separate disks within Windows? We would appreciate any guidance or clarification on the expected behavior.
Storage full but only 1% used
I am not an IT high knowledge. Can use programs but don't always understand how tings work. I have onedrive with 1TB storage. I am wanting to use the account for backup of my files on laptop. When I look at Manage my storage it says 1% in use but when I try to place folders/files onto onedrive it says not enough space. I cannot understand this. I've tried emptying the recycling bin but cannot seem to be able to delete anything - either in one go or individual files. Instructions say "Delete in Navigation Bar" but not on my screen! Can anyone help me please?
OneDrive sync causes workflow inefficiencies and UX issues in Microsoft 365 and File Explorer
I would like to describe some workflow issues caused by the current integration between OneDrive, Windows, File Explorer, and Microsoft 365 apps. I understand that OneDrive is designed to synchronize files across devices, but in some scenarios the current behavior creates unnecessary delays, especially with slow internet connections or large synchronization queues. 1. Exported Microsoft 365 files are not immediately available in the selected OneDrive folder When exporting a Microsoft 365 file, for example exporting a Word, Excel, or PowerPoint document to PDF, the user can select a OneDrive-synced folder as the destination. However, the exported file is not always immediately visible or accessible in that folder through Windows File Explorer. From the user’s perspective, it seems that the file is first saved into a temporary or internal Microsoft 365/OneDrive staging location, then uploaded to OneDrive, and only later appears in the actual synced folder through the normal synchronization process. The issue is not that the file is never stored locally, but that it is not immediately available in the location explicitly selected by the user. This creates practical problems. After exporting a PDF, I may need to quickly locate it in File Explorer to copy it elsewhere, attach it, upload it to another platform, or use it in a web tool to merge it with other PDFs. However, even though I selected a OneDrive folder as the destination, the file may not be available there right away. A related issue is that Microsoft 365 or Windows may open the exported file through a browser or web link instead of opening the local file directly. This can trigger login prompts, open the web version of Office, and interrupt the expected desktop workflow. Expected behavior: When saving or exporting a file to a OneDrive-synced folder, the file should become immediately visible and accessible in the selected folder in File Explorer, while OneDrive continues uploading or syncing it in the background. If the user selected a local OneDrive path, Microsoft 365 should prioritize the local file workflow and avoid redirecting to the browser unless explicitly requested. 2. File duplication inside OneDrive should use both cloud-side copy and local optimization Another issue occurs when duplicating or copying a file that is already stored in OneDrive, especially within the same OneDrive account. Currently, the process may behave like a traditional local copy: the file is downloaded if needed, copied locally, and then uploaded again as a new file. This is inefficient when OneDrive already has the source file in the cloud and the operation is simply a copy within the same account. Ideally, OneDrive should combine two optimizations: Perform a cloud-side copy when possible, so the duplicated file appears quickly in OneDrive online and on other devices. Reuse the local cache when available, so the current device does not unnecessarily download and re-upload the same data. This would make copied files appear faster on other devices as online-only placeholders, ready to be downloaded later if the user opens them or marks them as available offline. The other device should not have to wait for the first computer to download, copy, re-upload, and then synchronize the change. Expected behavior: When copying or duplicating a OneDrive file within the same account, OneDrive should use a cloud-side copy whenever possible, while also reusing local data when available. The copied file should appear quickly across devices as an online-available item, without forcing a redundant download, local copy, upload, and synchronization cycle. 3. OneDrive does not dynamically prioritize files the user needs immediately A third issue appears when OneDrive has a large backlog of pending synchronization changes, especially after using another computer. In this situation, OneDrive seems to follow its own synchronization order, even if the user opens a specific folder or tries to access a specific file urgently. For example, if there are hundreds or thousands of pending changes, and I need one specific document, that file may remain unavailable until OneDrive reaches it in the queue. Even when I navigate directly to the folder or attempt to open the file, OneDrive does not seem to move that item to the top of the sync priority. Expected behavior: OneDrive should dynamically adjust synchronization priority based on user activity. If the user opens a folder, selects a file, or attempts to open a cloud-only item, that file and its immediate dependencies should be prioritized over the general sync queue. Summary of requested improvements I believe these issues could be improved with smarter local and cloud prioritization: Exported or saved files should become immediately visible in the OneDrive folder selected by the user. Microsoft 365 should avoid opening exported files through a browser when the local file workflow is expected. Copying files within the same OneDrive account should use cloud-side copy operations when possible. Local file data should be reused to avoid unnecessary download and upload cycles. Copied files should appear quickly on other devices as online-available placeholders. OneDrive should prioritize files and folders the user is actively trying to access. Is this behavior expected, or are there settings to make OneDrive prioritize local file availability, cloud-side copy operations, and currently accessed files more intelligently?
onedrive sync issues
Hi We use OneDrive for Business and need a solution for sharing files and folders among a team while maintaining proper access permissions. Currently, each team member's Desktop and Documents folders are synced with their own personal OneDrive for Business account. In addition, we have a separate common OneDrive account that has been added to all team members' PCs, and all team members have Owner permissions on that account. When a user creates a folder or saves a file in the shared OneDrive location, it is actually being created under the common OneDrive account, not in the user's personal OneDrive. While this allows everyone to access the same files, we frequently experience synchronization conflicts and sync issues between users. What is the Microsoft-recommended approach for this type of collaboration? Is using a common OneDrive account with multiple owners a supported best practice, or should we instead use a SharePoint document library (or another Microsoft 365 solution) for shared team files, permissions, and reliable synchronization? Thanks
Write to workgroup fileserver from AzureAD joined device.
Hi, We currently have a situation where we are trying to install a program locally, but we want some of the data files (master data for projects, company settings for the most part) to be stored on a fileserver. The installer allows for this change to set UNC path to the share manually, and in our case recommends doing that. The problem we are facing occurs when trying to go on with the installation, the problem reports back that write-protection is enabled. I have the share mapped as a nettwork station, and can create folders/files through explorer. But I think the issue here is that the share mapped using the "Connect with different credential" option, which is required since the share is on a server in a workgroup and the client I'm using is joined to AzureAD. And when i run the installer for the program it is ofcourse ran with my azure user (local administrator), and I guess it tries to write to the UNC path with that user ofcourse. Is there any way i can let the program write to the share without it being to much of a security risk? The same program also has a nettwork license installed on a different workgroup server. I also had to add local users to that server and do some DCOM permission tweaking for that to work. For the license part i can authenticate with the local server user, but thats not an option when trying to install with UNC path for the file/folder structure.