Here’s where we stand with bugs in this month’s Patch Tuesday patches

Topic

New Reply

Microsoft’s given short shrift to the Start Menu critical error – but I see it popping up all over. Search isn’t working right – but that may be linke
[See the full post at: Here’s where we stand with bugs in this month’s Patch Tuesday patches]

3 users thanked author for this post.

abbodi86, AlbertMcCann623, lurks about

Reply | Quote

Replies

Gotta love you Woody. You must spend an extraordinary amount of time every month searching the deepest,darkest corners of the web to come up with as many problems as you can. ( I would put a smile here but i dont know how)

Color me a happy camper with none of these problems from the updates.

 

Barry
Windows 11 v23H2

1 user thanked author for this post.

woody

Reply | Quote

It’s great that you don’t have problems. Keep posting!

There’s a reason why I gather bugs like roses in May. There doesn’t seem to be a single repository for bug reports – they’re scattered all over the place, and only a few of them are ever officially acknowledged. By sticking them here, I hope that people who run into problems can at least discover that they’re not alone — and hopefully get their systems fixed.

13 users thanked author for this post.

rexr, wavy, Pim, abbodi86, LH, Geo, SueW, LHiggins, Charlie, bottomlineusa, Lars220, Alex5723, Barry

Reply | Quote

And that is why i keep reading. It’s nice to know that if i ever do have a problem i will see it first on this site.

Barry
Windows 11 v23H2

1 user thanked author for this post.

woody

Reply | Quote

I just added this to the main blog page:

UPDATE on VMWare: Peter Deegan, over at Office Watch, has more details on the VMWare bug. He’s looking at KB 4517211, which is the “optional non-security” September cumulative update to Win10 version 1903. It isn’t clear to me if this is the same bug we’re seeing with the October Patch Tuesday patch, but it sure sounds suspicious. If you’re using VMWare and getting the error “VMware Workstation Pro can’t run on Windows,” check it out.

Reply | Quote

The real fun was brought to users with Hyper-V VMs running 1903. After installing KB4517389, VMs hang on boot because the new and broken Hyper-V GFX driver (introduced in 1903, bugs reported back in May to the Feedback Hub, nothing fixed as of today) crashes. Best of all, after uninstalling KB4517389 via Windows built-in recovery tools (pulling the virtual plug 2 two times to get into the recovery console? Really, Microsoft?), Windows Update gets mad and hogs on the CPU forever. The workaround? Ditch the VM and build a new one from scratch; and don’t install 1903 even if previous versions run out of support soon! Better running an unsupported version than a version that has severe memory leaks (new Hyper-V GFX driver) and in the end, won’t boot.

2 users thanked author for this post.

nazzy, woody

Reply | Quote

Didn’t MS say something real recently about social responsibility and patching? Maybe they should stop kvetching about what users do and get their own house in order. </RANT>

2 users thanked author for this post.

SueW, Charlie

Reply | Quote

Ya know, except on rare occasions, when you buy a brand new car you expect it to run without problems for at least the first three years of normal use.  Thank goodness MS isn’t in the car manufacturing business!

Being 20 something in the 70's was so much better than being 70 something in the insane 20's

1 user thanked author for this post.

rexr

Reply | Quote

Has anyone installed KB4520005, the October cumulative update for W8.1 and Server 2012R2? I am not finding any reports of issues with this KB but it is early days yet. As usual, most of the anguish seems to swirl around W10 in its various incarnations.

Reply | Quote

I’ve installed it on a test device with a report over here
Bit early to consider installing it as we are at MS-Defcon1.
Best to wait ’til MS-Defcon level rises to 3 or above..

Windows - commercial by definition and now function...

1 user thanked author for this post.

woody

Reply | Quote

No problems yet (see here) but Microfix’s right, we’re at MS-DEFCON1 (WAIT!).

1 user thanked author for this post.

woody

Reply | Quote

I have installed KB4520005 on a test machine also with no problems.
But if you don’t have a test environment to try it on, you should WAIT till the DEFCON number is 3 or greater.

1 user thanked author for this post.

woody

Reply | Quote

