It's the second Tuesday in June, which means it's time for another batch of cumulative updates from Microsoft. Like with all previous Patch Tuesday releases, June's a number of fixes, but no new feature updates.
For those on the latest Windows 10 release, the April 2018 Update, today's fixes are rolling out as KB4284835 (build 17134.112). And while this rollout addresses a number of bugs, it also contains a crucial fix for an issue affecting brightness controls on some laptops. This seems to have been most noticeable on HP EliteBooks, but you should see an improvement if you've experienced issues on other laptops as well.
Here's a look at all of what's fixed in the April 2018 Update Patch Tuesday release:
- Provides protections from an additional subclass of speculative execution side channel vulnerability known as Speculative Store Bypass (CVE-2018-3639). 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 this guidance document to enable mitigations for Speculative Store Bypass (CVE-2018-3639) in addition to the mitigations that have already been released for Spectre Variant 2 (CVE-2017-5715) and Meltdown (CVE-2017-5754).
- Addresses an issue in which the 2017 and 2018 versions of Intuit QuickBooks can't run in multi-user mode on Windows 10 1803 devices. Users will now be offered Windows 10, version 1803.
- Adds support for the SameSite cookie web standard to Microsoft Edge and Internet Explorer.
- Addresses an issue with Internet Explorer that prevents it from using an updated version of location services.
- Addresses an issue that causes certain games to fail to show dialogs when connected to monitors that support interlaced display formats.
- Addresses an issue with the brightness controls on some laptops after updating to the Windows 10 April 2018 Update. Addresses a reliability issue in which the GameBar may fail to launch.
- Addresses an issue where firmware updates cause devices to go into BitLocker recovery mode when BitLocker is enabled, but Secure Boot is disabled or not present. This update prevents firmware installation on devices in this state. Administrators can install firmware updates by:
- Temporarily suspending BitLocker.
- Immediately installing firmware updates before the next OS startup.
- Immediately restarting the device so that BitLocker doesn't remain in the suspended state.
- Addresses an issue that caused the system to start up to a black screen. This issue occurs because previous updates to the Spring Creators Update were incompatible with specific versions of PC tune-up utilities after installation.
- Security updates to Internet Explorer, Microsoft Edge, Microsoft scripting engine, Windows Desktop Bridge, Windows apps, Windows shell, Windows kernel, Windows Server, Windows storage and filesystems, Windows wireless networking, remote code execution, and Windows virtualization and kernel.
This update also contains a single known issue:
As is typical, we're also expecting Patch Tuesday updates to roll out to other currently supported versions of Windows, including older Windows 10 releases. For more, you can find all of the release notes for current and previously released cumulative updates at Microsoft.
Dan Thorp-Lancaster is the Editor in Chief for Windows Central. He began working with Windows Central as a news writer in 2014 and is obsessed with tech of all sorts. You can follow Dan on Twitter @DthorpL and Instagram @heyitsdtl. Got a hot tip? Send it to firstname.lastname@example.org.
ooowww that's why my laptop suddenly locked up during my work session 😅 its Patch Tuesday again.
Oh may wont to configured active hours.
it usually takes awhile to kick in for me though until I actually press check for updates
Of update windows defender
Yeah. I forgot to do that again after i had to fix the black screen issue the 1803 update gave :/ luckily is save my work every 15 minutes :D
yes I had the black screen for a few minutes myself
HDD related? it didn't happen on any of my other devices SSD/eMMC.
but I hear it's fixed after this update
'Notify me before update' should help you.
Great! This time 0.71% of the issues are fixed. Keep it up. Now, where is that guy who was telling me that it wasn't even a Patch Tuesday when the other 0.01% of the issues were fixed?
and the win10 mobile build is 10.0.15254.489
Get over it. It's dead. Stop beating a dead horse.
Not dead until updates stop & MS official anouncement...so you get over it, just work with your droid and/or iOS device and leave us be!
thanks to Microsoft now my brightness control works fine
One issue I (and many others on reddit) are having is that Windows still tries to install this update, even after it has verifiably been successfully installed, i.e. it asks me to reboot as if this update weren't installed in the first place even though the version number in winver reflects the correct version (OS build 17134.112).
Get the best of Windows Central in in your inbox, every day!
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.