2018-11 Update for Windows 10 Version 1803 for x64-based Systems (KB4023057) -Error 0x80070643
Refuses to install. Usual Microsoft merry go round, reinstall,reinstall etc. Still does not install.
Any ideas guys?
Many thanks.
ps; Happy New Year.
Mothie: KB4023057 is no longer available in the Microsoft Update Catalog. My best guess is that means it's since been supplanted by a different and newer Windows Update update (which is what this is: read about it: https://support.microsoft.com/en-my/help/4023057/update-to-windows-10-versions-1507-1511-1607-1703-1709-and-1803-for-up ). If you check this answer.ms.com thread about your very problem, the most common repair advice boils down to "upgrade to 1809." Sigh.
HTH,
--Ed--
Why is 1809 to be avoided and is there a good/safe Plan B for solving the problem? THX.
No idea, I've been using it since 3rd October and have found it to be as trouble free as 1803. Microsoft now feel confident enough to let anyone who clicks 'check for updates' get it.
Microsoft said:
If you have (or can get) the ISO for installing 1803 then you could try an in-place repair install....is there a good/safe Plan B for solving the problem? THX.
Repair Install Windows 10 with an In-place Upgrade | Tutorials
I am delighted that you have found 1809 to have no problems,Guru. Please pardon me if I do not share your faith and trust in Microsoft Windows 10.
A bit like Brexit in a way, too much controversy, no trust all round.
I have an older computer a Dell XPS 420 on W10 pro. I have managed to keep it running smoothly on W10 by any and all my own personal knowledge PLUS, all the help available from IT friends, The Internet and this good forum.
I do not trust Microsoft one jot and will not download another bag of trouble Until, Microsoft dumps it on my computer, which from past experience, they will to suit their own ends, not mine .
Sorry, can not share your faith.
Faith and trust? Not after the 1803 launch - IMHO that was one of the most bug-ridden initial releases I've ever seen. It was rushed out on the last day of April to qualify for its 'April Update' name. For months after it still had some 'Insider' telemetry built in. 1809 was a pleasant surprise (for a change).
You could of course share in my precautions. It's always safe to try out a new release if you have a Macrium Reflect image you could go back to if it all turns pear-shaped
Consider that a good thing.
The issue you bring up may not be limited to Microsoft and in your case Intel maybe involved.
I went through some similar codes yesterday with a couple of friends and was able to investigate information on their Intel products. I didn't keep the sources but I suspect the principle is the same.
Intel is updating their microcodes which isn't unusual but it's possible legacy products have to be dealt with.
In your case your Legacy product's code is related to code name Kentsfield.
Intel Core™2 Quad Processor Q6600 (8M Cache, 2.40 GHz, 1066 MHz FSB) Product Specifications
I don't have time to investigate Kentsfield but it can be time consuming anyway.
I see you don't trust but Microsoft did it's job when it just did the automatic 1809 update as it was determined your original KB4023057 didn't apply and moved on to allowing the next available update to install: in your case 1809.
--- I hope this helps.
Quote
Many thanks O guru. I will look it up.
Too true my friend. Yes,I do have one.
He he. I do not believe it! 
