hidden/system folder or drive full causes OneDrive to crash and re-sync everything!
When the OneDrive Client (windows 10) hits a folder it can't read (such as the System Volume Information on drives mounted as folders) it crashes and makes you have to re-configure and re-sync everything. It also does that if the drive it works on is full. After re-sync, it re enables all folders, even the ones you did not want to sync, causing even more problems.
It will sit for hours and hours "processing changes" before letting me uncheck folders or actually syncing again.
Nicholas H commented
WORKAROUND (tested on Windows 10)...
EDIT: For those of you who don't know how to map a drive letter to your OneDrive folder, read this thread and search for my latest comment:
The workaround is based on the idea of taking ownership of the System Volume Information folder and limiting access only to authorized users which OneDrive needs in order to work. This prevents Windows services from trying to create this folder (because it already exists) and may also prevent Windows from using it for search and recovery operations which should be left to the main volume settings.
1) Open an elevated command prompt (i.e., run Command as Administrator)
2) CD to the root of the mapped-drive folder (which points to your OneDrive folder)
3) To confirm if you already have a System Volume Information folder, type dir "System" then press the TAB key. The word System should expand to "System Volume Information" if the folder already exists. Alternately, you could try to create the folder, which will fail only if it already exists.
4) If Windows hasn't yet created this folder, create it now (to avoid the OneDrive crashing issue) and then use Windows Expolorer or the attrib +H command to hide it and you are done.
5) If the folder already exists (the usual case) then you must take ownership of it by running the command: takeown /f "System Volume Information" /R
6) Once you have ownership, remove the system, read-only, hidden attributes by running the command: attrib -H -S -R "System Volume Information"
7) (OPTIONAL) Reapply the hidden attribute with attrib +H "System Volume Information". However, be prepared to Show Hidden Files and Folders for the next step
8) Find this System Volume Information folder using Windows Explorer
9) Right-click the folder and choose Security->Advanced->Add->Select a principal. Enter the name "Authenticated Users" and press the Check Names button, then press OK. Leave the security settings at their defauls (i.e., Read&Execute List, and Read)
10) Map (or remap) your OneDrive folder to this folder using the OneDrive->Settings-->Account->Add an account dialog. Be sure to use the Change Default Location option and point to your OneDrive folder NOT using your mapped drive (use the full path on the host drive).
I'm experiencing the exact same issue. I mapped a drive letter to the root of my OneDrive folder to make it easier to access my cloud files and to make it more obvious to me when I'm saving stuff to the cloud. For example, I know that anytime I'm writing to drive Z: it's going to sync to the cloud. The problem is that the drive mapping causes The System Volume Information folder to be created inside my OneDrive folder which blows up OneDrive. It's painful to work with long and ugly folders like D:\OneDrive\OneDrive - MyBusiness\ so fixing this would be very helpful. The only workaround is to settle for a directory junction (see mklink /? DOS command) that points to this ugly path. At least then I can access my cloud data as d:\mycloud.
I am having this same problem. I can delet the SVI folder by changing permissions after its created, but this is only after OneDrive crashes and needs to reconfigure.
The SVI is supposedly a dependent of the system restore feature. I disabled system restore and deleted all history. Still, it came back. SysRestore is deleted on all machines that access the account. Still, it comes back.
Yes, it is a ROYAL PITA to have to reconfigure b/c it locks you out of your OneDrive for hours. I don't mind SVI sitting there (I can hide after all and it isn't large), but when it nukes OneDrive each time b/c it gets dropped there with no permissions that is a huge problem.
Have either of you made any progress on this?
OneNote crashes when using attached folders and the total space consumption calculation becomes negative (compared to the root drive's available space) because of it
After updating to Windows 10 (from W7 pro), I´m experiencing this issue.
I have mapped folders inside the OneDrive base folder as virtual drives (in my case for example Z: using SessionManager DosDevices registry allocation) in order to easily access my files...
Now, Windows 10 creates System Volume Information on the folder root of my virtual Z drive and OneDrive crash continuously.. Worst is that you can´t deselect those folders when configuring the OneDrive client because they are not shown on the tree.
Moving my data to the cloud (Office 365 storage) takes me a week of pain already and I'm not even half way done with only 100gig of data.