A family member recently acquired a new laptop with v1903 PRO pre-installed.  I am running v1809 PRO.  But I am responsible for supporting the v1903 machine.

Well, when I looked at the Advanced Options setting for Windows Update on v1903, I found them to be mind-boggling.

I’m a daily Ask Woody reader so I naturally turned to Woody.  These settings seem to be in a state of flux and so I had difficulty finding them on the site.  Woody kindly pointed me to https://www.computerworld.com/article/3444484/as-patch-tuesday-approaches-turn-off-automatic-update-temporarily-and-especially-disengage-ie.html
and
https://www.computerworld.com/article/3436776/time-to-install-the-august-windows-patches-but-watch-out-for-the-bugs.html .

I am making this post so that others see it but I think a sticky on the front page would be a useful idea.  Although the content (i.e. settings) would change, readers could always reach  that content from the same place.

Reply | Quote

Read through this thread about Advanced Settings deferral pulldowns in the Windows Update GUI which have disappeared after v1809.

1 user thanked author for this post.

CyGuy

Reply | Quote

Would I be right in thinking the problems are mostly with 1903 and not the older versions like 1803 and 1809?

I follow this site to determine what and when to install and I always do it by going to the catalog and downloading from there. Never ‘ seeked’ even though I have Professional.

Reply | Quote

Most of the problems we’ve seen with the Oct updates so far have been with Win10 v1903. But it is still too early to say there are no problems with the other versions of Windows. It’s only been three days since Patch Tues.

That’s what the DEFCON System is all about. Waiting (and letting others Beta test).

Reply | Quote

I’m running 1809 Pro.  I had the start button won’t work problem, the Outlook won’t start problem, the search won’t work problem AND all the icons on the Task Bar disappeared.

I ended up uninstalling KB4512578 to fix my machine.  I also ran the Microsoft utility to hide this update until further notice.  It’s been three days and so far so good.

2 users thanked author for this post.

woody, PKCano

Reply | Quote

[woody]

YIKES!

First time I’ve heard of that…. I’m going to post this on the main blog page to see if I can get confirmation….

By any chance, do you have web search turned off? That seems to be a common theme with many 1903 bugs.

• This reply was modified 5 years, 7 months ago by woody.

Reply | Quote

Yes.  Web Search is turned off.

Reply | Quote

If you install the October cumulative update, does the problem persist?

Reply | Quote

VMware has released a statement on VMware Communities about recent Windows 10 1903 updates preventing VMware Workstation (15.0.x and earlier versions) running :

Statement for Workstation 15.0 and earlier being blocked by Microsoft KBs

Did Microsoft not tell anyone (including VMware) that it decided to block VMware Workstation 15.0.x and earlier on Windows 10 1903 and later?

One more reason for me to stay away from Windows 10 (1903) at this time. I depend on VMware Workstation for my work and entertainment needs and although I am running 15.0.4 on my main system running Windows 8.1, I still need to run older versions of VMware Workstation (10.0.7 / 12.5.9 on Windows 7) as it seems to me older versions of VMware Workstation works better with older versions of Windows (XP / 98) in virtual machines.

I would be incensed if I am running Windows 10 1903 and still working with an older version of VMware Workstation. As stated in the article Woody links to : Some customers need to stay with earlier versions of VMWare Workstation for compatibility with certain types of hardware (or other valid reasons).

Hope for the best. Prepare for the worst.

1 user thanked author for this post.

woody

Reply | Quote

How to bypass the “compatibility” issue that Microsoft imposes on VMWare Workstation 12 Pro, or others….  w/o patching….

Start-> Run-> Compatibility Administrator

Then navigate the tree to “System Database”\Applications\

Then locate the entry “VMWare Workstation Pro”

In that node, at the right pane you will see “vmware.exe” (or vmplayer.exe) and below that an entry that says “AppHelp – HARDBLOCK”

At this point this means the application will be blocked immediately.  T0 bypass this, right click the entry, and choose “bypass”.  Then hit Save, and you can exit.

Then you can run VMWare w/o any issues.  Worked out perfect for me!!

1 user thanked author for this post.

woody

Reply | Quote

