J'ai un laptop running Windows 8. Although it originally ran well, it started having very bad performance issues. I decided to perform some research into the topic. Opening up Gestionnaire des tâches, I discovered a process called `TiWorker.exe` (Je pense this handles update checking) takes up ~50% of my CPU for the first hour my computer is on, then shuts down.
This causes my computer to have horrible load times an very bad performance. My CPU usage hovers between 90-100%, which is unacceptable. To put this into perspective, my CPU hovers between 0-20% and Linux, and the startup is quick. I understand that Linux has much better performance than Windows anyway, but this is excessive.
Is there any way I can cause TiWorker to take up less CPU? I really need my computer to be fast (au moins, more so than a snail). Thanks for any help. I really appreciate it.
Here is my `xperf` `etl` file: [https://www.dropbox.com/s/6le4j7ye9on0k79/HighCPUUsage.etl]( 3 )
TiWorker.exe - Very High CPU Usage
Re: TiWorker.exe - Very High CPU Usage
So it seems, that Microsoft published an update in 2013, introducing some new features into the Windows Update engine, including compression of old files. The `TIWorker.exe` will start to compress files, but the SFC (System File Checker) detects the modified files and restores them back to how they were, causing the `TIWorker.exe` to crash (you'll see the Windows Error Reporting in the Gestionnaire des tâches eating all you resources).
It seems, that running la commande suivante on an elevated invite de commandes fixes the issue:
```
DISM /online /cleanup-image /restorehealth
```
I can't test it on my machine as J'ai installé my machine from scratch when I encountered that issue, but the approach looks really promising.
The original source mentioning this solution can be found [here](http://www.bit-tech.net/news/bits/2013/06/14/win8-bug/1).
It seems, that running la commande suivante on an elevated invite de commandes fixes the issue:
```
DISM /online /cleanup-image /restorehealth
```
I can't test it on my machine as J'ai installé my machine from scratch when I encountered that issue, but the approach looks really promising.
The original source mentioning this solution can be found [here](http://www.bit-tech.net/news/bits/2013/06/14/win8-bug/1).