If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Sound and Mouse in 1809 Update
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 |
Ads |
#2
|
|||
|
|||
Sound and Mouse in 1809 Update
"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. -- Buffalo |
#3
|
|||
|
|||
Sound and Mouse in 1809 Update
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 |
#4
|
|||
|
|||
Sound and Mouse in 1809 Update
"Paul" wrote in message news
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 Now that is really interesting. Thanks Paul -- Buffalo |
#5
|
|||
|
|||
Sound and Mouse in 1809 Update
"Paul" wrote in message news
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 I don't have an " Intel " entry in that folder: C:\Windows\System32\Intel\IntelKeywordDetectorAdap ter\IntelKeywordDetectorAdapter.log" I am running Win10 Home 64bit. -- Buffalo |
#6
|
|||
|
|||
Sound and Mouse in 1809 Update
Buffalo wrote:
"Paul" wrote in message news 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 I don't have an " Intel " entry in that folder: C:\Windows\System32\Intel\IntelKeywordDetectorAdap ter\IntelKeywordDetectorAdapter.log" I am running Win10 Home 64bit. My guess is, there is PNP (Plug and Play) information that determines whether that driver loads or not. I don't think any computing device I own, uses that. It could be that KB4468550 fixes audio for people with computers that have the "Smart Audio" feature (supporting "Hey Cortana" Wake On Voice, or "Hey whatever they want" as a function of the config files it comes with). The KB4468550 shouldn't do anything to my computer, as that subsystem isn't present. You cannot wake my computer from sleep by speaking to it. But there are some computers running Windows 10 where that does work. And KB4468550 is for those people. If you have a regular computer and you have broken audio, your odyssey starts with Device Manager (available from the right-click Start menu). Look for "Code" errors or colored marks indicating trouble or even, "Unknown" devices. Look in Properties. The HardwareID in the details can indicate the hardware bus, and there is a hardware bus declaration for HDAudio. That's how you guess at whether some Unknown item in Device Manager, is actually your sound not being detected. Paul |
#7
|
|||
|
|||
Sound and Mouse in 1809 Update
"Paul" wrote in message news
Buffalo wrote: "Paul" wrote in message news 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 I don't have an " Intel " entry in that folder: C:\Windows\System32\Intel\IntelKeywordDetectorAdap ter\IntelKeywordDetectorAdapter.log" I am running Win10 Home 64bit. My guess is, there is PNP (Plug and Play) information that determines whether that driver loads or not. I don't think any computing device I own, uses that. It could be that KB4468550 fixes audio for people with computers that have the "Smart Audio" feature (supporting "Hey Cortana" Wake On Voice, or "Hey whatever they want" as a function of the config files it comes with). The KB4468550 shouldn't do anything to my computer, as that subsystem isn't present. You cannot wake my computer from sleep by speaking to it. But there are some computers running Windows 10 where that does work. And KB4468550 is for those people. If you have a regular computer and you have broken audio, your odyssey starts with Device Manager (available from the right-click Start menu). Look for "Code" errors or colored marks indicating trouble or even, "Unknown" devices. Look in Properties. The HardwareID in the details can indicate the hardware bus, and there is a hardware bus declaration for HDAudio. That's how you guess at whether some Unknown item in Device Manager, is actually your sound not being detected. Paul I didn't pay attention when I went to Device Manager before I reinstalled my sound chip drivers, but I think I would have noticed 'colored' marks next to items in it. Still, it doesn't matter now since all is working well after I reinstalled drivers for my sound chip, my headset and my mouse. Task Manager still is not working properly as it show, for example, 55% cpu use and in the column below, only around 8% used. Not sure how to get that going properly unless there is a fix out there. Eventually it will read 1 or 2% and that is accurate. Thanks for all you info and advice. -- Buffalo |
#8
|
|||
|
|||
Sound and Mouse in 1809 Update
Buffalo wrote:
I didn't pay attention when I went to Device Manager before I reinstalled my sound chip drivers, but I think I would have noticed 'colored' marks next to items in it. Still, it doesn't matter now since all is working well after I reinstalled drivers for my sound chip, my headset and my mouse. Task Manager still is not working properly as it show, for example, 55% cpu use and in the column below, only around 8% used. Not sure how to get that going properly unless there is a fix out there. Eventually it will read 1 or 2% and that is accurate. Thanks for all you info and advice. Task Manager on Windows 7 had the annoying property, that you had to click a button at the bottom to have "all users" processes displayed. The copies of Windows 10 I've installed here, don't make you do that any more. It's possible in Windows 10, if you were a limited user and not a member of administrators group, that something like that is going on. Maybe a limited user, cannot "see" as many tasks as a person who is a member of Administrators Group. It would be unfortunate if the computer worked that way. On my Win10 installs here, generally everything is shown the first time I start Task Manager. And I have the normal home-user situation of the primary account (1000) being a member of Administrators group. If that account is starting the Task Manager, it should have sufficient rights to see everything. What's missing on my Win10, is the GPU pane in Task Manager. If you have a sufficiently new video card, the video card resources will be displayed in Task Manager. That comes with some version of WDDM. My card(s) are slightly too old to qualify. My Task Manager isn't "the best it could be", because I'm missing the GPU portion. If you type "control" into Start : Run box, that opens Control Panels. There should be an Accounts panel, and in there you can check that you're a member of Administrators group. Some people will have turned on Account 500 "Real Administrator", and I don't know what the rules of engagement are for Task Manager when it's run while logged in as 500. Maybe it won't show certain stuff. Dunno. Summary: The behavior could have to do with accounts and what privileges the logged-in account has. Paul |
#9
|
|||
|
|||
Sound and Mouse in 1809 Update
"Paul" wrote in message news
Buffalo wrote: I didn't pay attention when I went to Device Manager before I reinstalled my sound chip drivers, but I think I would have noticed 'colored' marks next to items in it. Still, it doesn't matter now since all is working well after I reinstalled drivers for my sound chip, my headset and my mouse. Task Manager still is not working properly as it show, for example, 55% cpu use and in the column below, only around 8% used. Not sure how to get that going properly unless there is a fix out there. Eventually it will read 1 or 2% and that is accurate. Thanks for all you info and advice. Task Manager on Windows 7 had the annoying property, that you had to click a button at the bottom to have "all users" processes displayed. The copies of Windows 10 I've installed here, don't make you do that any more. It's possible in Windows 10, if you were a limited user and not a member of administrators group, that something like that is going on. Maybe a limited user, cannot "see" as many tasks as a person who is a member of Administrators Group. It would be unfortunate if the computer worked that way. On my Win10 installs here, generally everything is shown the first time I start Task Manager. And I have the normal home-user situation of the primary account (1000) being a member of Administrators group. If that account is starting the Task Manager, it should have sufficient rights to see everything. What's missing on my Win10, is the GPU pane in Task Manager. If you have a sufficiently new video card, the video card resources will be displayed in Task Manager. That comes with some version of WDDM. My card(s) are slightly too old to qualify. My Task Manager isn't "the best it could be", because I'm missing the GPU portion. If you type "control" into Start : Run box, that opens Control Panels. There should be an Accounts panel, and in there you can check that you're a member of Administrators group. Some people will have turned on Account 500 "Real Administrator", and I don't know what the rules of engagement are for Task Manager when it's run while logged in as 500. Maybe it won't show certain stuff. Dunno. Summary: The behavior could have to do with accounts and what privileges the logged-in account has. Paul I am the "Local Account Administrator" and it is the only account, AFAIK. I have my Task Manager checked to show 'more details'. I do have a gray box in the Performance tab for the GPU. Still, many times the Task Manager will be reading 40-60% CPU and the tasks shown may only show around 8-10% all added up. All 0's after the few that are using some CPU. This seems to be most prevalent during the first several minutes. I have Samsung EVO SSD 850 500GB as the only HD. It didn't do that before that 1809 update. I use Task Manager every time the computer is on. Thanks for you input, Paul. -- Buffalo |
Thread Tools | |
Display Modes | Rate This Thread |
|
|