Forum Discussion
OneDrive for Business Client Stuck Processing nn changes for 2 full days. Never stops
I've got the same issue
and I'm in the situation : I can't uninstall !
Hoping we'll get a solution quickly
Hi Michel,
Do you re-direct one drive letter to a different drive letter, using the Subst or Map command, or via any third party apps. One of my computers has Windows on Drive C and ODFB local copy of Cloud Data on Drive D. It's been working beautifully for years.
I use DDE extensively with Office, so one spreadsheet can autoupdate other spreadsheet and Word files. When I sync-up to my main system using a machine that only has a Drive C, it can't find any of the DDE links on Drive D, because there is no Drive D on this remote machine.
The command is Subst d: c:\. After that, any time you reference drive d:, it is supposed to access c:\, and resolve the rest of the file path from there. With the redirected D: drive in place, my DDE programs work properly, but then OneDrive client hangs up forever. At first, I didn't think it was creating a problem. I thought it was just an annoyance dealing with the icon spinning forever. Now I've discovered that there are some folders I created that are not syncing to the cloud, and must be part of the "Processing 65 Changes".
It seems like this remapping of one drive letter to another confuses OneDrive Sync Client, and causes the situation where Sync Client gets stuck forever.
If you or anyone redirects drive letters and has the never ending Processing changes message, please write back with details and solution if available.
After much checking and no progress, I think using the SUBST command in a One Drive for Business Environment causes problems for the sync engine. As OneDrive client got more and more confused, the number of files included in the "Processing xx Changes message" kept getting bigger.
I finally had to give up, abandon the SUBST command, and document all of the sub folders throughout our OneDrive that were selectively synced to the problematic PC. Then, I unpaired the client from the cloud, uninstalled the OneDrive client, deleted the local copies of all of the files that were left on the machine, and re-installed the OneDrive client, selecting the subfolders that I previously documented. 48 hours later I was up and running, and the errant "Processing Changes" disappeared.
As I mentioned previously, I like using a C:\ partition for the operating system and a D:\ partition for data, because it allows image recovery backups of the C:\ partition to be restored without affecting any data on the local machine. However, if you have DDE Links that access D:\ and you move to a single partition environment, your DDE Links will be broken.
This may no longer be necessary as I've heard the one-button reset, with the option to leave all of your data intact, might obviate the need to have the O/S on C:\ and the data on D:\. In fact, recent Microsoft .docs papers suggest NOT partitioning a single C:\ drive in a Windows 10 environment:
- Data partitions
You can include a separate data partition to enable easier maintenance for situations where either the primary operating system is likely to be replaced, or when multiple operating systems exist on the same device, such as Windows 10 and Windows 7. When a device has multiple hard drives, a data partition may be stored on another drive. - Warning: For typical single-drive configurations, we do not recommend that you use a separate data partition. There are two main reasons:
- The partition may not automatically protect data that is stored outside the user profile folders. For example, a guest user might have access to files in an unprotected data partition.
- If you change the default location of the user profile folders to any volume other than the system volume, you cannot service your image. The computer may not apply updates, fixes, or service packs to the installation. For a list of known issues related to changing the default folder locations, see Description of known issues with the FolderLocation settings.
Microsoft can now add another reason not to partition the C:\ drive in Windows 10: If you use the SUBST: D: C:\ command to simulate a single drive environment after you partition the drive, it will interfere with OneDrive and cause errant messages and certain files and folders will not be synced, and you will not be warned that they aren't being synced.
- Data partitions
