Jump to content
Solid-State

Win Server 2019/2016 General questions and discussions

Rate this topic

Recommended Posts

I recently installed the latest version of Windows Server 2019, downloaded from the Microsoft website. Unlike the previous version, with this current I'm having problems with the Ayre driver, even using the Audiophile Optimizer for installation.

 

Whenever I start Windows, the Ayre driver appears in devmgmt as "Unknown" and "Disabled", and when I enter the properties, I get the following message: "This device is disabled (Code 22)". Nothing I tried solved the problem. Anyone have any suggestions? I thought about trying the FOB installation, but I couldn't understand that there would be any advantage.

Ayre.jpg

Share this post


Link to post
Share on other sites

Hi Felipe,

I've had driver problems in the past and I feel your pain.

 

Just to establish a baseline, I assume you: 
- are using Win2019 standard core (have you tried it in gui?)
- installed the driver before running AO
- tried F8 and ST driver helper, pnputil
- tried the HD Audio Controller
- tried again with a fresh windows install
- are using AO 3.0 beta 36 (I had problems installing my dac driver with version 34 or 35).

- could you hack the driver inf file?

 

I know you're very capable but sometimes we forget the obvious. Perhaps something here will trigger your thoughts:
- are there any old driver entries in the registry?
- have you checked for IRQ conflicts?
- are any old driver files on one of the attached drives?
- does it install on gui mode? 

 

I can't install the dac driver unless the dac is connected and turned on and the usb input is selected. 
- have you tried reconnecting the cable/restarting the dac?
- have you tried another cable?
- have you tried with a different usb port?

 

Good luck, Bill
 

Share this post


Link to post
Share on other sites

Hi, Bill. Actually, since the Ayre QB-9 driver worked perfectly on Windows Server 2016 Core and an earlier version of Server 2019 Core, I've always been sure that the problem is with the Windows version (17763.253; I haven't yet tried to manually update). What I didn't investigate yet is if have any problems related to the BIOS (it's a new motherboard, a completely new hardware that I'm still exploring). I've tried the standard procedure, which I've always adopted: in a completely clean installation of Windows, I use the Driver Helper of Audiophile Optimizer to install. From the moment it didn't work, I tried, for once, to do a manual installation, through the .inf file. It also didn't work. The big problem is Windows no longer identifies the driver as being a sound driver, although the JPLAY does it perfectly.

 

In research, I checked similar cases on the Internet, even with Realtek High Definition Audio, but no reports from anyone who actually solved the problem. So, to get around it while something more concrete isn't offered (by Microsoft or by Audiophile Optimizer), I created a script for activating the driver and inserted it at Windows startup. Therefore, whenever I turn on the computer, the driver (which is disabled) is immediately enabled and works perfectly. For now, that's how I solved it.

 

Answering some questions: I just didn't try to change the USB cable and even the USB port I use because in the previous version of Windows Server 2019 Standard Core the operation was perfect.

Share this post


Link to post
Share on other sites

So it installs ok but boots in disabled state until your script enables it again? It does sound like a bios or registry issue.

The idea with cable/connections came from a problem I had with networking until I discovered I had knocked the cable and the connector was part-way out.

BTW I'm still playing happily in ramdisk.

Share this post


Link to post
Share on other sites

importent

 

https://support.micr...pdate-kb4489899

 

Applies to: Windows 10, version 1809Windows Server 2019, all versions

 

After installing this update on machines that have multiple audio devices, applications that provide advanced options for internal or external audio output devices may stop working unexpectedly. This issue occurs for users that select an audio output device different from the “Default Audio Device”. Examples of applications that may stop working include:

Share this post


Link to post
Share on other sites

