How does OneDrive make its folder not functional for older Windows versions?
Clash Royale CLAN TAG#URR8PPP
After the Fall 2017 Creators Update for Windows 10 OneDrive folder can not be accessed using prior Windows versions. This oddity is described at the official site:
If you have installed the Fall 2017 Creators Update for Windows 10 and you sync OneDrive files to an external drive, you may be unable to open your OneDrive files if you move the external drive to a computer running an operating system older than Fall 2017 Creators Update for Windows 10.
The suggested workaround is "Use a computer running the Fall 2017 Creators Update for Windows 10 (or newer) to open the content".
I've successfully reproduced the issue with Windows 7 by plugging in a hard drive with a OneDrive folder, created using Windows 10 earlier. Now, when I'm trying to do something with the directory (delete it, or cd into it), I get an error:
The file cannot be accessed by the system.
There are no logical errors in the FS according to chkdsk, also I am the owner of the folder and have all the security privileges. No processes are using the volume. Regardless, I can't do anything with this (and only) folder. What is the blocking mechanism?
windows windows-10 ntfs onedrive
edited Feb 4 at 20:04
JakeGould
31.5k1096138
asked Feb 4 at 19:10
enkryptorenkryptor
435410
add a comment |
After the Fall 2017 Creators Update for Windows 10 OneDrive folder can not be accessed using prior Windows versions. This oddity is described at the official site:
If you have installed the Fall 2017 Creators Update for Windows 10 and you sync OneDrive files to an external drive, you may be unable to open your OneDrive files if you move the external drive to a computer running an operating system older than Fall 2017 Creators Update for Windows 10.
The suggested workaround is "Use a computer running the Fall 2017 Creators Update for Windows 10 (or newer) to open the content".
I've successfully reproduced the issue with Windows 7 by plugging in a hard drive with a OneDrive folder, created using Windows 10 earlier. Now, when I'm trying to do something with the directory (delete it, or cd into it), I get an error:
The file cannot be accessed by the system.
There are no logical errors in the FS according to chkdsk, also I am the owner of the folder and have all the security privileges. No processes are using the volume. Regardless, I can't do anything with this (and only) folder. What is the blocking mechanism?
windows windows-10 ntfs onedrive
edited Feb 4 at 20:04
JakeGould
31.5k1096138
asked Feb 4 at 19:10
enkryptorenkryptor
435410
add a comment |
After the Fall 2017 Creators Update for Windows 10 OneDrive folder can not be accessed using prior Windows versions. This oddity is described at the official site:
If you have installed the Fall 2017 Creators Update for Windows 10 and you sync OneDrive files to an external drive, you may be unable to open your OneDrive files if you move the external drive to a computer running an operating system older than Fall 2017 Creators Update for Windows 10.
The suggested workaround is "Use a computer running the Fall 2017 Creators Update for Windows 10 (or newer) to open the content".
I've successfully reproduced the issue with Windows 7 by plugging in a hard drive with a OneDrive folder, created using Windows 10 earlier. Now, when I'm trying to do something with the directory (delete it, or cd into it), I get an error:
The file cannot be accessed by the system.
There are no logical errors in the FS according to chkdsk, also I am the owner of the folder and have all the security privileges. No processes are using the volume. Regardless, I can't do anything with this (and only) folder. What is the blocking mechanism?
windows windows-10 ntfs onedrive
edited Feb 4 at 20:04
JakeGould
31.5k1096138
asked Feb 4 at 19:10
enkryptorenkryptor
435410
After the Fall 2017 Creators Update for Windows 10 OneDrive folder can not be accessed using prior Windows versions. This oddity is described at the official site:
If you have installed the Fall 2017 Creators Update for Windows 10 and you sync OneDrive files to an external drive, you may be unable to open your OneDrive files if you move the external drive to a computer running an operating system older than Fall 2017 Creators Update for Windows 10.
The suggested workaround is "Use a computer running the Fall 2017 Creators Update for Windows 10 (or newer) to open the content".
I've successfully reproduced the issue with Windows 7 by plugging in a hard drive with a OneDrive folder, created using Windows 10 earlier. Now, when I'm trying to do something with the directory (delete it, or cd into it), I get an error:
The file cannot be accessed by the system.
There are no logical errors in the FS according to chkdsk, also I am the owner of the folder and have all the security privileges. No processes are using the volume. Regardless, I can't do anything with this (and only) folder. What is the blocking mechanism?
windows windows-10 ntfs onedrive
windows windows-10 ntfs onedrive
edited Feb 4 at 20:04
JakeGould
31.5k1096138
asked Feb 4 at 19:10
enkryptorenkryptor
435410
edited Feb 4 at 20:04
JakeGould
31.5k1096138
asked Feb 4 at 19:10
enkryptorenkryptor
435410
edited Feb 4 at 20:04
JakeGould
31.5k1096138
edited Feb 4 at 20:04
JakeGould
31.5k1096138
edited Feb 4 at 20:04
JakeGould
31.5k1096138
31.5k1096138
asked Feb 4 at 19:10
enkryptorenkryptor
435410
asked Feb 4 at 19:10
enkryptorenkryptor
435410
asked Feb 4 at 19:10
enkryptorenkryptor
435410
435410
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
NTFS has a feature called reparse points, in which a file or directory can be tagged for special processing by the operating system. It's used to implement quite a few features – e.g. volume mount points (the Unix-ish alternative to drive letters); junctions and symlinks; GitVFS sparse directories; files that are actually stored inside a WIM image; files that have been offloaded to tape or other slow storage; and so on.
Recent versions of OneDrive also use reparse points to implement "online files" – they're placeholders at first, but downloaded on demand. Earlier versions did this at shell level, which didn't work with many programs; using a reparse point and moving the auto-downloading into the core OS makes them almost indistinguishable from local files.
Naturally new tags will result in an error when the path is accessed through an older OS; the NTFS driver doesn't know what to do with such items, so it just rejects the access. It could show e.g. an empty directory, but that could quickly result in more damage when the older OS tries to write to it.
You can use fsutil reparsepoint through Cmd to see the reparse point tag, if any, that's been attached to a file or directory.
answered Feb 4 at 19:24
grawitygrawity
239k37506561
9
You was right.fsutil reparsepoint query OneDriveshowed the data, andfsutil reparsepoint delete OneDrivesuccessfully "unlocked" the directory.
– enkryptor
Feb 4 at 19:38
1
Are reparse points not extensible/installable? Surely, the Windows OS does not natively support GitVFS.
– usr
Feb 4 at 20:38
3
The Windows OS did in fact receive changes in order to support GitVFS. IIRC, it always had a "minimum Win10 version" requirement. As with OneDrive, I assume it's partial support – the ability for userspace or for custom drivers to hook into the OS... Don't know if it means supporting arbitrary reparse points, or if it means supporting a specific reparse point but letting the implementation be installable.
– grawity
Feb 4 at 20:44
4
@usr Going forward, ProjFS will likely be the supported option for similar features, as it can be implemented purely in user-mode. It's not yet available in a stable release, though. ProjFS itself is (was?) implemented as a file system filter driver, which has been available as an extension point for quite a few Windows versions (going back through XP, I believe). OneDrive itself uses (used?) CldFlt ("Cloud Files Mini Filter Driver").
– Bob
Feb 5 at 1:22
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "3"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1401970%2fhow-does-onedrive-make-its-folder-not-functional-for-older-windows-versions%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
NTFS has a feature called reparse points, in which a file or directory can be tagged for special processing by the operating system. It's used to implement quite a few features – e.g. volume mount points (the Unix-ish alternative to drive letters); junctions and symlinks; GitVFS sparse directories; files that are actually stored inside a WIM image; files that have been offloaded to tape or other slow storage; and so on.
Recent versions of OneDrive also use reparse points to implement "online files" – they're placeholders at first, but downloaded on demand. Earlier versions did this at shell level, which didn't work with many programs; using a reparse point and moving the auto-downloading into the core OS makes them almost indistinguishable from local files.
Naturally new tags will result in an error when the path is accessed through an older OS; the NTFS driver doesn't know what to do with such items, so it just rejects the access. It could show e.g. an empty directory, but that could quickly result in more damage when the older OS tries to write to it.
You can use fsutil reparsepoint through Cmd to see the reparse point tag, if any, that's been attached to a file or directory.
answered Feb 4 at 19:24
grawitygrawity
239k37506561
9
You was right.fsutil reparsepoint query OneDriveshowed the data, andfsutil reparsepoint delete OneDrivesuccessfully "unlocked" the directory.
– enkryptor
Feb 4 at 19:38
1
Are reparse points not extensible/installable? Surely, the Windows OS does not natively support GitVFS.
– usr
Feb 4 at 20:38
3
The Windows OS did in fact receive changes in order to support GitVFS. IIRC, it always had a "minimum Win10 version" requirement. As with OneDrive, I assume it's partial support – the ability for userspace or for custom drivers to hook into the OS... Don't know if it means supporting arbitrary reparse points, or if it means supporting a specific reparse point but letting the implementation be installable.
– grawity
Feb 4 at 20:44
4
@usr Going forward, ProjFS will likely be the supported option for similar features, as it can be implemented purely in user-mode. It's not yet available in a stable release, though. ProjFS itself is (was?) implemented as a file system filter driver, which has been available as an extension point for quite a few Windows versions (going back through XP, I believe). OneDrive itself uses (used?) CldFlt ("Cloud Files Mini Filter Driver").
– Bob
Feb 5 at 1:22
add a comment |
NTFS has a feature called reparse points, in which a file or directory can be tagged for special processing by the operating system. It's used to implement quite a few features – e.g. volume mount points (the Unix-ish alternative to drive letters); junctions and symlinks; GitVFS sparse directories; files that are actually stored inside a WIM image; files that have been offloaded to tape or other slow storage; and so on.
Recent versions of OneDrive also use reparse points to implement "online files" – they're placeholders at first, but downloaded on demand. Earlier versions did this at shell level, which didn't work with many programs; using a reparse point and moving the auto-downloading into the core OS makes them almost indistinguishable from local files.
Naturally new tags will result in an error when the path is accessed through an older OS; the NTFS driver doesn't know what to do with such items, so it just rejects the access. It could show e.g. an empty directory, but that could quickly result in more damage when the older OS tries to write to it.
You can use fsutil reparsepoint through Cmd to see the reparse point tag, if any, that's been attached to a file or directory.
answered Feb 4 at 19:24
grawitygrawity
239k37506561
9
You was right.fsutil reparsepoint query OneDriveshowed the data, andfsutil reparsepoint delete OneDrivesuccessfully "unlocked" the directory.
– enkryptor
Feb 4 at 19:38
1
Are reparse points not extensible/installable? Surely, the Windows OS does not natively support GitVFS.
– usr
Feb 4 at 20:38
3
The Windows OS did in fact receive changes in order to support GitVFS. IIRC, it always had a "minimum Win10 version" requirement. As with OneDrive, I assume it's partial support – the ability for userspace or for custom drivers to hook into the OS... Don't know if it means supporting arbitrary reparse points, or if it means supporting a specific reparse point but letting the implementation be installable.
– grawity
Feb 4 at 20:44
4
@usr Going forward, ProjFS will likely be the supported option for similar features, as it can be implemented purely in user-mode. It's not yet available in a stable release, though. ProjFS itself is (was?) implemented as a file system filter driver, which has been available as an extension point for quite a few Windows versions (going back through XP, I believe). OneDrive itself uses (used?) CldFlt ("Cloud Files Mini Filter Driver").
– Bob
Feb 5 at 1:22
add a comment |
NTFS has a feature called reparse points, in which a file or directory can be tagged for special processing by the operating system. It's used to implement quite a few features – e.g. volume mount points (the Unix-ish alternative to drive letters); junctions and symlinks; GitVFS sparse directories; files that are actually stored inside a WIM image; files that have been offloaded to tape or other slow storage; and so on.
Recent versions of OneDrive also use reparse points to implement "online files" – they're placeholders at first, but downloaded on demand. Earlier versions did this at shell level, which didn't work with many programs; using a reparse point and moving the auto-downloading into the core OS makes them almost indistinguishable from local files.
Naturally new tags will result in an error when the path is accessed through an older OS; the NTFS driver doesn't know what to do with such items, so it just rejects the access. It could show e.g. an empty directory, but that could quickly result in more damage when the older OS tries to write to it.
You can use fsutil reparsepoint through Cmd to see the reparse point tag, if any, that's been attached to a file or directory.
answered Feb 4 at 19:24
grawitygrawity
239k37506561
NTFS has a feature called reparse points, in which a file or directory can be tagged for special processing by the operating system. It's used to implement quite a few features – e.g. volume mount points (the Unix-ish alternative to drive letters); junctions and symlinks; GitVFS sparse directories; files that are actually stored inside a WIM image; files that have been offloaded to tape or other slow storage; and so on.
Recent versions of OneDrive also use reparse points to implement "online files" – they're placeholders at first, but downloaded on demand. Earlier versions did this at shell level, which didn't work with many programs; using a reparse point and moving the auto-downloading into the core OS makes them almost indistinguishable from local files.
Naturally new tags will result in an error when the path is accessed through an older OS; the NTFS driver doesn't know what to do with such items, so it just rejects the access. It could show e.g. an empty directory, but that could quickly result in more damage when the older OS tries to write to it.
You can use fsutil reparsepoint through Cmd to see the reparse point tag, if any, that's been attached to a file or directory.
answered Feb 4 at 19:24
grawitygrawity
239k37506561
answered Feb 4 at 19:24
grawitygrawity
239k37506561
answered Feb 4 at 19:24
grawitygrawity
239k37506561
answered Feb 4 at 19:24
grawitygrawity
239k37506561
239k37506561
9
You was right.fsutil reparsepoint query OneDriveshowed the data, andfsutil reparsepoint delete OneDrivesuccessfully "unlocked" the directory.
– enkryptor
Feb 4 at 19:38
1
Are reparse points not extensible/installable? Surely, the Windows OS does not natively support GitVFS.
– usr
Feb 4 at 20:38
3
The Windows OS did in fact receive changes in order to support GitVFS. IIRC, it always had a "minimum Win10 version" requirement. As with OneDrive, I assume it's partial support – the ability for userspace or for custom drivers to hook into the OS... Don't know if it means supporting arbitrary reparse points, or if it means supporting a specific reparse point but letting the implementation be installable.
– grawity
Feb 4 at 20:44
4
@usr Going forward, ProjFS will likely be the supported option for similar features, as it can be implemented purely in user-mode. It's not yet available in a stable release, though. ProjFS itself is (was?) implemented as a file system filter driver, which has been available as an extension point for quite a few Windows versions (going back through XP, I believe). OneDrive itself uses (used?) CldFlt ("Cloud Files Mini Filter Driver").
– Bob
Feb 5 at 1:22
add a comment |
9
You was right.fsutil reparsepoint query OneDriveshowed the data, andfsutil reparsepoint delete OneDrivesuccessfully "unlocked" the directory.
– enkryptor
Feb 4 at 19:38
1
Are reparse points not extensible/installable? Surely, the Windows OS does not natively support GitVFS.
– usr
Feb 4 at 20:38
3
The Windows OS did in fact receive changes in order to support GitVFS. IIRC, it always had a "minimum Win10 version" requirement. As with OneDrive, I assume it's partial support – the ability for userspace or for custom drivers to hook into the OS... Don't know if it means supporting arbitrary reparse points, or if it means supporting a specific reparse point but letting the implementation be installable.
– grawity
Feb 4 at 20:44
4
@usr Going forward, ProjFS will likely be the supported option for similar features, as it can be implemented purely in user-mode. It's not yet available in a stable release, though. ProjFS itself is (was?) implemented as a file system filter driver, which has been available as an extension point for quite a few Windows versions (going back through XP, I believe). OneDrive itself uses (used?) CldFlt ("Cloud Files Mini Filter Driver").
– Bob
Feb 5 at 1:22
9
9
You was right.
fsutil reparsepoint query OneDrive showed the data, and fsutil reparsepoint delete OneDrive successfully "unlocked" the directory.– enkryptor
Feb 4 at 19:38
You was right.
fsutil reparsepoint query OneDrive showed the data, and fsutil reparsepoint delete OneDrive successfully "unlocked" the directory.– enkryptor
Feb 4 at 19:38
1
1
Are reparse points not extensible/installable? Surely, the Windows OS does not natively support GitVFS.
– usr
Feb 4 at 20:38
Are reparse points not extensible/installable? Surely, the Windows OS does not natively support GitVFS.
– usr
Feb 4 at 20:38
3
3
The Windows OS did in fact receive changes in order to support GitVFS. IIRC, it always had a "minimum Win10 version" requirement. As with OneDrive, I assume it's partial support – the ability for userspace or for custom drivers to hook into the OS... Don't know if it means supporting arbitrary reparse points, or if it means supporting a specific reparse point but letting the implementation be installable.
– grawity
Feb 4 at 20:44
The Windows OS did in fact receive changes in order to support GitVFS. IIRC, it always had a "minimum Win10 version" requirement. As with OneDrive, I assume it's partial support – the ability for userspace or for custom drivers to hook into the OS... Don't know if it means supporting arbitrary reparse points, or if it means supporting a specific reparse point but letting the implementation be installable.
– grawity
Feb 4 at 20:44
4
4
@usr Going forward, ProjFS will likely be the supported option for similar features, as it can be implemented purely in user-mode. It's not yet available in a stable release, though. ProjFS itself is (was?) implemented as a file system filter driver, which has been available as an extension point for quite a few Windows versions (going back through XP, I believe). OneDrive itself uses (used?) CldFlt ("Cloud Files Mini Filter Driver").
– Bob
Feb 5 at 1:22
@usr Going forward, ProjFS will likely be the supported option for similar features, as it can be implemented purely in user-mode. It's not yet available in a stable release, though. ProjFS itself is (was?) implemented as a file system filter driver, which has been available as an extension point for quite a few Windows versions (going back through XP, I believe). OneDrive itself uses (used?) CldFlt ("Cloud Files Mini Filter Driver").
– Bob
Feb 5 at 1:22
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1401970%2fhow-does-onedrive-make-its-folder-not-functional-for-older-windows-versions%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown