Link to @adasch’s posts:
https://www.askwoody.com/forums/topic/fatal-update-onedrive-17-3-6998-0830/

A solution I’ve landed on is to completely uninstall OneDrive. I can honestly say it doesn’t cost me one extra cycle of CPU time. 🙂

::
:REMOVE_ONEDRIVE
::
    ECHO.
    ECHO Removing OneDrive system integration.
::
::  Kill OneDrive if it's running.
::
    TASKKILL /F /IM OneDrive.exe 2>nul
::
::  Run the OneDrive installer to uninstall it.
::
    IF EXIST "%SYSTEMROOT%\SysWOW64\OneDriveSetup.exe" GOTO REMOVE_64BIT_ONEDRIVE
::
::  32 bit
::
    "%SYSTEMROOT%\System32\OneDriveSetup.exe" /uninstall
    GOTO GIVE_TIME_FOR_ONEDRIVE_REMOVAL
::
:REMOVE_64BIT_ONEDRIVE
::
::  64 bit
::
    "%SYSTEMROOT%\SysWOW64\OneDriveSetup.exe" /uninstall
::
:GIVE_TIME_FOR_ONEDRIVE_REMOVAL
    TIMEOUT /T 15 /NOBREAK
::
::  Remove OneDrive files.
::
    IF EXIST "%PROGRAMDATA%\Microsoft OneDrive"  RD "%PROGRAMDATA%\Microsoft OneDrive" /S /Q
    IF EXIST "%USERPROFILE%\OneDrive"            RD "%USERPROFILE%\OneDrive" /S /Q
    IF EXIST "%LOCALAPPDATA%\Microsoft\OneDrive" RD "%LOCALAPPDATA%\Microsoft\OneDrive" /S /Q
::
::  Hide OneDrive from Windows Explorer.  This may be excessive, but we aim to be thorough.
::
    REG DELETE "HKEY_CLASSES_ROOT\CLSID\{018D5C66-4533-4307-9B53-224DE2ED1FE6}" /f >nul
    REG DELETE "HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{018D5C66-4533-4307-9B53-224DE2ED1FE6}" /f >nul
::
:: = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
::
    ECHO.
    ECHO Completed removal of OneDrive system integration.
::
:END_REMOVE_ONEDRIVE
::

Many folks don’t realize you can still share files via OneDrive by accessing the web interface through a browser, even after uninstalling the system integration.

-Noel

This post alarmed me a bit because we just accepted this update across multiple machines.  However, a quick random spot check tonight is not showing any of these symptoms at all on any I checked so far.  (12 out of 60+)

I have seen this behavior before though, specifically when a file that was shared with multiple users had a version contention.  The solution is to identify that file(s) and save a copy of the version you want off the OneDrive folder system, then delete it in OneDrive, wait for a full sync, then copy the good file back.

I think the reason is obvious by reading @adasch’s post

this bug kill netbook Atom CPU 1.6GHz resources.

This is very old hardware, never meant to run CPU intensive tasks and which could hardly cope with Windows 7 32-bit.
Once I owned a Dell Mini and I know it. 🙂

@adasch has also posted a topic on this subject.

Please see posts from @adasch at Fatal update: onedrive 17.3.6998.0830

Solution for me:

download onedrive 17.3.6943.0625

disconnect from internet and install it (it’s prevent to auto update)

make copy folder 17.3.6943.0625 in appdata\microsoft\onedrive some like copy_17.3.6943.0625

install latest official 17.3.6998.0830

setup it and synchronize files (aria files and high cpu usage is normal)

turn off onedrive

copy all accessible files from folder 17.3.6943.0625 to 17.3.6998.0830

some files is used but they do not make problems

after this run onedrive.exe, of course onedrive report version 17.3.6943.0625 but this prepared version don’t make upgrade to buggy 17.3.6998.0830 (15-25% CPU) and 17.3.7059.930 (50% CPU usage)

now, all work ok, CPU usage is close to 0% (under status actual) and don’t make large aria files.

system works nice under 1.6 Atom too 🙂

If it is any consolation, I opened a case with Microsoft and received this response two days ago:

 “We would like to inform you that many of our customers are facing this issue. This has already been escalated to our product team, and our product team is working towards its fix.
In the mean time till we come up with the fix to this issue, we request you to use selective sync or stop using sync client. I will inform you once I receive an update from our product team.”