Windows 10: Windows update stuck

Been waiting for 2 hours for download 144Mb updates and not yet finish. My internet just run normally but the update stuck at 71%
Here some screenshots.





Thanks in advance

:)

 

Thinkpad X201 Tablet pen input and finger touch conflict since windows 10 upgrade

I have exactly the same problem with my Samsung smart pc pro. Can't sketch anymore because exactly the same reason.

I also tried a surface pro tablet with a pen and it had exactly same problem too. I think Microsoft forgot that issue...

 

Windows update and app download stuck

Hi

windows 10 app updates stuck on starting download and windows update also stuck

 

Hi, download the ISO manually and create a bootable medium (which is useful in various circumstances).
(How - where- see the Tutorial section
Windows 10 ISO Download - Windows 10 Forums
or search the net- not difficult).

That way you download once and can retry and have it available for other purposes. Also you avoid issues with Windows update.

 

It seems, like the cache is damaged. Run CMD as admin and copy/paste:

taskkill /im TiWorker.exe /f
net stop wuauserv /y
rmdir "%systemroot%\SoftwareDistribution\Download" /s /q
del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr0.dat"
del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr1.dat"
Dism /Online /Cleanup-Image /StartComponentCleanup
cleanmgr /sageset:65535 & cleanmgr /sagerun:65535

I wonder, if MS ever stops producing bad updates, it has problem installing and damages powershell afterwards.

 

Hi TairikuOkami,

Just to let you know that even after that interesting cleanup process Downloading updates is still sitting at 0%. Anything else you can suggest?

 

Sorry to hear that. I use this bat before running WUMT, it enables required services and restarts the adapter. Maybe?

 

TairikuOkami,

This no joy. Even added the previous commands to the end of the bat file script.
This is only since the 1607 update.
I'm wondering if i install KB3176936 and KB3176495 separately via MS catalog, will this issue occur for the next updates?