I used the MSU - which worked fine for this HP Compaq Presario CQ57 Laptop:
Now to clean up the 841 MB of redundant files in Windows\SoftwareDistribution, and the 778 MB MSU file in Downloads!
Why does Bash seem to be hogging ~half the CPU (about 46%, but very little memory) during this WU install process?
It happened during this update, and during the failed 222 update attempts.
Last edited by Fafhrd; 07 Oct 2016 at 00:53.
I got fed up waiting too and used MSU with no problems.
Read the title of the topic.Got it via WU, system working fine as it did before the update.
Though the build N. is 14393.222
Here is a speech about "Cumulative Update KB3197356 for Windows 10 PC build 14393.223".
You got it through WU ?
Or you confuse.
My questions: Why would MS release a cumulative update a not release it globally through the standard WU option? Why are some countries getting this update and others are not?
I sitting here at my PC checking the WU with nothing coming/showing up at all since this thread was started. Also, I shouldn't have to manually go get an update that is already supposed to be working through the WU channel. I don't understand the logic in this.
Which countries are you talking about?Why are some countries getting this update and others are not?
List these countries.
Or do not mislead people.
I think nobody is getting this through the normal Windows update method. Somebody confused the issue earlier by saying it came through Windows update but they were referring to last weeks KB. But I agree, I'm not going to retrieve an update other than through Windows update. Not sure what MS are playing at but I guess it will came through Windows update either tonight or patch Tuesday. Maybe even a latter version number than this one wil come through this way. The less amount of times I have to update the better. But my concern was that it should of been showing on Windows update but I was not seeing it - but it's very clear now that MS has not done it this way on this occasion. As my system has no evident problems on .222 I will wait it out. No sense fixing what isn't broken at the moment!