From personal experience after applying an August update, I think you should have as many ways as possible to login.  I usually login with a PIN, but found after restarting that neither the PIN or the Microsoft account working, and the local account was the only way to login.  It took considerable tries at various methods until I got the PIN login working again.

Reply | Quote

Sorry, my reply above was put in the wrong place!

Reply | Quote

Concerning the shell/start menu/search/action center issues: After I’ve escalated this to MS engineers it’s confirmed. A fix is planned for end of October 2019. See the discussion at https://answers.microsoft.com/en-us/windows/forum/windows_10-start-win_menu/start-menu-showing-critical-error-after-installing/ae473b3c-ae57-4e1a-8c55-c727cd16fabd?messageId=5d035ddd-841c-4569-aaac-eed2c261cd9c&auth=1&page=3 for further details.

For those affected: I’ve outlined some workarounds and the root cause within my blog post https://borncity.com/win/2019/10/12/windows-10-fixes-for-october-2019-start-menu-issues/

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

2 users thanked author for this post.

rexr, woody

Reply | Quote

Excellent!

Man, you’re getting some response while the folks over here don’t seem to get anything but crickets. Are you working with MS Germany?

Reply | Quote

Following October8th updates on windows 2016 standard server the start menu now will not open for normal domain users and also the logon time has increased presumably as it’s having trouble loading the shell, all we get is a black screen after the profile loads for a couple mins whereas usually we have around a 30 second login.  Date/time also won’t open from the taskbar or the action button won’t do anything, search also doesn’t work.  Right click on start button does work

for now we’ve reverted back to a snapshot from september which doesn’t have this issue.  I’ve tried to install the October updates twice and same problem both times on server master images in different regions.  We use RDSH for full shared desktops so having a working start menu is a big requirement.  This is the first time it’s broken in 2 years.

do we know if the windows fix end of October is also going to be for windows 2016?

thanks

steve

Reply | Quote

my experience with the start menu issue is inconsistent though. the first time installed the patch was wednesday morning. I got the start menu error then I reimage my machine as I thought my vmware issue will be fix if i start fresh (which it didnt). the next time i installed it and another 2 more machines, I never get it anymore and the 2 more added machines. Let see

Reply | Quote

[gborn]

woody wrote:

Excellent!

Man, you’re getting some response while the folks over here don’t seem to get anything but crickets. Are you working with MS Germany?

Not really – still had the Windows Insider Most Valuable Professional (MVP), but after my sports accident with spine injury in 2015 I withdraw from attending any Microsoft event – also in Germany. I’m an independent blogger – and I try to get as less close and as less information as possible from inside of Microsoft  – because then I would be bend by NDA.

I have a brain, some experience (from DOS 1.0x) and I am still a Microsoft Answers community moderator – so I’m able to escalate things. And I play ‘billard’ with such issues: Write an English blog post with an analysis – then I’m searching an US MS answers forum post, add my analysis with a link to the blog post and escalate it to all Microsoft moderators asking to forward it to the developer. In most cases it helped – because Microsoft’s engineers find a single source describing the beef – and maybe the MVP title helps a bit ;-).

But: Your mentions at ComputerWorld also helps a lot. So we gain publicity with our topics – and not to forgot to mention Susan Bradley and Barb Bowman – and @PhantomofMobile & Kirsty at twitter. It’s a kind of team play (also with my blog readers, especially mentions EP & pkcano from askwoody, and blog reader Bolko from Germany, who are a valuable sources sharing their thoughts with me). So I just have to curate things in a proper manner (I’m the ear and mouth of many peple) – it’s classic crowd sharing – and play the billard ball in the right manner ;-).

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

• This reply was modified 5 years, 7 months ago by gborn.

9 users thanked author for this post.

Kirsty, Fred, Chris B, woody, DLivesInTexas, rexr, AJNorth, satrow, PKCano

Reply | Quote

Perhaps this has been asked already, but I have failed to find the same question by looking around this site, so here it goes:

I just have had a look to see what was up in Windows Update (set to let me know but not install unless I say so) and found there, checked, the SHA-2 KB4474419 that, I seem to remember, was released in June and I have most likely installed already, as I think I’ve been doing with all the SHA-2 patches released until now.

But, just in case, I looked into the “installed updates” list, and the result of the search was: “not here.”

So now I am wondering: Might I have simply forgotten to install this patch and now have a false recollection of having done so already?

Or could it be that I installed it and a later SHA-2 patch removed and replaced it?

Or, maybe, something completely different is going on?

I am in no hurry to install any September updates just yet, but I would like to get some clarification on this issue before it is high time to go ahead and patch. So: Thanks, in advance, for any practical answers.

Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).

MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV

1 user thanked author for this post.

Fred

Reply | Quote

“Didn’t MS say something real recently about social responsibility and patching? Maybe they should stop kvetching about what users do and get their own house in order.”

This comment is oh so tru

I have got here another pc from a friend with a small administration office, completely wrecked ; he didn’t touch the search button, for sure. Startmenu and Notificationmenu and some precesses in the backgroun simply don’t work anymore.
Needs to collects his email by Outlook (what he does not want to), and has to send his mail with Thunderbird. The other way around , or fetch & send by one program just is not working. This guy is just loosing his faith, and spending his money in pc repair, and all for nothing, so it appears.
*So this is nice puzzle to solve, I hope,  in the monday (NOT!)*
.

* _ ... _ *

Reply | Quote

Not sure what happened to your system. But there are several observations:

• Microsoft has updated the SHA-2 patch (afaik) several times
• I receive frequently comments from German blog readers using Win 7 and failing to install updates. They are facing crypting errors and my suggestion to re-install KB4474419 helps in many cases.

So just install KB4474419 – if it’s already there, Windows Update will notice that and will give you a notification.

1 user thanked author for this post.

OscarCP

Reply | Quote

Have you tried listing them in HTML and then searching?

Open an admin Command Prompt.
Change to a temporary directory: cd %temp%
Run this command: wmic qfe list full /format:htable > hotfixes.html
Then this one to open the file in your browser: start “” hotfixes.html
Search via Ctrl F.

cheers, Paul

Reply | Quote

Not sure if this is the right place to post, but part of that is because I don’t know which KB is actually causing my issue. I’m on Win7 x64 and after installing latest cumulative updates (whatever came out between June and now), so definitely kb4519976, my WiFi system tray icon is not showing me connected even though I am; it merely shows the “connections available” icon (greyed out wifi icon with yellow/gold store in front of it). I have tried reinstalling (and deleting) my wifi drivers, deleting the connection in the wizard, etc., but I remain connected and the icon doesn’t show the connection bars as usual. No hardware changes. Never had this before.

1 user thanked author for this post.

woody

Reply | Quote

It’s a  new one on me, too.

Another brick in the wall….

Reply | Quote

<h3>It’s a mighty mess.</h3>

Anyone out there still think we Group B Win7-using refuseniks are “willing to bite the hand that feeds” us, as Woody so provocatively put it in AKB2000003?  Surely even he must be willing to concede by now that we really aren’t talking about a hand, rather the stinky, hairy paw of the Big Bad Wolf!

As for me, I am in a particularly sweet mood these days.  Ever since I foolishly sacrificed a perfectly good Win7 Home Premium laptop over three years ago to beat the deadline for the free “upgrade” to the stripped-down edition of Win10, I have been kicking myself.  I have followed this tale of woe in Woody’s masterly CW articles, not just for useful Win7 advice (for my desktop), but also to keep from falling into more Win10 traps on my laptop.  I needed to keep it going as my fall-back.

Just a couple of weeks ago, purely by accident, I stumbled across Restore Acer/eMachines to factory with PQService Partition without Alt+F10.  Long story short,  I dumped my Win10 and was able to recover my original pre-SP1 Win7 OS!  Two weeks later, not just the Win7 OS but also my programs line-up are on par with my desktop, and I have a clone as back-up again!  This is my first personal experience with resurrection!  The nightmare of the past three years turned out to be just a particularly nasty dream!

Of course, I had jumped from Group B to Group W as of Dec 2017, so I am now blissfully disengaged from this M$ nightmare.  Yes, Win7 end-of-support is just around the corner, but like Canadian Tech, I expect to keep these machines going for another five years or more.

