June 2019 Patch Tuesday is rolling out

Topic

New Reply

With Bluekeep patching behind us (hopefully), we are waiting for the June 2019 results to come rolling in. There are (only) 108 new entries in the Win
[See the full post at: June 2019 Patch Tuesday is rolling out]

5 users thanked author for this post.

SueW, Fred, woody, jburk07, geekdom

Reply | Quote

Replies

Direct Catalog downloads for Group B Security-only patches and IE11 Cumulative Updates have been updated on AKB2000003 on 6/11/2019.

Please note: The font on the AKB2000003 page appears as light gray. The links still work. You have to squint!

Please note:  pciclearstalecache.exe was NOT bundled with the Win7 June Security-only Update and is NOT needed with the June Security-only update.

5 users thanked author for this post.

Sandman, SueW, woody, abbodi86, walker

Reply | Quote

What is the chance of repairing the font on that page for old eyes?

Installed pciclearstalecache.exe as instructed in the past. Does this now need to be done EVERY month???!!!

Reply | Quote

Faint Font Feint – Highlight* the text of interest -OR- Ctrl+A to highlight entire page.
* – Hold down either Shift or Ctrl, and sweep across text with mouse.

PCI… .EXE –
1) See PKCano’s third paragraph.

2) For those readers in “Group A” (full Rollups, not Security only) —
Below is copied from here, representative of notices starting April 9, 2019:

Starting with KB4493472 Monthly Rollup updates will no longer include PciClearStaleCache.exe.
. . .
Administrators should ensure that any one or more of the Monthly rollups released between April 10, 2018 (KB4093118) and March 12, 2019 (KB4489878) have been installed prior to installing April 2019 and later updates. Each of these rollup updates includes PciClearStaleCache.exe.

Reply | Quote

[NetDef]

Pulling 1903 KB4503293 now on several test machines.

Be interesting to see if the deferral settings bug gets fixed.

 

EDIT:  Post 1903 patch – looks like the deferral UI is still missing the Feature control/drop-down.  So not fixed yet.

~ Group "Weekend" ~

• This reply was modified 5 years, 10 months ago by NetDef.

Reply | Quote

Argh!

I wonder what will happen when they do fix it?

2 users thanked author for this post.

fk5353, Fred

Reply | Quote

Beta Test Reporting on Windows 7 x64 Updates

– Windows Malicious Software Removal Tool x64 – June 2019 (KB890830)
– June Security Monthly Quality Rollup Windows 7 x64 (KB4503292)

All installed without error and the system rebooted without error.

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

9 users thanked author for this post.

Chessie, TaskForce141, Sandman, dgreen, Ken Sims, abbodi86, wEarwOlf505cole, jburk07, Geo

Reply | Quote

I might inevitably have clashed with one of the mods resulting in my post disappearing completely. So let’s start again:

2019-06 Security Monthly Quality Rollup for Windows 8.1 for x64-based Systems (KB4503276)

Consistently crashes my Windows 8.1 laptop upon restart / first connection to (oh irony!) Microsoft Foldable Keyboard. OS crashes with SYSTEM_THREAD_EXCEPTION_NOT_HANDLED indicating (oh irony!) bthport.sys – so MS-own driver.

Genuinely surprised as never had encountered such nonsense before.

I guess it might be something to do with:

https://support.microsoft.com/en-gb/help/4503276/june-11-2019-kb4503276-os-build-monthly-rollup

Addresses a security vulnerability by intentionally preventing connections between Windows and Bluetooth devices that are not secure and use well-known keys to encrypt connections, including security fobs. If BTHUSB Event 22 in the Event Viewer states, “Your Bluetooth device attempted to establish a debug connection….”, then your system is affected. Contact your Bluetooth device manufacturer to determine if a device update exists. For more information, see CVE-2019-2102 and KB4507623.

https://support.microsoft.com/en-gb/help/4507623/some-bluetooth-devices-may-fail-to-pair-or-connect-after-applying-june

If you experience issues pairing, connecting or using Bluetooth devices after installing any of the affected security updates, please contact the manufacturer of your Bluetooth device to determine if a device update exits.

I’m using fairly recent Intel driver already @ AC7260 card that otherwise performs splendidly:

https://www.intel.com/content/www/us/en/support/articles/000005489/network-and-i-o/wireless-networking.html

Roll-back has worked for me either (I’m using laptop as we speak) and as I also use Bluetooth on my desktop PC with Windows 10 Home it looks like time to sit and wait.

