Windows 10: Another Windows 10 bug causes high CPU usage and breaks IME

Windows 10 KB4515384, which was released to everyone on September 10 with security fixes and quality improvements, has been plagued by yet another bug. KB4515384 comprises of security fixes and a fix for a Cortana bug causing high CPU usage on some systems, but users have reported that the update causes issues with Start menu, Windows Search and Audio.

The cumulative update for Windows 10 version 1903 comes with an ever-increasing list of bugs. Recently users reported that the update kills the network adapters and it looks the same patch is also causing problems with Input Method Editor (IME).

(IME) is a part of the OS and it basically provides a specialized UI for text input, which can be used in many situations. For example, IME allows users to enter Chinese, Japanese or Korean text using Latin Keyboard. It also allows users to enter Latin text using numeric keypad and this feature even helps to add text to the system with handwriting recognition.

In a post to the Feedback Hub, multiple users said that the IME fails to launch and consumes CPU after applying Windows 10 KB4515384:

“The input method was failed to launch after installing the patch, and there was no way to get it fixed. Eventually, I uninstalled this update, and the IME successfully came back. FYI, I use multiple IMEs on my PC, and all of them were down after the update. So I assume this issue is not limited to occur with a specific language in the IME,” a user documented the problem.



Microsoft is apparently aware of unresponsive IME or high CPU usage caused by IME. In a Feedback Hub, the company acknowledged the problem and confirmed that they are investigating the reports

“We’re investigating an issue where some Input Method Editor (IME) may become unresponsive or may have high CPU usage. Affected IMEs include Chinese Simplified (ChsIME.EXE) and Chinese Traditional (ChtIME.EXE) with Changjie/Quick keyboard,” Microsoft said.

Microsoft has also updated the support doc to detail a workaround:

• Open Start menu and search ‘Services’. You can also open Cortana and search ‘Services’.
• In the Services app, locate Touch Keyboard and Handwriting Panel Service.
• Double-click process and access Properties tab.
• Under Startup type, switch to Manual and click OK to apply changes.

A reboot may be required to resolve problems with IME and address the high CPU usage to some extent. Microsoft says IME issues will be resolved in an upcoming cumulative update.

The post Another Windows 10 bug causes high CPU usage and breaks IME appeared first on Windows Latest

Weiterlesen...

 

Windows 10 Chinese Traditional Array IME causing high CPU usage

I found Chinese Traditional Array IME will induce high CPU usage after Windows 10 anniversary update(aka version 1607). Every time I type Chinese(Traditional, Taiwan) with Chinese Traditional Array IME , the CPU usage get higher after some time.

I had clean installed different OS versions on different PCs, and quite sure the the problem is caused by the Array IME. Also I found many people complaining about the high CPU usage problem after upgrade and there are no solution yet. Hoping the problem can
be taken seriously, it is not just annoying but also bad for the earth environment, cannot imagine how much energy wasted on this problem. Thanks.

 

WIN10 1703 update cause Explorer.exe high CPU usage

Hi,



Glad you reached out. First, we would like to know if Explorer.exe
is the only cause of high CPU usage. Because the common cause of high CPU usage are the following:

- Windows 10 Memory leak after the update.

- Driver incompatibilities after the update.

- Multiple startup applications

• 
  

We'll be waiting for your update.

 

ntoskrnl.exe causing high cpu usage

It is completely random when it causes high CPU usage. It dosen't (as far as I can see) take up much memory, it just causes high CPU usage.

It spikes to about 20 - 90 % and stays like that for a second or so and causes my computer to freeze during that time. It can happen often, like every 5-10 minutes and sometimes it can go about 30 minutes. I do not recieve any error when this is happening.