OneDrive 100% CPU unable to kill process

Martijn Kools 141 Reputation points
2023-09-20T09:16:11.1366667+00:00

Hello,

Since a couple of weeks we have an issue with some users with OneDrive. I believe it is FSLogix related. The user gets stuck in his Remote Desktop session. We log him off, his session is gone but there is still one OneDrive.exe executable remaining under his name. Which is at 100% CPU. The FSLogix ODFC and Profile disk are unmounted and already gone. In task manager there is no user visible under 'Users'. It's just one OneDrive.exe process. I tried to kill it in every way possible, process monitor, wmic, taskkill force etc but it's impossible to kill the process. I always get access denied. The only solution is to restart the server.

We run RDS, Server 2019, FSLogix 2210 HF2 (latest) and latest OneDrive version.

OneDrive
OneDrive
A Microsoft file hosting and synchronization service.
821 questions
Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,249 questions
FSLogix
FSLogix
A set of solutions that enhance, enable, and simplify non-persistent Windows computing environments and may also be used to create more portable computing sessions when using physical devices.
463 questions
0 comments No comments
{count} vote

2 answers

Sort by: Most helpful
  1. Hersom 0 Reputation points
    2023-09-20T16:52:26.8+00:00

    I think it is a common but unsolved problem. Compare e.g. to this question

    Hypothesis:

    The OS cannot resolve the user, hence it cannot know whether you have the required privilege to kill the process.

    Untested fix:

    Take a look at the Services tab in Task Manager.

    Does TermService run? Start or restart.

    Perhaps also consider VaultSvc.

    Look in Event Viewer: Any errors / warnings saying service xxx could not be started, when you try to kill the process? Then try to restart such services.

    0 comments No comments

  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more