1 user thanked author for this post.

jburk07

Reply | Quote

Thank you krzemien. It is thanks to people like you and Geekdom, that test these new patches (and OSs) immediately and report back on the results, to get the ball rolling at Microsoft for “patches to the patches”.

The only comment to you and others is: please give computer information of what you have. OS, bit, CPU, network card and possibly the GPU video.

1 user thanked author for this post.

woody

Reply | Quote

SONY VAIO SVF151AC5E

fully fitted (12 GB RAM, 512 SSD, i7 3rd Gen, nVidia GT735M), with Windows 8.1 64-bit Home ever since and fully updated (as of May 2019 now, that is!). The only alteration is Intel 7260 card that replaced non-performing Broadcom adapter.

About this pickle that I have though… Reading into these Bluetooth vulnerabilities further and unless Intel got something wrong AGAIN, it might actually be Microsoft-own keyboard that got the chop here – as far as I’m concerned it might be not supported by them any more.

Which obviously would make me rather unhappy as laptop’s own keyboard stopped working some 18 months ago as a side effect of rather over-scrupulous cleaning…! And I was rather pleased with this workaround until now!

Reply | Quote

Update:

1. Just managed to get KB4503327 (Windows 10 1809 Jun 2019 patch) installed – whether I liked it or not, had to use PC today… Works fine although patch itself had to be installed twice.

All Bluetooth devices work fine as well.

(separately: I started seeing invite to get 1903 installed afterwards – funny that! I’ll wait and see this time as I really enjoy my little stability)

2. Hesitantly got this keyboard paired & connected to this PC – all is good either.

 

I therefore suspect either something dodgy within KB4503276 (yesterday’s monthly patch for Windows 8.1) or – more likely – Intel Bluetooth driver being at fault.

Interestingly, it’s 20.120.2 that’s available for Windows 8.1, but all other versions are on 21.10.1 already.

Reply | Quote

Hello krzemien, You mentioned, “… laptop’s own keyboard stopped working some 18 months ago as a side effect of rather over-scrupulous cleaning…!” Could you expand (if willing) on what happened? I use a vacuum cleaner with the long hose and “Soft brush” attachment to pull dust out of the keyboard, the vent slots, and the cooling fan pathways (both directions) and have done this for years. No issues.

Reply | Quote

Cleaning foam, guv, with which I must have been over-generous that particular time even though I do not spray directly onto surface (obviously) but paper towel…

I did not manage to find where the problem is exactly – I suspect controlling circuitry beneath, as main PCB etc. is definitely fine – and the trouble is that this keyboard forms part of the laptop top surface itself and is irreplaceable unless one decides to replace top casing. And as I got this laptop ordered in fierce red colour…

Reply | Quote

Krzemien,

I suspect that the keys, when depressed, push together 2 flexible membranes with circuit tracings on them. When wet & soapy they get stick together by surface tension. When the apparatus dries out, they become unstuck & function normally. That’s what happened to a standalone (and therefore able to be disassembled) keyboard of mine in the past.

Zig

Reply | Quote

Thanks very much.

Damage has been done early Dec ’17 – and more-or-less half of the keyboard does not to work ever since. Do you think there’s still something I could try and I possibly haven’t yet, except treating with copious amount of compressed air both inside & outside / using hairdryer to warm it up?

You sadly cannot replace this keyboard easily as it’s a part of top casing – as can be seen here:

https://www.youtube.com/watch?v=98mnZmwwJeE

This solution with MS Foldable Bluetooth Keyboard – not ideal but does the trick.

Reply | Quote

For those ones who still read this thread somehow and for completeness: I got dismayed by this situation and once I confirmed that it’s most likely now-obsolete Intel AC7260 and its Bluetooth driver that is to blame and does not (will not) allow me to use any small and compact Bluetooth Keyboard that I could be happy with anymore, I decided to give it a go and replaced keyboard (& top casing that contains it) yesterday.

So £10 (brand new top casing off eBay) & 3 hours later I’m happy to confirm that I have not damaged or broken anything, laptop remains fully operational and keyboard now works!

Reply | Quote

krzemien wrote:

I might inevitably have clashed with one of the mods resulting in my post disappearing completely. So let’s start again:

Not at all – you got caught by the automatic spam filter, for posting so many links! You have, in the meantime, sent us on a merry dance trashing repeated logged-in and anonymous reposts! 😉

1 user thanked author for this post.

jburk07

Reply | Quote

Sincere apologies for this mess – we got there in the end though!

