Current Status of Windows 10 October 2018 Update version 1809
-
Ex_Brit you may wish to have a look at this.
https://docs.microsoft.com/en-gb/win...dy_UpgradeTips
Notice the SetupDiag download, may point you to issue. Of course you might have a driver or app that is a known issue to 1809 and MS isn't ready for your machine. Did you force the update or did WU offer the update?
I forced it. I've even tried making an install disk including 1809 and trying a clean install and that also failed so I think it must be somewthing that Microsoft doesn't like but aren't telling me what it is.
I'm not good at reading error reports so am probably giving up on my Win 10 partitions until 7 dies in 2020.
-
I agree with you but they should have corrected the mapping issue by now - and others.
I'm very hesitant to upgrade to 1809 after what happened. 1803 works fine for me at the moment.
FWIW.
No matter what, at some point you will have to go with the flow. So why not make a system image backup first and give it a try. Because right now as we speak (or write), I am not having any problem with .134. Everything seems to be working fine so far. Maybe, I am just lucky and pretty sure that I am not the only one. 
-
No matter what, at some point you will have to go with the flow. So why not make a system image backup first and give it a try. Because right now as we speak (or write), I am not having any problem with .134. Everything seems to be working fine so far. Maybe, I am just lucky and pretty sure that I am not the only one.
It's already in progress down in my little test lab. Thanks.
However, I will *not* roll it out to my network dependent client base until many issues are marked and tested to be resolved.
-
-
However, I will *not* roll it out to my network dependent client base until many issues are marked and tested to be resolved.
Neither would Microsoft, not until they switch it from the 'Semi-Annual Channel (Targeted)' branch to the 'Semi-Annual Channel'. I suspect this time round they will take their time before doing that 
-
All of my 3 systems when checked for updates have only received KB4467702 CU for 1803. I have it downloaded via MCT, but at this point not ready to give it a test. I'll wait for the WU version.
-
-
I see. Yes, I was well aware of the issues with 1809 when they first released it. I have Google on my phone and it keeps me updated with the latest news about Windows 10. I think it used to be called Google Now, but I think they changed the name in later versions. The issues I had with my HP machine were sound quality issues. My HP came with Bang & Olufsen sound and the quality of the sound was horrible. Thats why I reverted back to 1803.
-
So, if you had KB4346084 installed on 1803 to give Spectre variant 4 mitigations, there is no equivalent for 1809.
This is the identical situation with 1803 until KB4346084 arrived. Updating reduces effective Spectre mitigations, especially galling when the Cumulative Update KB4467708 (17763.134) trumpets;
Provides protections against an additional subclass of speculative execution side-channel vulnerability known as Speculative Store Bypass (CVE-2018-3639) for
AMD-based computers. These protections aren't enabled by default. For Windows client (IT pro) guidance, follow the instructions in KB4073119. For Windows Server guidance, follow the instructions in KB4072698. Use these guidance documents to enable mitigations for Speculative Store Bypass (CVE-2018-3639). Additionally, use the mitigations that have already been released for Spectre Variant 2 (CVE-2017-5715) and Meltdown (CVE-2017-5754).
But....nothing for Intel-based computers. Way to go, Microsoft! Bravo! 
-
So, if you had KB4346084 installed on 1803 to give Spectre variant 4 mitigations, there is no equivalent for 1809.
This is the identical situation with 1803 until KB4346084 arrived. Updating reduces effective Spectre mitigations, especially galling when the Cumulative Update KB4467708 (17763.134) trumpets;
But....nothing for Intel-based computers. Way to go, Microsoft! Bravo!
Thanks for the info. However, I will join you in manifesting your frustration since I also have an Intel-based PC.
-
Thanks for the info. However, I will join you in manifesting your frustration since I also have an Intel-based PC.
The mcupdateGenuineIntel.dll does include the Spectre variant 2 mitigations that were such an annoyance (KB4100347) in 1803. But equally, it did annoy a lot of people who were enjoying an overclock due to older uCode.
The mitigations aren't active until the registry settings are changed (Spectre variant 2 and 4 can be manually enabled or disabled - or via a registry fragment .reg) so why the softpatches aren't included in mcupdateGenuineIntel.dll I have no logical explanation for.
-
![]()
The mcupdateGenuineIntel.dll does include the Spectre variant 2 mitigations that were such an annoyance (KB4100347) in 1803. But equally, it did annoy a lot of people who were enjoying an overclock due to older uCode.
The mitigations aren't active until the registry settings are changed (Spectre variant 2 and 4 can be manually enabled or disabled - or via a registry fragment .reg) so why the softpatches aren't included in mcupdateGenuineIntel.dll I have no logical explanation for.
I have never tried to overclock my PC, because I found the procedure too risky. And to tell you the truth, I don't even know where I stand right now with regard to Spectre & Meltdown since KB4100347. I don't even think GRC's Inspectre is worth trusting right now with all the bugs MS's recent updates are having lately. I completely understand that it would be very difficult to update their little app in such environment.
As to "why the softpatches aren't included in mcupdateGenuineIntel.dll", you will have to be part of the inner circle at Redmond to supposedly have an answer to that. Even then..!.Here is hoping that (fingers crossed) by 19H1 everything would get back to normal, which I consider a big word for now. .
Quote