Patch Lady – are you seeing issues with KB4556799?

[Susan Bradley]

KB4556799 I’ve got it installed here with no issues.  But I’m seeing forum posts about issues…but like last month… nothing widespread… nothing t
[See the full post at: Patch Lady – are you seeing issues with KB4556799?]

Susan Bradley Patch Lady

6 users thanked author for this post.

abbodi86, Elly, woody, rontpxz81, GreatAndPowerfulTech

Reply | Quote

[Bundaburra]

Have installed KB4556799 on two PCs – a Toshiba laptop and a custom built desktop, both running 64 bit 1909, Pro.  No issues whatever on either one.  Installation was routine, and none of the effects described has happened.  No BSODs, no video symptoms, Realtek audio is fine.  But when you think about it, the number of different hardware/software combinations out there must be huge, and it’s really not surprising if a minority of such combinations don’t like what they are given.  It’s easy to condemn Microsoft for a bad fix, but it must be very difficult for them to cover every possible permutation of  hardware, system software and application software when addressing a particular issue.

Windows 10 Pro 64 bit 20H2

• This reply was modified 10 months, 3 weeks ago by Bundaburra.

Reply | Quote

[F A Kramer]

I have a rock solid HP computer that has never given me a Blue Screen…. until about the 13th of May 2020, when I got one with the KMODE EXCEPTION NOT HANDLED error and no other information (no error codes, etc.). Since then this has occurred repeatedly, sometimes immediately after booting up and reaching the desktop, sometimes when I am selecting an application, and often when I am doing nothing on the computer.

I “reset” the computer with an entirely new installation of Windows 10. Have not yet installed any of my programs. Still get the same failures, about once every hour. I hope to get this report typed and sent off to AskWoody before another failure!

2 users thanked author for this post.

sledgewick, rontpxz81

Reply | Quote

[VulturEMaN]

https://support.microsoft.com/en-us/help/4556799/windows-10-update-kb4556799

We have seen social media and news reports related to various issues with KB4556799.
We are actively engaged with customers who are reporting issues. To date, we have not seen widespread issues reflected<span class=”x-hidden-focus”> in telemetry, support data, or customer feedback channels. We continuously investigate all customer feedback and are closely monitoring this situation.

That’s the MS “investigating” post.

We recently turned off driver updates across our company through WSUS because of some problems with video drivers and we don’t need that during Covid Times™. Last week, about the same time as this release, we had 4 users with audio problems reported. What we ended up finding was that HP Support Assistant had rolled out an updated driver to deal with a vulnerability:

https://support.hp.com/us-en/document/c06622884?hprpt_id=HPGL_ALERTS_2059454&jumpid=em_alerts_us-us_May20_xbu_all_all_2183698_2059454_LaptopsandHybridsPointofSaleSystemsDesktopsWorkstationsTablets_critical__/

But what was interesting was that all 4 of our laptops with issues were zBook 14u/15u G5’s. G5’s aren’t on the list of who was supposed to get this fix, except for the 15v, which is TOTALLY different hardware from the ‘u’ models.

Needless to say, we’re uninstalling HPSA agency-wide so we don’t have remote broken laptops en masse. Either way, wake me when someone’s determined that this was all Mfgr driver pushes to deal with the vulnerability that I linked to, and nothing to do with that patch.

1 user thanked author for this post.

woody

Reply | Quote

[woody]

That’s the same notice MS posted last month….

The Windows Release Status information page refers to last month’s cumulative update – doesn’t appear to be updated.

• This reply was modified 10 months, 3 weeks ago by woody.

Reply | Quote

[_Reassigned Account]

I’ve used PC’s for decades, back when drivers were manually installed, software typically did not auto updates and Windows certainly didn’t just install them automatically. I think it was good experience because back then we knew a bit about the OS, our devices and how to maintain them. Now it seems many are not able to install a driver, or uninstall a broken update let alone run system scans. Obviously I think Microsoft made a mistake telling us all that “we got this” so we don’t have to do anything. Yet when it does go wrong, many don’t know what to do? For myself I would gladly go back to installing my own updates, drivers, and app updates.

1 user thanked author for this post.

LeonW

Reply | Quote