Meanwhile raised this little problem with Intel on their forums:

https://forums.intel.com/s/question/0D50P00004MSnpbSAD/windows-81-os-consistent-crash-after-kb4503276-jun-2019-update-driven-by-bluetooth-drivers-when-connecting-to-microsoft-foldable-keyboard-upon-system-start

Reply | Quote

Here’s Bleeping Computer’s blurb on the BlueTooth issue:

https://www.bleepingcomputer.com/news/security/microsoft-blocks-some-bluetooth-devices-due-to-security-risks/

“…and the hits just keep onnnn comin’!”

Win7 Pro SP1 64-bit, Dell Latitude E6330 ("The Tank"), Intel CORE i5 "Ivy Bridge", 12GB RAM, Group "0Patch", Multiple Air-Gapped backup drives in different locations. Linux Mint Newbie
--
"The more kinks you put in the plumbing, the easier it is to stop up the pipes." -Scotty

Reply | Quote

Windows 8.1 x64; installed kb4503276 SMQR for June 2019 which seemed ok upon restart.
Hit by the following pop-ups when accessing Event Viewer Custom View whilst checking patch installation results:

The process cannot access the file ‘C:ProgramDataMicrosoftEvent ViewerViewsView_0.xml’ because it is being used by another process.

Windows Logs section of Event Viewer seems fine no errors after a thorough scan.
MMC is being used by another process?
Needless to say patch uninstalled and Event Viewer back to normal.

Windows - commercial by definition and now function...

3 users thanked author for this post.

laidbacktokyo, MrChaz, jburk07

Reply | Quote

No issue here, x86
i don’t even had that file

1 user thanked author for this post.

Microfix

Reply | Quote

Thanks abbodi86, investigated further to find that the xml file was from a usb device which no longer exists on this system. Deleted the redundant xml file and re-installed kb4503276 and all is good, no errors at all in event viewer 🙂

Windows - commercial by definition and now function...

2 users thanked author for this post.

jburk07, MrChaz

Reply | Quote

Looks like you’ve found something that is happening to Windows 10 also. More info over at Ghacks: https://www.ghacks.net/2019/06/12/windows-10-event-viewer-error-after-installing-kb4503293-and-kb4503327/

illegitimi Non Carborundum

2 users thanked author for this post.

jburk07, Microfix

Reply | Quote

thanks @mrchaz, the same thing happened on another W8.1 x64 device also.
Have posted over on ghacks to let Martin Brinkmann know also.

Windows - commercial by definition and now function...

Reply | Quote

MS has acknowledged a similar-sounding problem in all versions of Windows – Event Viewer may close or you may receive an error when using Custom Views

Looks like this bug was introduced in basically all of the patches this month….

2 users thanked author for this post.

jburk07, laidbacktokyo

Reply | Quote

Now shown as mitigated; a PowerShell script workaround is provided in KB4508640

3 users thanked author for this post.

jburk07, laidbacktokyo, woody

Reply | Quote

The similar / same MMC snap-in issue with June 11, 2019—KB4503292 (Monthly Rollup) https://support.microsoft.com/en-us/help/4503292 on win7sp1x64. Pls refer to a pic attached:

An attempt to resolve issue as deleting both keys FX:{b05566ad-fe9c-4363-be05-7a4cbb7cb510} found in registry and rebooting win7 laptop returned no results while this MMC issue persists. Then this June 2019 Rollup has been uninstalled and this issue vanished immediately while win7 now is back on May 2019 Preview state.

1 user thanked author for this post.

jburk07

Reply | Quote

UPDATE: well, I’ve duly try to apply that official m$ script as above https://support.microsoft.com/en-us/help/4508640/event-viewer-may-close-or-you-may-receive-an-error-when-using-custom-v both thru Power Shell x64 6.2.0 as well as thru the native win7 PS w/o any good result. The issue persists, so again rolling back to May 2019 Preview.

Reply | Quote

I think it’s fantastic that there is a shot out to the excellent work over at GHacks. It’s like two of my favorite musicians collaborating on a song. Thanks for the information. About to run this ADR to our testing group. To all my fellow admins and techs: good luck with this month’s updates!

Rugged indoorsman.

3 users thanked author for this post.

woody, Seff, AJNorth

Reply | Quote

Both ghacks and Borncity are my go-to sites when things go bump in the night…

1 user thanked author for this post.

AJNorth

Reply | Quote

[Geo]

