Windows 10: Windows Update, AppX & SPP eat CPU for 30+ minutes at every logon

I would like to revive this thread https://answers.microsoft.com/en-us/surface/forum/all/windows-update-cpu-deadlock-no-way-to-fix/8c66b5fa-a09e-4081-8b39-baa1d07bfc68?page=2 because as explained in my last reply in that thread, the problem is NOT solved, on the contrary, it is now more severe than 9 months ago, and it also affect a 2nd PC but is completely absent from a third one To recap: At *every* cold boot, shortly after opening my session login, Windows Update, AppX deployment service Software Protection service eat together more than 25% CPU during 30 to 35 minutes on the first s

:)

 

tiworker randomly doing something for 20-30 minutes, eating 50% cpu


I have this annoying issue on my Windows 10 tablet, and because it is a tablet, I dont want something like this happening of course, that tiworker is doing something every once in a while, maybe once a week, or once every 2-3 weeks, maybe once every few day, suddenly taking 50%. And it takes about 20-30 minutes, afterwards it's finished.

When I look into Windows Updates, no update is taking place, nor is MS Store installing any app updates. So what is this tiworker doing every once in a while for so long, 20 minutes, eating 50% cpu? Task manager shows, that it has 1.8-2.8MB/s disk usage over this time, so its doing something.

I also looked into Windows Scheduler and I cant see any "active timers active".

Is there a way to debug, what tiworker is doing, and maybe deactivate it?

 

Appmodel's process eats 30-100% CPU

Today I made a clean installation of Windows 10 from latest installation media. I continuously get UI freezes for minutes. Task Manager shows me a process "appmodel" which uses most time more than 30 percent of CPU. Why it is so and how to fix it?

 

Windows Update Service eats my CPU for days on end

So the Windows Update Service is eating a whole core of my CPU persistently. Here is my sad story: Yesterday I noticed that "Service Host" was eating ~30% of my CPU. This turned out to be the update service thread as Process Explorer showed me:





I figure that I just have new updates, so I ignored it all day. This morning I woke my PC back up and found that I had the same problem. Update service is running at full bore. I restarted my PC. It restarted normally, but I noticed MS Installer running. After a couple minutes the MS Installer is done and the PC returns to its status-quo with the Update Service still running. I then attempt to stop the update service from the command line and get this message:





So what gives? My computer was on for ~9 hours yesterday, this should be more than enough for Windows Update to finish its stuff.