Forum Discussion
Spc .
Aug 01, 2018Brass Contributor
Windows Server 2019 Preview Build 17744 -17738 - 17723 - Device Name not detected properly
Windows Server 2019 Preview Build 17744 (problem also occurs in Windows 10 17744) has a new problem when detecting devices.
All inputs from different sound cards are all always labeled as microphone although they're not a microphone.
Here's an example with alot of different audio inputs:
Windows Server 2016:
Windows Server 2019 Preview 17723:
Because of this system is very unstable ( crashes sometimes ), and alot of audio / conferencing / audio monitoring / audio server programs just hang because programs do not know what kind of input this is as they all assume it is a microphone but in reality it is a line-in or digital input.
Selecting a random microphone input can also damage speakers / headphones because user will hear dts or ac3 noise on listening device as the device is listed as analog input but in reality it is a digital SPDIF input.
I have the same issue on Windows 10 bulid 17738.
- Spc .Brass Contributor
Windows Server 2019 BUILD 17744.rs5 now only detects SPDIF OUT, no analog inputs or outputs for sound on any sound cards. Sound is not working on Windows 10 17744 / Windows Server 2019 17744.
Image:
- Spc .Brass Contributor
Build 17733 still doesn't fix devices not being correctly recognized in device manager, because of this programs fail or crash. Sound Card inputs show incorrect inputs. Because of this user hears static noise from SPDIF inputs acting as microphone input, and microphone inputs acting as SPDIF inputs.
Windows Server 2019 Preview 17723:
There should only be 1 microphone input, not 4 inputs, also there should only be 1 SPDIF interface not 3.
- Spc .Brass Contributor
Windows Server 2019 Preview 17738:
All analog sound inputs and outputs are now not detected on any sound cards, because of this analog audio ( in and out ) is not working at all. Only digital soundcard inputs and outputs are detected and working.
- Michael HennCopper Contributor
I have the same issue on Windows 10 bulid 17738.