- #Microsoft onedrive setup high cpu how to
- #Microsoft onedrive setup high cpu install
- #Microsoft onedrive setup high cpu windows 10
- #Microsoft onedrive setup high cpu windows
If it does, follow the same process, however this time instead of clicking End Task select Go to Details. Restart OneDrive and see if the problem returns immediately. Once you have the task manager open, find Microsoft OneDrive, right-click on it and select End Task. This can be done a variety different ways, the easiest of which is Ctrl+Alt+Delete.
#Microsoft onedrive setup high cpu windows
To kick off the process, you will first have to open the Windows Task Manager. Troubleshoot High OneDrive CPU and RAM Usage.
#Microsoft onedrive setup high cpu how to
Below you will find detailed step by step instructions showing you how to fix the problem. On top of high CPU usage, you may also find OneDrive is using far too much memory (RAM) The good news is that there are steps you can take to reduce OneDrives resource consumption.
#Microsoft onedrive setup high cpu windows 10
If you have recently noticed OneDrive is using more than its fair share of CPU power, this guide will show you how to solve the problem.Įven though the Microsoft OneDrive high CPU usage problem is most prevalent on Windows 10 it can be found on Windows 7, 8 and 8.1 as well.
Now the issue has transitioned to high CPU usage from Microsoft's cloud storage service OneDrive. More posts regarding UEM: Configuring printer in UEM with personalization.Windows 10 has a long history of high resource usage problems, originally starting with extremely high or 100% hard disk usage. If you like this post please help us by sharing this! Also leave a comment, If you have some questions. This will hopefully help you in providing the end user an overall better experience when using OneDrive in there RDS/VDI environment. ConclusionĪs you can see with a small adjustment we can have a big advantage in our OneDrive setup (no more performance hit during logon & profile bloat). Application blockingĪs this setup is using the %program files% installer, the application blocking rule can be adjusted to the same path to ensure no OneDrive could be initialized. So, therefore, the user does not need elevation rights. No process elevation is needed as the installer is available in the C:\program files (x86)\ folder. Change the path of the installer as shown below: I will be using the same configuration but adjust only a couple of settings using the machine based OneDrive installation.įirst, we need to change the initial installer that runs at logon when the user logs onto the RDS/VDI. Adjusting configĪs mentioned I already made an initial blog on how to configure Onedrive with VMware UEM.
#Microsoft onedrive setup high cpu install
Run the OneDrive.exe with the following parameter “/AllUsers”, this will install the client to the “program files” folder on the system.Īlso if you have pushed the initial OneDrive installer on the RDS/VDI base image, I suggest you remove this to have a clean setup when using the “Machine based” setup. The installation is rather straight forward as by start downloading the latest version of OneDrive, build 19.043.0304.0003 or higher. Machine-based installerįortunately, Microsoft has listened to the community and released a machine based installer that all users on a system will use. This to enhance the existing setup and use all benefits of the Machine-based installer. In this update, I will be adjusting the guide to use a machine based OneDrive installation. Again this was a working solution but the user profile gets bloated during the session and gets a performance hit during the installation.
Meaning when a user logged onto the RDS, a OneDriveSetup.exe was called, this installed the OneDrive agent into the %localappdata% of the user.
The setup had one major drawback being the Onedrive Installation was done in user context and not machine based. While the guide was a good and flexible way of configuring OneDrive for specific users. A few weeks ago, I wrote a post about configuring Onedrive for a Horizon VDI/RDS deployment with VMware UEM.