
Hopefully the WindowServer CPU usage issue is simply a bug or optimization issue that will be addressed, but for the time being this behavior continues well into the latest versions of Mac OS (Mac OS X 10.10.3 onward) even on the newest of Mac hardware. We’re going to attempt to tame the WindowServer process by reducing elements and features that may be spurring WindowServer behavior (or misbehavior), a challenging task given that WindowServer is necessary to draw almost everything seen in Mac OS X. If WindowServer is frequently staying at spiking high CPU usage for seemingly no meaningful reason in some situations with macOS and Mac OS X this article is aimed at you. Now after you have reset the PRAM, you may need to readjust your time zone and mouse speed etc, otherwise, you are good to go.At the worst, something like opening Quick Look, opening a few new Finder windows, or scrolling through a busy Finder folders contents leads to a surge in WindowServer processor usage that is high enough to cause a computer to freeze up or even the appearance of the much maligned beachball cursor.

Your MacBook will reboot again indicating that it has reset the PRAM and hold the keys until you can hear the startup chime. Press POWER+COMMAND+OPTION+P+R buttons before you see the grey screen. Release them after a few seconds and you shall see a brief change in the MagSafe light indicating that SMC has been reset. Now press CTRL+OPTION+SHIFT+POWER buttons. To reset your SMC, shut down your MacBook and attach the power adapter. When you observe odd behavior from that process, the first thing you can do is to take these troubleshooting steps.

The reason may be that your MacBook is having problems while connecting to Microsoft Exchange servers.

Some users have reported that when they visited particular websites, it triggered rpcsvchost to c onsume over 90% of the CPU power.