Speaking of CT, if you are listening, I followed your Sep 20, 2018 very helpful list of updates-to-avoid in rebuilding my laptop OS, thank you.  Just one of your pariah updates gave me trouble, KB2999226.  After I uninstalled it, two of my programs (including Libre Office, a biggie) threw fatal missing .dll errors.  When I reinstalled a later edition of Libre Office, I saw the installation software noticed that KB2999226 was missing and automatically installed it.  This also soothed the other program that had objected.

I assume you put that KB on your avoidance list for good reasons other than as a source of essential .dlls.  Is there some other way I can get those .dlls?  Thanks!

Reply | Quote

After recent patches, Dell Latitude E6230 was reporting “unrecognised battery”. Restored from backup of 1809 17763.504 and the battery is fine again. Can’t prove it’s the patches but it seems pretty likely.

Reply | Quote

[Wayne]

1903, OS Build 18362.356     Last 3 quality updates: Flash, Net 3.5 and 4.8, and CU on 22-Sep-19 after last raising of Defcon number.

So here I was—I think—at the end of the triple-click three-week “Pause updates for 7 more days” due tomorrow, 21-Oct-19, and still on Defcon 1. Happily, clicking it again just now got me seven more days’ delay, to 28-Oct-19, instead of some risky update or necessary restart or whatever we’re supposed to get when our deferral option runs out.

Does anyone know what happens with the next click? I have the vague understanding that there’s a limited number of times I can use the 7-day deferral before it’s refused and the updates start and the deferral option gets reset. I certainly could be wrong, happily so, but that’s my impression.

Any chance Defcon will go up before the next CU’s in November?

• This reply was modified 5 years, 6 months ago by Wayne.
• This reply was modified 5 years, 6 months ago by PKCano.

Reply | Quote

It sounds like you are using “Pause” not deferral – there is a BIG difference.
In the case you are clicking on “Pause,” the maximum is 35 days (five clicks).
When the “Pause” time is up (or when you click to end it earlier), you have to install the pending updates before you can “Pause” again.

1 user thanked author for this post.

Wayne

Reply | Quote

[Wayne]

Then I have one more click to use. Nice to know!

Yes, I meant “pause” throughout. Forgot that deferral is a separate operation, probably not available in my Home version anyway.

• This reply was modified 5 years, 6 months ago by Wayne.

Reply | Quote

Wayne wrote:

Does anyone know what happens with the next click?

You can get a total of 35 days deferral, and that’s the limit.  Doesn’t really matter when you click the pause button.  Once the 35 days are up, you have to accept all the updates you’ve deferred before you can pause updates again.

I don’t use it, but that’s the way it’s supposed to work.  I’m a Seeker (cannon fodder) who regularly checks for updates.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

1 user thanked author for this post.

Wayne

Reply | Quote

 

On my Win 7 Pro 64-bit, in Windows Update, KB4519976 now has a “Published” date of Oct 17, 2019.

So – how does it differ from the original version that had been dated Oct 8?

 

Reply | Quote

See Woody’s explanation here.

1 user thanked author for this post.

glnz

Reply | Quote

Thanks again, PKCano.

Reply | Quote

Can you tell us which October security patches we’re missing out on by not patching.

Saying don’t patch isn’t enough, we need to know what were trading off security wise by not patching.

Reply | Quote

I believe Microsoft, the author of the patches you ask about, would be the authority of what is included in the patches line by line. You can review the information they are willing to share in their documentation. If you are as interested in Woody’s opinion of content as you are his warning…

What to do? Wait.

There’s exactly zero reason to install the October Patch Tuesday patches just yet. If you’re concerned about the CVE-2019-1367 zero-day that saw so much publicity (and still hasn’t been exploited in the real world), you’re better off using a browser other than IE and changing your default browser to something else — which you should’ve done long ago.

from the Computerworld article linked in the blog topic we are commenting on.

Reply | Quote

Did they remove the October rollup KB4519976 from windows update? I haven’t seen it for a couple of days now, I just see the September rollup instead. Along with KB4474419 and the MSRT October on both computers.

Reply | Quote