Microsoft released an extensive update that will fix many issues with the plagued Windows 10 update. The company released cumulative update KB4469342, which Microsoft claims, has been thoroughly test... Microsoft fixes lots of issues with Windows 10 October 2018 Update KB4469342
Aye, more of this (patches and updates). Let's hope Microsoft don't release 19H1 (RS6) with the same lack of polish.
It's a VERY sad reality when you're surprised to hear a report about Windows updates that doesn't mention a new issue.
The report doesn't mention any issues, which means, it is full of issues yet to be revealed. Guess, sometime in October 2019, the October 2018 patch will be ready... Or will it be named window$ 11 FG (Fool's Gold)...?. Just don't give up hoping...
As much as I want MS to cleanup their own mess, that changelog has nothing on this one https://support.microsoft.com/en-us/help/4462933
True. I think I'll sleep better tonight knowing hell hasn't frozen over and MS is probably still making mistakes as we speak.
This proves that there is no QA team inside MS and all the testings are done by Windows Insiders and consumers!! MS software products probably one of the worst quality software one can find.
One has not tried much software, me thinks. Also, again, thread full of negativity and whining just for the sake of it.
Just recently had an issue with Windows Defender no longer working. Checked and the Microsoft Store also would not allow me to download and install any apps. Then checked windows update and it was also broken. Had to completely reinstall Windows 10 on both my pc and my office pc which also had the exact same issue a few days later. Hopefully with this latest update etc this issue wont arise again.
There's still a really annoying bug present even with this patch though. If Fast Boot is enabled in your BIOS and you try to boot into windows, you'll get passed the motherboard post screen then just as you're about to go to the windows login part, your screen will go black and monitor will lose signal. This bug was not present with build 1803. The only workaround i've found is to disable Fast Boot in the BIOS and forget about it.
