Buffalo wrote:
"Buffalo" wrote in message news

Win10 Home 64ibt
After that update, sometimes my Zelotes T-9 USB Mouse would freeze and
wouldn't start back up and sometime just unplugging it and putting it
in a different USB slot would get it going again. Also sometimes the
mouse lights would stop working.
I also tried plugging in another USB mouse and it would work even when
the Zelotes one wouldn't. (I had both plugged in at the same time to
test that out).
If I just unplugged the Zelotes and plugged it back into the same USB
port sometimes that would fix it and other times it would not.

After doing that, the mouse starting working again and the sound in my
monitor speakers would go ON even though I use headphones most of the
time and have it set that way.

If I rebooted, usually all would be OK.

Thought the mouse was becoming defective until I started reading how
some had 'sound' problems after the update to 1809.
After doing some checking I reinstalled my sound drivers and all seems
well now and I also reinstalled the drivers for my Sades Spellbound
headphones.

Coincidence? Possibly , but I am inclined to believe that it was the
1809 update that caused those problems. I later put in new mouse drivers.

So, if you are having sound or mouse problems AFTER the update to
1809, try reinstalling the drivers to your sound card, or chip.


Buffalo
Sounds like this KB is the fix for the audio problems that the last 1809
update caused: KB4468550
https://support.microsoft.com/en-us/...from-windows-u

I will try it if I continue to have problems.


If you were wondering what "Smart Audio" is about, here's a hint.

https://docs.microsoft.com/en-us/win...ice-activation

The computer audio buffer can listen for "Hey Cortana" and wake
a sleeping (WakeOnVoice) computer. Mentions S0ix, which is a Surface feature,
so likely to work there (as the ACPI states are different on
a Surface product).

"The logs are stored in

C:\Windows\System32\Intel\IntelKeywordDetectorAdap ter\IntelKeywordDetectorAdapter.log"

Just to give you some idea how creepy "progress" in design is.

It means there is hardware support for "Hey Cortana".

All the hardware needs to do, is keep a buffer of data around
for when the hardware rises to S0 runstate, milliseconds
after you start speaking. Actual voice recognition would be
a lot more difficult (and, fancy).

"removed Windows Registry entries: MsftVADState and WOVState * 27 Nov 2015:
IntelWoV binary updated to version 1.2.227.0"

This is not just some HDAudio driver, run amok. It's another layer.

Paul