Forum Discussion
OneDrive won't allow installation on fixed D: drive
Since 24 Sep 2026, OneDrive refuses to use my internal D:\ drive, even though the OneDrive build and Windows haven't changed. This applies to my Personal OneDrive and institutional OneDrive accounts.
Build 26.168.0830.0006 (per-machine install, installed 20 Sep 2026) synced both of my accounts to D:\ normally from 20 to 23 Sep. At the 24 Sep morning boot, OneDrive could not find either folder. Setup now rejects D:\ with "Your OneDrive folder can't be created in the location you selected," and Learn More links to the article on external drives.
The rejection persists with my existing folders (after renaming them) and with a brand-new empty folder (D:\ODTest). E:\, an identical Crucial T500 4TB NVMe in the motherboard's native M.2 slot, is accepted. The only difference is that D:\ is attached through an M.2-to-PCIe adapter card in an internal PCIe 4.0 slot (in place since Nov 2025).
Windows reports D:\ as Fixed and NTFS (Get-Volume, DriveInfo, Win32_DiskDrive), and it does not appear in Safely Remove Hardware. Dropbox on the same drive is unaffected. With the build unchanged and Windows Update paused, this looks like a server-side change in how OneDrive classifies drives. Please restore support for internal NVMe drives attached through PCIe adapter cards.
I hit the same refusal on 8 November and found the cause. Posting it for anyone else stuck here.
OneDrive asks Windows what kind of drive a location is on, and accepts only a fixed or removable disk. On my PC a Windows folder setting, "Local Downloads" ({7D83EE9B-2244-4E70-B1F5-5393042AF1E4}), pointed at the root of D:, and D:\ held a hidden desktop.ini for it. With that, Windows reports D:\ as a folder instead of a fixed disk, and OneDrive refuses every location on the drive with "Your OneDrive folder can't be created in the location you selected". C: was accepted throughout.
To check, run this in PowerShell (not as administrator). Any result is a Windows folder pointing at the root of a drive:
(Get-ItemProperty 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders').PSObject.Properties | Where-Object { "$($_.Value)" -match '^[A-Z]:\\?$' } | Select-Object Name, Value
To fix:
1. Point that entry at a subfolder. For example, using the name your check returned:
Set-ItemProperty 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders' -Name '{7D83EE9B-2244-4E70-B1F5-5393042AF1E4}' -Value 'D:\Downloads' -Type ExpandString
If you change it through the Downloads folder's Properties > Location instead, click No when Windows offers to move the files: the old location is the whole drive.
2. Delete the hidden desktop.ini at the root of the drive.
3. Sign out and back in, then set up OneDrive and pick the drive. Mine was accepted at once, and OneDrive is matching the existing 649 GB against the cloud without making duplicates.
The desktop.ini dated from January and OneDrive accepted the drive until 8 November, so something changed on Microsoft's side. Microsoft: OneDrive should either accept these drives again or say why it refuses them. A message naming the cause would have saved me two working days.
4 Replies
I hit the same refusal on 8 November and found the cause. Posting it for anyone else stuck here.
OneDrive asks Windows what kind of drive a location is on, and accepts only a fixed or removable disk. On my PC a Windows folder setting, "Local Downloads" ({7D83EE9B-2244-4E70-B1F5-5393042AF1E4}), pointed at the root of D:, and D:\ held a hidden desktop.ini for it. With that, Windows reports D:\ as a folder instead of a fixed disk, and OneDrive refuses every location on the drive with "Your OneDrive folder can't be created in the location you selected". C: was accepted throughout.
To check, run this in PowerShell (not as administrator). Any result is a Windows folder pointing at the root of a drive:
(Get-ItemProperty 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders').PSObject.Properties | Where-Object { "$($_.Value)" -match '^[A-Z]:\\?$' } | Select-Object Name, Value
To fix:
1. Point that entry at a subfolder. For example, using the name your check returned:
Set-ItemProperty 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders' -Name '{7D83EE9B-2244-4E70-B1F5-5393042AF1E4}' -Value 'D:\Downloads' -Type ExpandString
If you change it through the Downloads folder's Properties > Location instead, click No when Windows offers to move the files: the old location is the whole drive.
2. Delete the hidden desktop.ini at the root of the drive.
3. Sign out and back in, then set up OneDrive and pick the drive. Mine was accepted at once, and OneDrive is matching the existing 649 GB against the cloud without making duplicates.
The desktop.ini dated from January and OneDrive accepted the drive until 8 November, so something changed on Microsoft's side. Microsoft: OneDrive should either accept these drives again or say why it refuses them. A message naming the cause would have saved me two working days.
I've been having the exact same issue since Friday November 6th 2026. OneDrive suddenly on launch couldn't recognize the directory it's been installed in for years and refuses to create a new folder in the directory even with a clean install and deletion of previous data. I'm at a loss. I've tried everything Microsoft recommended online, including running a script that resets the app and deletes the dat file. I looked at disk management and it doesn't look like there's any issue, the partition is recognized still as a partition of my main drive and the error message is unhelpful and doesn't provide any more information. I'm stumped.
I'm having the same issue, too. OneDrive was running fine for over a year, and on October 3rd, 2026, OneDrive cannot access my secondary drive. There's no issue shown on Disk Management. I'm currently trying to give Full Control access on Security to Users, but it takes a long time since there are many files. This is so frustrating as my C drive is full and can't OneDrive requires alot of space.
a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; }
Based on your description, this does not appear to be a Windows or hardware issue.
The key point is that OneDrive accepted D:\ from September 20 through September 23 using the same OneDrive build and the same Windows installation, then suddenly began rejecting the location on September 24 without any reported local changes.
Since Windows correctly identifies the drive as a fixed NTFS volume and other applications (such as Dropbox) continue to use the drive normally, the behavior suggests that OneDrive may now be classifying the drive differently than before.
A few questions may help narrow this down:
- Does D:\ appear as a fixed drive in Windows Disk Management?
- Is the SSD connected through a PCIe NVMe adapter that exposes any "removable" characteristics to Windows or the storage controller driver?
- Have you checked whether the SSD manufacturer's driver or firmware was updated around the time the issue appeared?
One additional test would be to create a completely new OneDrive account configuration and attempt to select a new empty folder on D:\. Since you have already tested both existing folders and a newly created folder, and OneDrive still rejects the entire drive while accepting E:\, the issue appears to be associated with how OneDrive is evaluating the drive itself rather than the folders stored on it.
Given that E:\ (a similar NVMe SSD) is accepted while D:\ is not, I would be interested to know whether OneDrive engineering recently changed the logic used to determine which storage devices qualify as supported locations. From the information provided, it seems possible that an internal NVMe drive connected through a PCIe adapter is now being identified differently than it was previously.
If possible, please provide a screenshot of:
- Windows Disk Management
- The OneDrive error message
- Device Manager → Disk drives
That would help determine whether OneDrive is detecting the drive as removable storage even though Windows presents it as a fixed internal drive.
