Windows 10 April 2018 Update now available Monday, April 30

fdegrove · 30 Apr 2018

Hi,
@JohnBurns, thanks for the reply. I'll check a Haswell (same as your own I3 CPU) based machine I have here that I updated to 17134.1 and report back should it be fully protected.
I know there's no BIOS/UEFI update available yet for that one.
@essenbe, if that's for the I7 8700K then it quite likely had an update through the MB manufacturer, right ?

Cheers,

Phone Man · 30 Apr 2018

swarfega said:

For some reason I don't have .5, just .1.

.5 was only available to Insiders. Why MS did not include it in the release only the Shadow knows.

Jim

swarfega · 30 Apr 2018

Ah thanks for the clarification.

kado897 · 30 Apr 2018

JohnBurns said:

I updated to WinVer 1803 (OS Build 17134.5 thru Insider, tho I am not presently in Insider - and per InSpectre, I am fully protected. You might try InSpectre with 17134.1 again. If not, 17134.5 evidently fixed it.

Fully protected on 17134.1.

Brink · 30 Apr 2018

Deprecated and Removed Features in Windows 10 Version 1803 - Windows 10 Forums

Samsung User · 30 Apr 2018

Brink said:

Hello @JimWiz1, :)

It should be available via Windows Update, but it is a staggered (phased) release.

How to get the Windows 10 April 2018 Update - Windows 10 Forums

Got mine here in uk via WU and so far all working ok

MartinMDL · 30 Apr 2018

@kado897, @JohnBurns, @essenbe

did you guys update the BIOS with the newer uCodes released by Intel? If that's the case then it's normal to be protected even under 17134.1 because that protection does not come from the os side but rather from the BIOS one.
For those of us who don't have an official bios update, the only way to be protected is through a software ucode update which ms did with its optional kb. I was protected under FCU .402 with that KB installed (i double checked with either inspectre and via powershell speculation control), but am not anymore under 17134.1. Some other user on this very forum wrote:
"The Skip Ahead Update, Build 17369, is using the latest microcode from Intel on both my i7-2600 and i7-920.The Inspectre now shows that both Spectre and Meltdown as fixed on both processors. HWinfo also shows the microcode is updated on both to match Intel March guidance."
That makes me think that MS included the updated uCode again in those builds and we should hopefully get it when those updates get pushed through WU (some say May 8th which marks the first patch tuesday since this major update).

lopedoggie · 30 Apr 2018

103,871 views and 1,158 comments. Is there a problem here? you either get 1803 17134.1 or 17134.5. relax as it all works fine.

indianacarnie · 30 Apr 2018

Installed. No problems at all. Edge seems to look a little ……… snappier but it could just be these old eyes. Didn't have to go back and uninstall any MS app's like the last few times. Ran through Settings and all I had to really turn off was the Timeline thing. Very happy with this. Easiest upgrade ever.

kado897 · 30 Apr 2018

MartinMDL said:

@kado897, @JohnBurns, @essenbe
did you guys update the BIOS with the newer uCodes released by Intel? If that's the case then it's normal to be protected under 17134.1 because that protection does not come from the os side but rather from the BIOS one.
For those of us which don't have an official bios update, the only way to be protected is through a software ucode update which ms did with its optional kb. I was protected under FCU .402 with that KB installed (i double checked with either inspectre and via powershell speculation control), but am not anymore under 17134.1. Some other user on this very forum wrote:
"The Skip Ahead Update, Build 17369, is using the latest microcode from Intel on both my i7-2600 and i7-920.The Inspectre now shows that both Spectre and Meltdown as fixed on both processors. HWinfo also shows the microcode is updated on both to match Intel March guidance."
That makes me think that MS included the updated uCode again in those builds and we should hopefully get it when those updates get pushed through WU (some may May 8th which marks the first patch tuesday since this major update).

Yes. Of course that would not be affected by the upgrade