[Susan Bradley]

https://forums.dc3.com/showthread.php?13157-How-to-recover-from-database-error&fbclid=IwAR3IpDArAmog9ItasnVo16b_xtodHk2fD8FAS_kxGvpjwYF6y2fxdlpQDUk

Microsoft needs to actively engage with him.

Susan Bradley Patch Lady

2 users thanked author for this post.

GoneToPlaid, woody

Reply | Quote

[rontpxz81]

Does it seem in reports that it is primarily HP computers effected?

Reply | Quote

[b]

Susan Bradley wrote:

Windows 10 KB4556799 update causes BSOD & Outlook search issues, changes default font, switches PC to S Mode & more issues, report users

The Outlook search issue mentioned at Windows Central is not related to KB4556799.

It was an Exchange service issue, only affecting on-premises users using non-modern authentication, which has just been fixed for most users:

Reports that this month’s Outlook update knocks out Search via Exchange Server

2 users thanked author for this post.

Elly, woody

Reply | Quote

[Perturbance]

I’m an HP Obelisk desktop owner and have been fighting KMODE EXCEPTION NOT HANDLE BSODs for the past two weeks.  Started the weekend of May 9.  At that time I blamed recently-installed Intel updates to their eXtreme Tuning Utility (XTU).  Uninstalling that didn’t fix the issue, but a System Restore to a point before the XTU update did.

My system remained stable for 6 days, then starting the same BSOD loop as before. Another System Restore kept me stable, but this time only for about 36 hours before commencing the crash loop again.

For me anyway, the problem appears to be a conflict between HP software/drivers and Windows Defender.  In the HP support forums there’s a mega-thread of desktop and laptop owners encountering the issue.  Some of the posts there have instructions on how to disable Defender via registry edits, pushed in via the Recovery Console.  I ran those steps on Tuesday, and have been stable since.  The only downside is finding an alternative antivirus solution.

When the BSODs happen, I can’t even get in to Safe Mode.  Once the Windows login screen appears, even moving the mouse appears to trigger a crash.

1 user thanked author for this post.

woody

Reply | Quote

[F A Kramer]

My computer is an HP Omen. I did a reset with a “clean” installation of Windows 10, which then went back to HP’s initial setup as well. This reinstalled the trial version of McAfee. So I am not using Windows Defender at the moment yet I continue to get the same BSOD occasionally and randomly. From other comments, I suspect that HP computers are a major target.

1 user thanked author for this post.

woody

Reply | Quote

[woody]

From Mayank Parmar on Twitter:

HP BSOD appears to be Windows Defender related and turning off Defender resolves the problem. Interesting.

From @sumitdhimanmvp on Twitter:

Three common problems I noticed:

1. BSOD 1E with HP machines running Windows Security

2. Mysterious deactivation of Windows

3. Error code 0x8024a105

2 users thanked author for this post.

F A Kramer, Perturbance

Reply | Quote

[numike]

All systems are go but remember I really dont know what Im doing.  I will say that I was having problems with my computer i.e. flashing black screen and I did everything to try and remedy it. I got to the point where I said forget this and brought my system back to its factory settings and rebuilt stuff I had on the computer.  HOWEVER I did not bring back all the software stuff that I  had to clear out registry errors malware etc. because I believe now they were the problem.  I only have Kerish Dr Kaspersky and Windows security.  AND I do not have any of those restore programs e.g. macrium reflect just the old fashioned external hard drive back up

Windows 10 Professional (x64) Version 1909 (build 18363.836)

KB4556799 5/19/2020 Update for Windows 10 (KB4556799)
KB4497165 5/10/2020 Update for Windows 10 (KB4497165)
KB4497727 5/10/2020 Security Update for Windows 10 (KB4497727)
KB4498523 5/10/2020 Security Update for Windows 10 (KB4498523)
KB4503308 5/10/2020 Security Update for Windows 10 (KB4503308)
KB4508433 5/10/2020 Security Update for Windows 10 (KB4508433)
KB4509096 5/10/2020 Security Update for Windows 10 (KB4509096)
KB4515383 5/10/2020 Security Update for Windows 10 (KB4515383)
KB4516115 5/10/2020 Security Update for Windows 10 (KB4516115)
KB4517245 5/10/2020 Update for Windows 10 (KB4517245)
KB4521863 5/10/2020 Security Update for Windows 10 (KB4521863)
KB4524569 5/10/2020 Security Update for Windows 10 (KB4524569)
KB4525419 5/10/2020 Security Update for Windows 10 (KB4525419)
KB4528759 5/10/2020 Security Update for Windows 10 (KB4528759)
KB4537572 5/10/2020 Update for Windows 10 (KB4537572)
KB4537759 5/10/2020 Security Update for Windows 10 (KB4537759)
KB4538674 5/10/2020 Security Update for Windows 10 (KB4538674)
KB4541338 5/10/2020 Security Update for Windows 10 (KB4541338)
KB4552152 5/10/2020 Security Update for Windows 10 (KB4552152)

Reply | Quote

[woody]

Mayank Parmar has tracked down the Blue Screen:

If you just hit “KMODE_EXCEPTION_NOT_HANDLED” Blue Screen of Death error on your HP computer with Windows 10, don’t worry, it’s not a hardware issue and it’s not just you.

Looks like it’s a conflict between some HP software (not clear to me what) and Windows Defender. Details in Parmar’s post.

3 users thanked author for this post.

F A Kramer, Elly, Perturbance

Reply | Quote

[fracky]

already deployed it to more than 500 users since 15th, no issue so far. the only problem i encountered is downloading cumulative for 1803, 1809, 1903 and 1909 via SCCM so I needed to pull the source from msft cloud instead.

 

1 user thanked author for this post.

woody

Reply | Quote

[fracky]

fracky wrote:

already deployed it to more than 500 users since 15th, no issue so far. the only problem i encountered is downloading cumulative for 1803, 1809, 1903 and 1909 via SCCM so I needed to pull the source from msft cloud instead.

 

notebooks hp, surface, toshiba/dynabook and HP desktops running W10 enterprise with mixed builds majority 1903. I hope nothing happen in the future

Reply | Quote

[Cameochi]

KB4556799 installed just fine here with no problems on my Dell XPS 8930. Thank goodness. 🙂

 

Reply | Quote

[bbearren]

I installed it as soon as it was offered, and I haven’t had a single issue with it (or with any other update).  The only non-Windows software/services I have running are Malwarebytes Premium v4.1.0 (permanent license, before the subscription model) and no other AV/AM (Windows Defender is fine).

I have Intel’s Hardware Monitor running, Intel RST, Cyberpower Powerpoint Monitor (to perform a normal shutdown when AC power fails and I’m running on battery), Intel Graphics,  Realtek HD Audio Manager, and Samsung Magician to handle TRIM and Rapid Mode.

I have no OEM bloatware on my machines, since they’re all DIY.  The laptop is a Dell Latitude E5420, but I uninstalled all the Dell software in the process of setting it up.  All five of my installations are basically “clean”.  I don’t use any “tweaker” software of any kind, no download manager or anything of that nature.

KB4556799 is just one of the list of offered Windows Updates that I have installed as soon as they were made available that have given me no problems whatsoever.

Create a fresh drive image before making system changes/Windows updates, in case you need to start over!

"When you're troubleshooting, start with the simple and proceed to the complex."—M.O. Johns

"Experience is what you get when you're looking for something else."—Sir Thomas Robert Deware

Computer Specs

Reply | Quote

[anonymous]

Are you sure people should wait on this month’s patches, Steve Gibson’s show notes say

Last Tuesday’s Windows patch Tuesday was the not the biggest ever, but it was the 3rd largest in Microsoft’s history, weighing in with a whopping 111 CVE-tracked bug fixes, 16 of which were rated CRITICAL and all but one of which enabled Remote Code Execution by an attacker.

Reply | Quote

[woody]

I don’t think Steve would recommend that you install the patches immediately. (Steve, if you’re watching, was that your intent?)

Every month MS releases patches for XXX CVEs, some percentage of which are Critical, and many of which involve RCEs (Remote Code Execution).

Every month, most of the patches work fine for most people. But, again, every month there’s a certain subset of Windows and Office customers who have problems. Some of the problems are trivial. Some most assuredly are not.

Our job, as crowdsourced beta testers, is to figure out where the problems are and, if possible, figure out how to work around them. Sometimes Microsoft acknowledges the bugs. Sometimes it actually fixes them. Many times we’re on our own.

The big question is whether there’s a risk in waiting to see where the bugs appear and how to deal with them. Some folks insist you should patch as soon as the patches are available. Others, like me, say you should wait until the dust has settled.

Looking back over the past two decades of Windows patches, I’ve found exactly one case where a patched security hole turned into a widespread threat in a couple of weeks — the Sasser infection — but that was 16 years ago. I’m still very much interested in hearing if anybody can find another situation where waiting a couple of weeks caused problems.

On the other hand, we’ve had problems with patches almost every month for years. I have month-by-month reports of those problems going back three years, starting here.

If you decide to install patches right away and get bit, please let us know! Otherwise, follow the MS-DEFCON warnings at the top of the page and make sure you get patched when things look stable.

1 user thanked author for this post.

Elly

Reply | Quote

[woody]

P.S. See https://www.askwoody.com/2020/omg-run-for-the-hills-five-new-windows-zero-days-published/

1 user thanked author for this post.

Elly

Reply | Quote

[AceOfAces]

I have installed the update on three machines (an old ASUS X51RL laptop – running Windows 10 Pro 32-bit, a custom built AMD Ryzen 5 APU based desktop and my daily driver HP 15 ay049nv). None of them had any issues. Only the daily driver had HP Support Assistant installed and HP Connection Optimizer. The only issue I’ve encountered with it is breaking when I’ve upgraded to the May 2020 Update (although the  HP Support Framework still works. I can go to HP’s website and use the included batch download tool). All of them are prett much stock, with no tweaks applied.

KMODE Exception sound to me that there’s a bug with a kernel driver. I wouldn’t be surprised that Riot Vanguard (Valorant’s anti-cheat driver. Yes.)would cause issues as well (it’s beta, but does it really have to run every time the system starts?)

On a minor note, I noticed that the Windows Update offered a new driver for Realtek HD Audio (6.0.8940.1). Not sure if it’s due to me having an OEM driver or it’s due to Windows finding a compatible driver for 2004, but I wouldn’t be surprised. Sometimes, newer OEM drivers find themselves on Windows Update.

• This reply was modified 10 months, 3 weeks ago by AceOfAces.

Reply | Quote

[EP]

I don’t think the Realtek audio driver v6.0.8940.1 is available there yet on WU, AcecOfAces.
It’s definitely not showing up on MS Update Catalog as of today May 25.

But HP themselves DO have a v6.0.8940.1 Realtek HD audio driver package available from their support site [sp103828 – release notes]

Edit – I’ve actually installed the 8940 Realtek audio driver on my old HP pavilion m8417c desktop pc and it works.

• This reply was modified 10 months, 3 weeks ago by EP.

Reply | Quote

[DRW]

Haven’t seen any of the problems reported.

Reply | Quote

[GoneToPlaid]

Our IT guy told me last Friday that many of the computers at the office were experiencing issues, including BSODs and occasionally black screens. All of the computers which are affected are HP desktops. I already suggested uninstalling this KB. I will also suggest uninstalling HP Assistant.

1 user thanked author for this post.

woody

Reply | Quote

[F A Kramer]

On Sunday May 24th HP provided through Windows Update “HP Software Component 4.1.4.3079” for my OMEN desktop computer. With Windows Defender running and no other antivirus program, I am now encountering no problems; no BSOD’s. This update was not provided for my HP Envy laptop computer, which has shown no problems; in two plus years it has had no BSOD’s ever.

My guess is that this  Software Component is a fix for the conflict that has plagued HP OMEN computers for past two weeks or so. I hope so and suggest that other HP desktop computer users look for this update.

2 users thanked author for this post.

sledgewick, woody

Reply | Quote

[woody]

Through Windows Update? Really?

Reply | Quote

[F A Kramer]

Yes, through Windows Update and not HP Support Assistant.

Afterward you will find it listed as a Driver Update under the update history listing. Perhaps HP gave the item to Microsoft to distribute to insure that it reached everyone affected?

Reply | Quote

[anonymous]

Hello F A Kramer, I had this HP Update 4.1.4.3079 on May 9th and experienced BSOD (well, GSOD since I’m an Insider) on May 10th and 19th…

Still waiting for a real fix (but since I’ve found a way to “resolve” tempoarily the bug and wait if my PC will GSOD again…)

Reply | Quote

[anonymous]

My hp laptop is suffered from KB4556799. That’s why how can I install Hp component software 4.1.4.3079?

Reply | Quote

[EP]

anonymous wrote:

Are you sure people should wait on this month’s patches, Steve Gibson’s show notes say

Last Tuesday’s Windows patch Tuesday was the not the biggest ever, but it was the 3rd largest in Microsoft’s history, weighing in with a whopping 111 CVE-tracked bug fixes, 16 of which were rated CRITICAL and all but one of which enabled Remote Code Execution by an attacker.

source or link to the site where Steve Gibson actually says this?

Reply | Quote

[b]

https://www.grc.com/sn/SN-767-Notes.pdf

Reply | Quote

[EP]

F A Kramer wrote:

Yes, through Windows Update and not HP Support Assistant.

Afterward you will find it listed as a Driver Update under the update history listing. Perhaps HP gave the item to Microsoft to distribute to insure that it reached everyone affected?

post a screenshot or image of this as proof, F A Kramer

Reply | Quote

[F A Kramer]

OK, here it is!

Attachments:

You must be logged in to access attached files.

Reply | Quote

[EP]

thanks!

Reply | Quote

[Alex5723]

Just like last month update Microsoft acknowledged that there are problems with KB4556799 and that Telemetry isn’t helping at all and is calling for help :

“We have seen social media and news reports related to various issues with KB4556799.

We are actively engaged with customers who are reporting issues. To date, we have not seen widespread issues reflected in telemetry, support data, or customer feedback channels. We continuously investigate all customer feedback and are closely monitoring this situation.

Note If you experience any issues, we’d like to know. Please provide feedback using the keyboard shortcut Windows + F or go to the Start menu and select Feedback Hub so that we can investigate.

After installing this update on a Windows 10 device with a wireless wide area network (WWAN) LTE modem, reaching the internet might not be possible. However, the Network Connectivity Status Indicator (NCSI) in the notification area might still indicate that you are connected to the internet.

We are working on a resolution and will provide an update in an upcoming release.”

https://support.microsoft.com/en-us/help/4556799/windows-10-update-kb4556799

Reply | Quote

[Alex5723]

F A Kramer wrote:

Yes, through Windows Update and not HP Support Assistant.

You are checking daily for Windows Updates ?

Reply | Quote

[EP]

per comment from this Bleeping Computer article about the KB4556799 problems:
https://www.bleepingcomputer.com/news/microsoft/windows-10-kb4556799-update-wont-install-has-audio-issues-bugs/#cid15733

Users who have the audio or BSOD issues should try disconnecting all USB devices from their PC (aside from mouse and keyboard obviously) and then rebooting. After the computer has restated plug the devices back in.

This has been my go to procedure for update issues for years and it resolves a surprising number of driver problems.

YMMV but I had both BSOD and audio issues after this latest update and the problems were resolved after following these steps.

Reply | Quote

[anonymous]

Hi everyone.  Late to the game and discussion, but just received my HP Pavilion back from Texas for the BSOD repair.  Same as everyone here, encountered early May 2020.  Mine BSODed on May 12th.  Was able to enter Safe Mode and restore.  But the 2nd BSOD on 20th resulted in an endless Loop, and couldn’t restore, reinstall, reset, etc.  I sent it back last week and now it is sitting next to me still in the packaging “repaired”.  I am afraid to turn the thing back on after all the **** it put me through (due to a software bug?).

My question- now we are on June 10th- did the said 4.1.4.3079 update from HP fixed the problem?  Thanks.  -Howard

Reply | Quote

[Perturbance]

I haven’t had a BSOD since May 19.  I re-enabled Windows Defender about 10 days later, and remain stable.  So, things are back to normal (for me anyway).

Reply | Quote

[Author]

Posts