Group A,  Win7X64,  Home premium,  AMD,  Microsoft security essentials, ADWcleaner, only used for email, print and  internet.  No problems, no slow down.

• This reply was modified 5 years, 10 months ago by Geo.

2 users thanked author for this post.

dgreen, jburk07

Reply | Quote

[abbodi86]

Windows 8.1 x86, no issue with KB4503276

FYI, when i opened IE11 after restart, this page automatically opened asking me to set the “recommended” settings
https://ie11welcome.microsoft.com/en-us/index.html

clicked the X mark inside the page, the tab closed and i retained my current settings

• This reply was modified 5 years, 10 months ago by abbodi86.

2 users thanked author for this post.

Elly, woody

Reply | Quote

Yeah, I even had an update reset my homepage and default search provider to MS/bing without asking. Can’t remember which version of Win that happened to (I have everything from XP to Insiders 20h1).

It had been popping up the old box with the two radio buttons (recommended or not) with every update for a long time. And I had removed Bing as a search provider long ago.

Reply | Quote

This is first time i seen it on IE11 (whether Win 7, 8.1 or 10), and with web page not the regular pop window 🙂

similar situation is when i use unattend.xml answer file during setup to change IE settings, the first time i run IE after installation it ask you with pop up window if you want to retail custom settings or change to MS things

maybe this new change is to mitigate this issue

https://www.askwoody.com/2019/may-patches-may-block-ie-11-if-you-dont-have-default-search-provider-specifiedh/

Reply | Quote

Having similar symptom, only thing that I found that would help is here:
https://social.technet.microsoft.com/Forums/sharepoint/en-US/fbe5b01a-d5e9-45f9-8c18-aeaf2b6a3789/fresh-enterprise-1809-kiosks-are-prompted-to-change-homepage-to-msncom-and-search-to-bing-in-ie11?forum=ieitprocurrentver

 

Reply | Quote

Hey all you Fore Runners with Windows 10 ver 1803 and 1809

The June CU brings the new Windows Updater screen and update process we have been discussing here at AskWoody for several months while awaiting actual feedback as to what the screens look like, the Advanced options, and with the Pro version what Group Policy(ies) changed, if any.

So please provide “Detailed feedback” with screen shots if possible so we can finally know what Microsoft has actually provided us.

Many thanks in advance.

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

1 user thanked author for this post.

woody

Reply | Quote

Far as I can tell, nothing’s changed since my article two months ago:

https://www.askwoody.com/bombshell-updating-win10-will-be-better-really/

There’s a screenshot of the advanced options here:

https://www.computerworld.com/article/3400953/save-yourself-a-headache-make-sure-windows-automatic-update-is-off.html

Many unanswered questions, but the big one for me is why the options disappear when you set feature update deferral to 365 (or something lower?). It’s almost certainly a bug, but ya never know, eh?

 

Reply | Quote

The only thing I’m getting today is a Skype for Business update.

Before you wonder "Am I doing things right," ask "Am I doing the right things?"

Reply | Quote

Update, Skype failed but it rechecked and getting more now.

Before you wonder "Am I doing things right," ask "Am I doing the right things?"

Reply | Quote

W7 x86 : Good-2-Go !

Reply | Quote

Installed the new CU for 1903 a few hours ago. Everything seems to running normally.

Barry
Windows 11 v23H2

1 user thanked author for this post.

woody

Reply | Quote

Have you tried setting the feature update deferral?

Reply | Quote

Is there any particular urgency to patch now to address CVE-2019-0722?  Thanks.

Reply | Quote

If you aren’t running Hyper-V there’s nothing to worry about.

1 user thanked author for this post.

JNP

Reply | Quote

The SSU for server 2016 is once again prerequisite for the monthly update.

Maybe this is now becoming the norm. Time to start pre installing the SSU’s now.

Reply | Quote

Might have a look at this page, about half way down:

CVE-2019-0722

https://www.technoexpress.net/microsoft-releases-june-2019-security-updates-to-patch-88-vulnerabilities.html

Before you wonder "Am I doing things right," ask "Am I doing the right things?"

Reply | Quote

win10 1809 here, installed the kb4503327 without problem, but seem to have the event viewer error on both machines now

Reply | Quote

Windows 10 Pro 1809.
Deferrals : SAC/120/21.
Microsoft has pushed some old updates for me.

Reply | Quote

KB4465065 is an update to the Intel microcode.

Reply | Quote

1903 Home …. June Cum Kb4503293, Flash, MSRT, and C2R Stdn-Hm Office ’16 ran without issues.

Reply | Quote

[CraigS26]

anonymous wrote:

1903 Home …. June Cum Kb4503293, Flash, MSRT, and C2R Stdn-Hm Office ’16 ran without issues.

Does anyone have the patience to Recap what Win Update gives me now in 1903. (3) Critical and (39) Importants are known Updates but I just realized I don’t know exactly what I just installed. I’m closer to finding the Holy Grail than I am a Recap List of WHAT parts (ie) Kb4503293 Includes of (42) possible Updates.

FWIW, my last-known 4.72 Net Frmwk is Now 4.8, so the Update was Auto possibly in the 1903 Upgrade.

W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / Macrium Pd vX / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU = 0

• This reply was modified 5 years, 10 months ago by CraigS26.

1 user thanked author for this post.

geekdom

Reply | Quote

W10 1809, KB4465065 showed up this morning. Intel microcode update for my AMD processor.

Reply | Quote

Well, this would make sense in a “portable” installation, where you never know what hardware you’ll have on next bootup…

Reply | Quote

CraigS26 wrote:

FWIW, my last-known 4.72 Net Frmwk is Now 4.8, so the Update was Auto possibly in the 1903 Upgrade.

It is in  my Windows 10 Home x64 Version 1903 Build 18362.145, don’t know how far back it showed up.

Before you wonder "Am I doing things right," ask "Am I doing the right things?"

Reply | Quote

All .NET Framework are shown here:
https://dotnet.microsoft.com/download/dotnet-framework

.NET Framework 4.8 was released April 18, 2019, but as near as I can tell, was not released as part of Microsoft Updates.

If .NET Framework 4.8 is installed separately, then
2019-05 Security and Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 7 and Server 2008 R2 for x64 (KB4499406) must be installed after .NET Framework 4.8. Windows Updates prompts for KB4499406 installation.

————

Microsoft Visual C++ Redistributables are here:
https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

Microsoft Visual C++ 2015-2019 Redistributables are the latest, and have digital signature date of May 2, 2019. These redistributables are not included in the Windows Update queue.

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

2 users thanked author for this post.

woody, AJNorth

Reply | Quote

Addendum: .NET Framework 4.8 appears to be an update for Windows 10; it is not an update for Windows 7. If you have Windows 7, you must track down .NET Framework 4.8 yourself and install it separately.

Does anyone have information regarding .NET Framework 4.8 under Windows 8.1?

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

1 user thanked author for this post.

ashfan212

Reply | Quote

.NET 4.8 itself is not pushed or published through Windows Update yet

but if you manually install it, then you will get a separate security update for it through WU

1903 already have .NET 4.8 inbox, so you will always get the update (combined with .NET 3.5)

3 users thanked author for this post.

woody, AJNorth, geekdom

Reply | Quote

On W7 x64, up to date apart from this month while the dust settles. Although I do have .NET Framework 4.8 installed, I’m not being offered any updates for .NET at all. I find it hard to believe it doesn’t need any updates: when has that ever happened?

Reply | Quote

I did not see any .NET updates for June listed in the usual places.

Reply | Quote

[Ken Sims]

According to my notes, W7 x64 did not have .NET updates as recently as April 2019 (or if it did, I didn’t get them).  (And I also don’t have any for June.)

• This reply was modified 5 years, 10 months ago by Ken Sims.

Reply | Quote

Ken Sims, you said, “According to my notes, W7 x64 did not have .NET updates as recently as April 2019 (or if it did, I didn’t get them). ” I may be reading you wrong but there have been some .net updates for windows 7, recently. Here are Group B, SO updates.

Feb 2019 2019-02 Security Only Update for .NET Framework 3.5.1 for Windows 7 and Server 2008 R2 for x64 (KB4483483)
May 2019 2019-05 Security Only Update for .NET Framework 3.5.1 for Windows 7 and Server 2008 R2 for x64 (KB4495612)

If I misunderstood, my apologies.

Reply | Quote

I meant only that for the month of April specifically I did not receive .NET updates W7 x64, and that that was the most recent month (prior to June) for which I did not receive .NET updates.  I did receive .NET updates for some other months.

For 2019:
Jan – My notes are unclear.
Feb – I did receive .NET updates.
Mar – I did not receive .NET updates.
Apr – I did not receive .NET updates.
May – I did receive .NET updates.
Jun – I did not receive .NET updates.

Reply | Quote

[geekdom]

KB4499406 information, May 2019 update, is here:
https://support.microsoft.com/en-us/help/4499406/security-and-quality-rollup-for-net-framework

If you don’t have .NET Framework 4.8, you won’t see KB4499406 in the update queue.

You must have .NET Framework 4.8, to see KB4499406 in the update queue.

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

• This reply was modified 5 years, 10 months ago by geekdom.

Reply | Quote

I checked for updates today on wushowhide on both my desktop and laptop. Both have Windows 10 Pro, version 1809. SAC set at 365/20. The desktop shows the following;

1. kb4465065 – update for windows 10 v1809
2. kb890830 – windows malicious software removal tool
3. kb4503308 – flash player update
4. kb4503327 – cu for windows 10 v 1809

laptop only shows; kb4465065

Anyone know why laptop only shows the one update? Thanks for any info!

Reply | Quote

I think the laptop is showing only one update b/c your settings are set not to show quality updates for 20 days after release.

Check again – where is the quality deferral set on the desktop?

1 user thanked author for this post.

taftbaby

Reply | Quote

Thanks PK! Set the quality deferral to 0, ran wushowhide again. All the updates were there! Your knowledge is greatly appreciated! Desktop deferral was set at 0 btw. Thanks again!

Reply | Quote

So I wanted to hide two updates, kb4503327 & kb4465065. Followed your instructions and double checked every ‘click”. Set to “metered” etc. etc. Upon restart ran wushowhide, verified updates are hidden and not available to be hidden per your directions.When I open Settings/Updates and Security shows the ‘hidden” updates as pending install still.

Reply | Quote

Did you follow exactly the instructions in AKB2000013? You not only have to hide the updates, you have to clear rhe Windows Update queue afterward.

Reply | Quote

Or, after hiding selected updates, simply wait for Windows to update itself again then the hidden items will no longer show in Settings. Once they no longer show you are good. (If it shows in Settings, it will download and install if you hit the Download button).

Unfortunately Windows currently updates itself about every 15 – 20 hours so you’ll have to have some patience.

I usually let the Updates download when they come out, run wushowhide and hide the ones (mainly the new monthly CU) I want to wait for the Defcon rating on, then use my system as normal for that day (nothing will happen or go wrong unless you hit the “Check for Updates” button – a big no no, or the “Download” button).

The next day at some point, Windows will automatically check for updates and the hidden updates will disappear from Settings. If there were some you did not hide, they will be the only ones still there and then you can Download and install them.

Hopefully with the new Update procedure in 1903 and 1803/1809 with the June CU, we will be able to finally use the Check for Updates button and actually force Windows to refresh itself upon command which hopefully will do all the above immediately. Awaiting reports from the field.

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

1 user thanked author for this post.

taftbaby

Reply | Quote

Tex265 wrote:

I usually let the Updates download when they come out, run wushowhide and hide the ones (mainly the new monthly CU) I want to wait for the Defcon rating on

Something isn’t right here. If the updates download, they will install and you will no longer be able to hide them with whshowhide.
Perhaps the explanation could be clearer?

1 user thanked author for this post.

walker

Reply | Quote

PK you are correct!

I totally forgot that having Windows 10 Pro version, in addition to my info above, you also need to have the Group Policy for Windows Update set to 2 – Ask before downloading/installing. So updates show in Settings but do not download/install unless you select the Download button. This provides the delay necessary to hide updates and wait until the next automatic Windows Update.
(Basically followed your “formula” when I first found AskWoody last year).

The sentence “I usually let the Updates download when they come out, run wushowhide and hide the ones….” should say ” I usually let the Updates show when they come out, run wushowhide and hide the ones …..”

If you think this is now confusing or too complicated, feel free to delete or edit my original post above since my Edit period has past.

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

I followed the directions exactly in AKB2000013 but when checking Settings/update&Security/windowsupdate all updates are still showing.  WUshowhide shows them to be hidden.

Reply | Quote

Wanted to give you an update on trying to cleaCheck updr the Settings/Update and Security que. After doing all the steps in AKB2000013 was still seeing all updates even the ones I hid in wushowhide as pending download. So thought I should j be patient. So before turning pc off last night made sure I was on metered connection. This a.m., immediately run wushowhide and in hide it shows the two that should be there. In hidden shows the two I want hidden. Go to Setting/Updateand Security and it shows Nothing. Says all upto date, “Check for Updates”.  So I check update history. Nothing new installed.  So what happened? Who knows! So against all that everyone says “Do not click on Check for Updates” I clicked on Check for updates. WOW what a surprise! Only shows the two I wanted to download and install, so I did.First turning off metered. Then after install turned metered back on. The two I did not want to install are still showing hidden.  I accomplished what I wanted to do but do not know how in the world I did it!!!

Reply | Quote

Looking at Windows 7 these updates appear to be house keeping after the May Updates.

Reply | Quote

[EP]

It looks like the 2019-02 Intel Microcode Updates like KB4465065 for v1809 are no longer MS Catalog only updates as they seem to be pushed thru Windows Update and seemed to have gotten new WU metadata for them this June.

This Deskmodder.de blog seems to show a screenshot of the KB4465065 intel microcode update being delivered thru Windows Update (on a machine running Windows 10 version 1809):
https://www.deskmodder.de/blog/2019/06/12/intel-microcode-update-juni-2019-fuer-windows-10-1809-1803-1709-1703-und-darunter/

for those who do not need these new intel microcode updates (especially for those using AMD based systems), use wushowhide.diagcab to hide/block these updates

• This reply was modified 5 years, 10 months ago by EP.
• This reply was modified 5 years, 10 months ago by EP.

Reply | Quote

Unless I’ve been seeing things yesterday, I think it got deployed on my PC on 1809 this exact way as well. Will check later when will boot it up and report back.

Reply | Quote

The Intel microcode patches, in my experience, are not showing up in wushowhide this month on 1803 or 1809. So I have not found away to hide them (I have GP set WU=Enabled, 2). They show up in the queue in WU, but the usual clearing of the cache does not seem to remove them from the queue.

What I have had to do to avoid them is clear the SoftwareDistribution\Download folder, run Disk Cleanup, then clear the cache according to AKB2000013. Long way aroung but I have managed to avoid them.

Reply | Quote

On Win 10 1809, updated yesterday 6/12 and got the CU KB4503327, and when machine updated today, it got downloaded and installed again. Same thing happened with one of last month’s updates. Saw that another person had the same issue, wondering if it is happening widespread?

Reply | Quote

Same here – after reboot it got re-downloaded and reinstalled again asking for yet another reboot – and indeed I’ve witnessed it month-two-three (?) before.

I’ve read somewhere it may be something to do with updated Servicing Stack updates re-released then and installed as well.

But I also installed something manually yesterday which might have clashed with this update’s auto-deployment.

Reply | Quote

Some of the recent CUs have to go through two install cycles. It may be b/c the Servicing Stack has to be installed first by itself, then the CU. There is a new Servicing Stack for 1809 in June which might explain it.

Reply | Quote

Thanks PKCano. Makes sense, sort of, that a Servicing Stack would need to be installed first, but why can’t MS figure out a way to update that prior to the CU? Last month’s CU installed twice as well. Hopefully this doesn’t become the “new normal”. It could be a time and bandwith waster, especially if it is a large update.

Reply | Quote

but why can’t MS figure out a way to update that prior to the CU? Last month’s CU installed twice as well.

C’mon! We’re talking about MS here! 🙂 🙂

2 users thanked author for this post.

walker, Lars220

Reply | Quote

I have just noticed that Microsoft Outlook 2010 junk mail filter junked the regular Microsoft email advising of the monthly rollup patch. Microsoft junks Microsoft. In my slightly twisted mind, I find that quite funny!

Chris
Win 10 Pro x64 Group A

1 user thanked author for this post.

TaskForce141

Reply | Quote

[jayinalaska]

Had a Microsoft Security Advisory email this evening. Microsoft released Servicing Stack Updates today for Windows 10 1903 (KB4498523) and Windows Server 2019 Server Core (KB4504369).

EDIT: It looks like I jumped the gun on those links. Those still point to the 5/29/2019 SSU. I got the links from https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/ADV990001. It looks like the new KB# for 1903 is 4500109, but it’s currently redirecting to KB4498523. The 1903 SSU download from the Update Catalog still points at KB4498523. Not sure what to think. I got the email a couple of hours ago.

• This reply was modified 5 years, 10 months ago by jayinalaska.
• This reply was modified 5 years, 10 months ago by jayinalaska.

Reply | Quote

[EP]

jayinalaska wrote:

Had a Microsoft Security Advisory email this evening. Microsoft released Servicing Stack Updates today for Windows 10 1903 (KB4498523) and Windows Server 2019 Server Core (KB4504369).