I've experienced the same issue lately, Mutec DDC driver getting disabled no matter if F8 or driver signature or AO3 Driver Helper were tried.  What I've found effective in resolving the disabled audio driver is running "AO -e" command, reset afterwards, do your own things (i.e. setting fix IPs, adjusting audio driver's latency & buffers, etc.), install and activate JPLAY, then finally run "AO -u".

 

AO3 executed in express mode appears to inject something WASAPI-related to the system that facilitates audio driver installation.  A good sign of audio driver properly installed is that a speaker symbol appears and stays unchanged next to the driver in Device Manager.


WS2019 Datacenter Core, dualPC, JPLAY Femto, AO3, Fidelizer 8.5, BubbleUPn.

 

Share this post


Link to post
Share on other sites

"FelipeRolim

Well, my computers use Windows Server in Core mode, with no GUI. All I do is by command line. I leave, to facilitate, remote access enabled, so that I can command the two computers through the notebook (mstsc.exe).

 

When the computer has the IP set as fixed (task for which use the command netsh interface ipv4 set address name ="Ethernet" source=static addr=192.169.0.1 mask=255.255.255.252), there's no internet access. And, as the Audiophile Optimizer only needs internet at the time of installation and configuration (and this only in the Beta version), when I use it, just activate DHCP again, through the command netsh interface ipv4 set address name="Ethernet" dhcp. I then connect the computer to the router. To revert, just fix the IP again and you're done. I find it simple and, for my case, fully functional. For a user of a JCAT network card (which has two possible connections), this isn't even necessary. Just swap the network port.

"

 

when you set staic IP you neeed to set GW and DNS also,
same as you do in Sconfig !!

 

netsh interface ip set address name="Ethernet" static 192.168.0.1 255.255.255.0 (GW) 192.160.0.x
netsh interface ipv4 add dnsserver "Ethernet" address=xxx.xxx.xxx.xxx

Share this post


Link to post
Share on other sites

Why !!!!

Don't you know why,

then start som basic IP lerning

 

GW = default route

DNS = to resolv ip to host or Host to IP

Share this post


Link to post
Share on other sites
8 minutes ago, TubeMan said:

Why !!!! 

Dont you no whay, then start som basic IP lerning

 

I think someone needs his coffee..

Share this post


Link to post
Share on other sites

Another person should be responsible for doing this coordination between the Audiophile Optimizer and Windows Server topics. TubeMan simply has no education to answer people's questions. You don't have to treat everyone like your son, but there's no need to write with that grin, either.

 

My system doesn't depend on the router and also doesn't depend on internet access. There's nothing in the network settings other than the IP numbers (192.169.0.1 and 192.169.0.2) and the subnet mask (255.255.255.252). It's fully functional and JPLAY and Audiophile Optimizer (the only software I need) works perfectly. So before replying rudely, it's interesting to check out the particularities of each system.

Share this post


Link to post
Share on other sites
7 hours ago, TubeMan said:

when you set static ip. by netsh,
windows clear all ip settings
that's why you need to set GW and DNS

You should have said this in the first place 😉


WS2019 Datacenter Core, dualPC, JPLAY Femto, AO3, Fidelizer 8.5, BubbleUPn.

 

Share this post


Link to post
Share on other sites

I updated both PCs to Windows 2019 Datacenter 17763.379 a week ago and found the sound a bit on the sterile, bright side, almost unbearable.  Swapping in an OS disk of 17763.316 to AudioPC and music came back.  A couple days later, out of curiosity I put the 17763.379 disk back into AudioPC, let it sit and play for less than a day and surprisingly found the SQ improved.  Today, about a week after initial update, 379 on AudioPC is getting better and closer to 316 in musicality (subjective) but probably never the same.

 

Lesson I learned from this humble finding:  never judge, even a newly installed OS or newly ripped songs/album, right off the bat.  Intead, let it sit in and play for a good few days.

 

While waiting for AO3 final release with excitement, I look forward to this month-end's Windows Update which promises to fix an audio related issue.  Until then, I hope we all continue to enjoy the music.


WS2019 Datacenter Core, dualPC, JPLAY Femto, AO3, Fidelizer 8.5, BubbleUPn.

 

Share this post


Link to post
Share on other sites

I am having difficulty installing driver for a USB microphone (UMIK-1 for room EQ). I was able to install it before using usbaudio2.inf (usbaudio2.sys and related dll) on WS2016 core/AO2.20 machine.  Now I am on WS2019 core/AO3.0 and the same driver no longer installs. New OS says it is not the right driver for the microphone device. I injected WASAPI, installed HD audio drivers but without success. Can someone help me find a driver for my microphone?

 

image.thumb.png.02b5a6acc13cdb720230d323f4c8368f.png

 


Music Source: NAS[Synology], Qobuz, Tidal

Music Player: Roonserver[Mac mini]

Control PC: squeeze2upnp, fb2k, dirac, Jplay Femto, Fidelizer, AO(4D), WS2019 GUI, Mac mini w/HDPlex 200W

Audio PC: Jplay Femto(KS/1000hz), Fidelizer, AO(4D), WS2019 core, i7 w/HDPlex 200W

DDC: Iso Regen w/LPS1.2, Acousence afi+USB (USB to S/PDIF) w/Li-ion battery PS

DAC: Yggdrasil Analog 2

Share this post


Link to post
Share on other sites

The „Install HD Audio“ feature should take care of that. 100% sure you pressed F8 and disabled driver signature enforcement before running the install hd audio feature?


ıllıllı [  ...AO 3.00 IS HERE... ] ıllıllı
____________________________________________________________________________________

 

Shop | Core Audio Music Server | Reviews | Reference System | AudiophileOptimizer 3.00 | PDF Guide

 

Share this post


Link to post
Share on other sites

Hi Phil,

 

Thank you for getting back to me.

 

I did pressed the F8. HD Audio installation routine did give me a warning whether I would like to proceed. 

 

image.png.7a7486c3158ad3efca48f37358398f0f.png

 

In the above snapshot, I am seeing the "Unknown" speaker icon. This is my control PC. On my audion PC, I also see the "Unknown" speaker icon, under which I have my XMOS device. More importantly, Umik-1 microphone does not install even after installing the "HD Audion". Umik-1 is probably the most popular microphone for room calibration purpose. What can I try further?


Music Source: NAS[Synology], Qobuz, Tidal

Music Player: Roonserver[Mac mini]

Control PC: squeeze2upnp, fb2k, dirac, Jplay Femto, Fidelizer, AO(4D), WS2019 GUI, Mac mini w/HDPlex 200W

Audio PC: Jplay Femto(KS/1000hz), Fidelizer, AO(4D), WS2019 core, i7 w/HDPlex 200W

DDC: Iso Regen w/LPS1.2, Acousence afi+USB (USB to S/PDIF) w/Li-ion battery PS

DAC: Yggdrasil Analog 2

Share this post


Link to post
Share on other sites

What happens when you remove both items with yellow exclamation mark and after that click on „rescan“?


ıllıllı [  ...AO 3.00 IS HERE... ] ıllıllı
____________________________________________________________________________________

 

Shop | Core Audio Music Server | Reviews | Reference System | AudiophileOptimizer 3.00 | PDF Guide

 

Share this post


Link to post
Share on other sites

They reappear. 


Music Source: NAS[Synology], Qobuz, Tidal

Music Player: Roonserver[Mac mini]

Control PC: squeeze2upnp, fb2k, dirac, Jplay Femto, Fidelizer, AO(4D), WS2019 GUI, Mac mini w/HDPlex 200W

Audio PC: Jplay Femto(KS/1000hz), Fidelizer, AO(4D), WS2019 core, i7 w/HDPlex 200W

DDC: Iso Regen w/LPS1.2, Acousence afi+USB (USB to S/PDIF) w/Li-ion battery PS

DAC: Yggdrasil Analog 2

Share this post


Link to post
Share on other sites

No, It is not. "Umik-1" device is still marked with a yellow triangle as can be seen in the screenshot above (this is my control pc with WS2019 core). In my Windows 10 machine, " "Umik-1" device shows up under the "Sound, video and game controller" section with usbaudio2 generic driver. I tried the same on my audio pc (again, WS2019 core), but with same result.


Music Source: NAS[Synology], Qobuz, Tidal

Music Player: Roonserver[Mac mini]

Control PC: squeeze2upnp, fb2k, dirac, Jplay Femto, Fidelizer, AO(4D), WS2019 GUI, Mac mini w/HDPlex 200W

Audio PC: Jplay Femto(KS/1000hz), Fidelizer, AO(4D), WS2019 core, i7 w/HDPlex 200W

DDC: Iso Regen w/LPS1.2, Acousence afi+USB (USB to S/PDIF) w/Li-ion battery PS

DAC: Yggdrasil Analog 2

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...