Replies

Since no one seems to have a definitive answer as to where the KIR that fixes the loss of sound issue may or may not be at this time (see #2472787)  is it safe to assume that it will be included in the September CU?

Is so, I think the I’ll pass the uncertainty of the August CU.

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

@sb

Susan Bradley wrote:

Bottom line on this kind of side effect, install the update, if sound works you weren’t impacted, if your sound is impacted, uninstall the update, block it and the fix will be in the September updates. Windows patches are uninstallable.

I don’t mean to pile-on, but this advice basically disregards the existence of the KIR to prevent the problem in the first place.  The CU either works or it causes problems, something we are trying to avoid.  And who says the fix will be in the September updates?

It appears @Mele20  #2472700 just got tagged with the sound issue, so he/she neither had the KIR fix already nor was the KIR installed after the CU was installed to automatically fix the issue.  Has anyone had the sound issue, and then miraculously it corrected itself  via this KIR?

Isn’t there anyone of the experts here that can tell what the KIR is/does and how to tell if it was automatically downloaded onto our computers?  Or how to obtain it?

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

@alejr

Thanks for the info thread.  Note that I have not yet installed the August update, but the symptoms appear similar.  Questions:

Do I need to uninstall the existing HP Full features driver software package?  Or can just the driver part be replaced like you did? I thought you needed the Full feature package to obtain scanning etc?

Does the Control Panel uninstaller take everything out or is there a need for more thorough uninstalling?  I seem to recall HP installs being a bit complex.

Do I need to also uninstall the HP Smart software that originally also installed, and pops up now and then for various apps such as photo printing?

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

I appears this may have something to do with the “HP Printer Assistant” software that controls this internal communication between printer and computer.

Does this help troubleshooting?

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

@SB

Regarding #2472528

Could we please get a definitive answer regarding how to tell if the KIR has been installed BEFORE we install KB5016616?  This seems rather important to know.

sheldon wrote:

This KIR prevents the issue on Windows devices that do not have KB5015878 (or later updates) installed, but does not affect devices already affected by this known issue.

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

If you scan through the MS page for KB5016616 and click through the blue reference links, there is one with the word “health” in it.

The page opening states “After installing KB5015878 or later updates, some Windows devices might have issues with audio not working.”

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

Sorry, your response was unclear.  It just said to check the build with no further explanation on what to do next.  Current 19044.1826

I don’t install any interim updates and haven’t had any problems until last several weeks.  Only updates I can think of was a bunch of MS Office 2016 Retail (CtoR) updates back on 8/15.

Awaiting a definitive answer on the Sound KIR before installing KB5016616.

Also I dont have “printing” problems, I can print from the computer to the printer, it appears the other communication connections are gone (eg: can’t scan, fax, check printer cartridge levels, etc between the computer and printer. Printer by itself also  functions normally).

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

My reading of the issue agrees with @sheldon.

sheldon wrote:

This KIR prevents the issue on Windows devices that do not have KB5015878 installed, but does not affect devices already affected by this known issue.

So how do we tell if the KIR has been installed?

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

cyberSAR wrote:

I have had 4 or 5 calls with the same thing the last couple months

Interesting, as stated I’m not sure the power blip had anything to do with this as I only Scan every once in a while.

When I installed the HP printer, at the end somehow HP Smart got installed, but I never opened it or allow any install although when printing a photo, a printing option pops up now and then. In Settings, Apps and Features, HP Smart shows 7/13/2022. Advanced options allow for Repair, Reset, or Uninstall. I”m rather certain that I may have successfully Scanned since 7/13 if that is the update date.

I probably need more than  a basic driver.  What is the MS Scan app?  Can it override HP stuff?

Any advice on troubleshooting this issue?

I’ll try the remove cable and restart routine again, but not any luck the first time I tried it.

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

I tried those (FF system now) but only the Dark setting does anything and that is to change the entire screen field to Black.

Any other ideas?  From anyone?

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

1 user thanked author for this post.

Lars220

Thanks for trying to help as much as you have. It initially sounded as though your board was similar enough to mine to provide the specific answers.

alejr wrote:

Secure Boot is a function built into the motherboard, not the OS. In order for an OS to actually be able to access/use Secure Boot, these two things (located somewhere in the BIOS for a motherboard) need to be set as indicated: Secure Boot must be enabled. OS Type must match the OS you’re using. If either of those is not set correctly, your OS will not be able to access/use Secure Boot!

I am aware of those requirements. That is why I initially thought the Security Boot> OS Type dropdown box selector could be the answer. But you said:

No, you enable/disable secure boot by changing the Secure Boot state option.

So what is still missing is HOW to actually enable Secure Boot. As noted, the Bios says the Secure Boot state is Enabled, but all Windows checks say it is NOT Enabled. I checked every possible setting in my Bios and there is nothing that references an Enable/Disable Secure Boot switch. Or a way to directly change the Secure Boot state.

alejr wrote:

You’re over complicating things

Not really, still no definitive answer for my motherboard Z370-E.  The search continues.

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

@alejr

alejr wrote:

Regardless, you can check whether it’s enabled/disabled by running the following command from powershell as an Administrator. Confirm-SecureBootUEFI You’ll see True if Secure Boot is enabled, False if it’s disabled.

I show False.

Also System Information >System Summary>Secure  Boot State show OFF

Inside my ASUS bios under Boot>Secure Boot screen it shows:

“Secure Boot state >   Enabled” (Gray lettering/not selectable)

“Platform Key (PK) state > Unloaded” (Gray lettering/not selectable)

“OS Type >  Other OS” ( White lettering in a dropdown box, selectable between “Other OS” and  “Windows UEFI mode” also in White lettering)

Perhaps the “Secure Boot state” lights up after selecting Window UEFI mode? Or the Gray Enabled then also displays a Disabled?

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

@alejr

Thanks for the detailed reply, however I am still confused on how to turn Secure Boot ON.

You say:

No, you enable/disable secure boot by changing the Secure Boot state option.

I thought/read setting  the Secure Boot >OS Type to “Windows UEFI Mode” was changing the Secure Boot state to ON/ENABLE for Windows?

I don’t recall seeing any separate setting option in the ASUS  bios settings called Secure Boot state to select simply “Enable/Disable” Secure Boot.

Pls advise where to find such a setting in the bios, or are we basically saying the same thing?

 

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

@alejr

Regarding turning Secure Boot on within an ASUS Motherboard:

I have an ASUS Rog Strix Z370-E Gaming board that came in my Maingear computer and Secure Boot has never been activated.

My disk partition is GPT, Bios Mode is UEFI.

The Motherboard BOOT menu > Secure Boot >OS Type is currently set to “Other OS” which I understand on an ASUS board means Secure Boot is OFF/DISABLED.  This has to be switched to “Windows UEFI Mode” to turn Secure Boot ON/Enabled – correct?

Another confusing item with an ASUS board is the CSM setting(s). Some say the CSM needs to be turned OFF to enable/use Secure Boot, others (perhaps you included) say CSM > Launch CSM > Enabled > Boot Devices Control can be set with Secure Boot at the same time.

As I said, Secure Boot has never been set on my computer and the CSM was originally set per above at “UEFI only”.  However this would not allow me to boot from a CD so we changed the setting to “UEFI Legacy OPROM” which solved the problem.

Can I leave the CSM at the above current setting and still turn on Secure Boot? Or does CSM need to be completely turned OFF, or only use the “UEFI only” setting?

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

So is use the command “reg delete HKEY_CLASSES_ROOT\ms-msdt /f”  still the best advice?

FMI, what is the purpose of the  “/f ” at the end of the command?

I assume you could also enter the registry and manually delete the key?

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