EDIT: It looks like I jumped the gun on those links. Those still point to the 5/29/2019 SSU. I got the links from https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/ADV990001. It looks like the new KB# for 1903 is 4500109, but it’s currently redirecting to KB4498523. The 1903 SSU download from the Update Catalog still points at KB4498523. Not sure what to think. I got the email a couple of hours ago

no jayinalaska.

The KB4498523 SSU for v1903 is newer than the KB4500109 SSU.

Microsoft said so here:
https://support.microsoft.com/help/4498523

Update replacement information

This update replaces the previously released update KB4500109.

AND KB4503469 for Server 2019 Server Core is for v1809 version

• This reply was modified 5 years, 10 months ago by EP.
• This reply was modified 5 years, 10 months ago by EP.
• This reply was modified 5 years, 10 months ago by PKCano.
• This reply was modified 5 years, 10 months ago by PKCano.

1 user thanked author for this post.

jayinalaska

Reply | Quote

EP,

Thank you for correcting my mistakes. I admit to great confusion and to not reading all of Microsoft’s pages closely enough. What threw me off was the date at the top of the KB4498523 article, which is 5/29/2019. That convinced me Microsoft had made some kind of Friday afternoon error and confirmation bias set in, especially after I saw the same date on the Microsoft catalog page. These “discoveries” were all after I had made my original post and I was anxious to correct my “errors”.

As for the Server Core SSU update, the similarities between Windows Server 2019 (Server Core Installation) and Window Server, version 1903 (Server Core Installation) tripped me up.

My apologies.

Reply | Quote

laidbacktokyo wrote:

UPDATE: well, I’ve duly try to apply that official m$ script as above https://support.microsoft.com/en-us/help/4508640/event-viewer-may-close-or-you-may-receive-an-error-when-using-custom-v both thru Power Shell x64 6.2.0 as well as thru the native win7 PS w/o any good result. The issue persists, so again rolling back to May 2019 Preview.

Martin Brinkmann presented (via Deskmodder) another solution :

Open File Explorer on the device.
Navigate to the following path: C:\ProgramData\Microsoft\Event Viewer\Views
Backup the content of the folder. The next step deletes the custom views and you may want the backup to restore the views when Microsoft fixes the issues.
Delete all View_X.xml files in the folder (it starts with View_0.xml and increments the number by 1 for each file).
Start the Event Viewer after deleting the files.

https://www.ghacks.net/2019/06/12/windows-10-event-viewer-error-after-installing-kb4503293-and-kb4503327/

Moderator Edit and note: Quote all material that isn’t yours. Not doing so may cause your post to be deleted without notice.

Reply | Quote

W10 1803 x64.   
Installed June cumulative update KB4503286, stable for two days.  Now using WUMgr utility to check for, select/discard, and install updates.   Seems to provide more control than the WUSH utility procedure.

Reply | Quote

Window 7 Pro SP 1… I’m showing in WU, KB4503292 roll up, which I don’t see mentioned in the Master Patch List. Am I being offered something different than everyone else or did I overlook it ?

Reply | Quote

KB4503292 is the June Rollup. It is listed on the fourth page of the .PDF file listed at the top of the Master Patch List page.

Reply | Quote

Sorry..I get kinda lost, but thanks for the answer. I’m assuming that defer means to skip this June update altogether ?

Reply | Quote

DEFER MEANs “put off,” “do not do now,” “wait.”
DOES NOT MEAN skip altogether.

Reply | Quote

Dear Abbodi86!

Do we need to install KB4503269 (June 2019 Windows 7 SP1 Security-only update) before KB4508772 or is it enough to install only KB4508772 to a Windows 7 64 bit system, that has no 2019 June updates installed on it? With one word: does KB4508772 replace/supersede KB4503269?

I think yes, because of the following:

– In the official description of KB4508772 we can read this: This update for Windows 7 SP1 and Windows Server 2008 R2 SP1 includes the quality improvements from KB4503269 (released June 11, 2019), in addition to these key changes: …”

– If we compare the file information of KB4503269 and KB4508772 updates, the similarity is conspicuous.

If I am right, then these two updates have the same connection as KB4338823 (July 2018 Windows 7 SP1 Security-only update) and KB4345459, or as KB4512486 (August 2019 Windows 7 SP1 Security-only update) and KB4517297: in both cases, the second one replaces/supersedes the first one.

After all these, what is the truth? Am I right, that KB4508772 replaces/supersedes KB4503269?

If yes, then it would be useful to provide this information at AKB-2000003 as well.

Thank you very much for the help!

Reply | Quote