New version of OneDrive jacks up CPU, creates huge files aria-debug…log

Topic

New Reply

This was posted by @adasch: After update Onedrive to 17.3.6998.0830 under W7x64, I notice huge disk and CPU activity. Onedrive shown starus “actual’ b
[See the full post at: New version of OneDrive jacks up CPU, creates huge files aria-debug…log]

Reply | Quote

Replies

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

Reply | Quote

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

7 users thanked author for this post.

AlexEiffel, Karlston, SueW, GoneToPlaid, woody, BobbyB, Great Lake Bunyip

Reply | Quote

Thanks! I was wondering how I could completely remove OneDrive from my computers.

Reply | Quote

Sounds like Noel gets rid of the errant “OneDrive” same as I do but its really handy and free storage and you can still use it without the CPU thrashing away.
http://www.thewindowsclub.com/map-onedrive-network-drive-windows-10
It just adds a right click ability to “send to” which gives you control over what you send to M$’s cloud. Beauty of this is that it works on Win7-10 all
Needless to say if your running on a few machines “OneDrive” doesent allow simultaneous logins but as a network drive you dont always have to login automatically.

3 users thanked author for this post.

AlexEiffel, flackcatcher, SueW

Reply | Quote

Thanks for the script. Manually removing OneDrive was just as good.

Reply | Quote

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.

~ Group "Weekend" ~

4 users thanked author for this post.

flackcatcher, woody, Great Lake Bunyip, Kirsty

Reply | Quote

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.

1 user thanked author for this post.

woody

Reply | Quote

(Awaiting moderation) OneDrive resets its whole catalogue after any version upgrade and verifies the file data for every file in the “drive”. That’s why it grinds away seemingly endlessly after an upgrade or App reset. How long it takes depends on the amount of data and number of files it need to crunch through. If you have a good number of gbs up, expect it to take a while, perhaps a couple of hours. Especially if you have a large number of files. After the re-catalogue is done it should be fine with normal running behaviour. Be patient. Enjoy several coffees or take a walk.

1 user thanked author for this post.

SueW

Reply | Quote

@adasch has also posted a topic on this subject.

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

Reply | Quote

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

1 user thanked author for this post.

MrBrian

Reply | Quote

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.”

Reply | Quote