Hi All.
I found mme/wdm and ASIO drivers working with Apogee Mic 96k in Windows 7.
There is a tricky way to make apogee mic work under Windows7...
Apogee mic is USB Audio Class 2.0 (UAC2) device so it works out of the box for MAC os (OSX 10.6.4 and higher) and some newer linux ALSA drivers, but windows does not have internal USB 2.0 audio drivers... However there is one company which makes the universal UAC2 drivers for oem device manufacturers -Thesycon.
A lot if Hi-Fi DAC manufacturers use their drivers, which are just a little customized.... Also BLUE Yeti PRO USB Microphone uses their drivers to work under windows.
So... can we use Thesycon UAC2 driver to install Apogee mic under windows? YES!!! We Can !!!
How to install Apogee mic using Thesycon UAC2 driver:
1. Download from Blue home page "YetiPro_Windows7_DriverA" (it is Thesycon v1.29 UAC2 driver),
or from m2tech company HiFace Two driver which is the newer Thesycon V1.70 UAC2 driver: http://www.m2tech.biz/public/pdf/M2T...ver_r1.7.0.exe
2. Download from Thesycon page "TDD" Thesycon USB Description dumper tool to obtain your Apogee MIC usb PID&VID numbers: http://www.thesycon.de/tdd/tdd.exe,
3. Connect your MIC to usb port and run TDD tool and select MIC device from selectable list of connected USB devices...
4. now you are able to copy/remember your mic VID and PID numbers (vendor and product ID)
You can also read PID&VID directly from Windows Device Manager, if you connected MIC to USB port, Windows will recognize it and it should appear in Control Panel->DeviceManager->Audio,Video and Game Controllers
as MiC or MiC96k. Then if you duble click it and open the third tab "details" you can read second position from Properties list which is your hardware identification then you get description like:
"USB\VID_0C60&PID_001B&REV_0002&MI_01" - Which contains VID and PID values: "VID_0C60&PID_001B"


5. disconnect MIC from USB port.
6. extract YetiPro_Windows7_DriverA ( or M2Tech HiFace Two 1.7 Driver) and open for edition two *.inf files:
"BLUE_YETI_PRO.inf" and "BLUE_YETI_PROks.inf"

7.Find first [_Models] and [_Models.ntamd64] entries in both files looking like:

"BLUE YETI PRO"=_Install, USB\VID_074d&PID_0001 two entries for "BLUE_YETI_PRO.inf"
and
"BLUE YETI PRO Audio"=_Install, TUSBAUDIO_ENUM\VID_0074d&PID_0001&KS two entries for "BLUE_YETI_PROks.inf"

Just change the VID and PID numbers to those of your apogee MIC values noted from TDD tool for MIC96k it will be:

"BLUE YETI PRO"=_Install, USB\VID_0C60&PID_001B two entries for "BLUE_YETI_PRO.inf"
and
"BLUE YETI PRO Audio"=_Install, TUSBAUDIO_ENUM\VID_0C60&PID_001B&KS two entries for "BLUE_YETI_PROks.inf"
and save *.inf files.

8. Run yeti/m2tech driver "setup.exe" when mic is disconnected and connect mic when driver setup will ask for that... Just click next and agree for not signed driver to be installed ,and you are ok.
9. After setup will finish your Mic will show under device manager as Blue_YetiPro/m2tech device
10. Now you can use your Apogee MIC for any mme/WDM recording software as well as for ASIO as Thesycon UAC2 driver is MME and ASIO, you can for example use your MIC for Skype calls in windows

Just one important remark regarding USB ports, your MIC will be recognized properly with the new drivers only in this USB port for which you made the driver installation procedure. If you connect your mic to different port then you have to run the driver setup again for that port... Off course you do not need to modify anything more in the setup files as PID and VID are the constant identification values of the hardware.

Is anybody of you having by chance other Apogee devices, like Jam,One or Duet and having also Windows7 computer? I'm really curious if that UAC2 drivers will also work for Jam,One or Duet But I do not know anybody, who can check it.
I know that for One and Duet such a Windows operation will be very limited, probably only basic playback capability and if recording will be available, I'm not sure if gain settings will be accesible through Thesycon Controll Panel - Which for MIC allows to set buffer settings.

So if anybody is able to check it please just try... I know that people having Apogee gear use mostly Apple computers, but some people use sometimes both platforms and having possibility to use Apogee equipment with PC could be useful.

Hey gregorg! Many thanks for your help!

I made it work and it records perfectly (first recording mic I own so I can't really tell how good it is)

The only thing is, that whenever I try to monitor myself during any recording (Using Reaper, or Mixcraft) I listen to a little buzz. but when I render the file, the buzz goes out... it seems that it's only for monitoring.. I guess smth wrong with the output settings?

Anyone that understands of this matter?

Cheers!!

I tried it but it didn´t work for me, I don´t know what I did wrong, My mic´s ID is: USB\VID_0C60&PID_000B;

This is what I wrote:
I did it also for the M2Tech, at first when the instalation was finishing it said there was a error with the file "BLUE_YETI_PRO.inf" but it would still look as if it was installed because there was a folder created on Program Files.

So I now unistalled it and when I try to install it agains it says (even tough it´s plugged":

Any ideas?

Did you ever get a solution, nahumo?
My pc gives me the exact same answer you got.

Hi guys, I have the same problem which nahumo gets. Any solution for this problem?
My system is Win 8.1 X64.

I have pretty much the same problem, trying to get MiC to work on Windows 8.1. I extracted the M2Tech driver files and modified m2techusbaudio.inf and m2techusbaudioks.inf as follows:

[_Models]
"hiFace TWO"=_Install, USB\VID_0C60&PID_000B
"hiFace TWO"=_Install, USB\VID_0C60&PID_000B

[_Models.ntamd64]
"hiFace TWO"=_Install, USB\VID_0C60&PID_000B
"hiFace TWO"=_Install, USB\VID_0C60&PID_000B

and

[_Models]
"M2Tech hiFace TWO UAC2"=_Install, TUSBAUDIO_ENUM\VID_0C60&PID_000B&KS
"M2Tech hiFace TWO UAC1"=_Install, TUSBAUDIO_ENUM\VID_0C60&PID_000B&KS

[_Models.ntamd64]
"M2Tech hiFace TWO UAC2"=_Install, TUSBAUDIO_ENUM\VID_0C60&PID_000B&KS
"M2Tech hiFace TWO UAC1"=_Install, TUSBAUDIO_ENUM\VID_0C60&PID_000B&KS

I run setup.exe, it recognizes that MiC is connected, but installation fails: "ERROR: Pre-installation of 'C:\.....\m2techusbaudioks.inf' failed


I can see one thing that's wrong with nahumo's setup. You have an "O" instead of "0" for your VID: "BLUE YETI PRO"=_Install, USB\VID_0C60&PID_000B instead of "BLUE YETI PRO"=_Install, USB\VID_OC60&PID_000B

But even with that, my m2tech driver won't install.

I've been wanting to try the Blue Yeti driver too, but I seem to be able to find only the new version that doesn't let you extract and modify the .inf files. Can anyone point me to the driver referenced in this thread.

Other than that I'm at my wits end. Can someone help please?

I can confirm that Duet 2 is working using the described method.
I downloaded the files, took note of VID and PID and replaced those in m2techusbaudio.inf by editing an entry for Mercury DAC (first entry of two). I proceeded with the driver setup which ended successfully, however Windows complained of not being able to install the driver anyway. I rebooted, went into Device Manager and found that my Duet was listed as Mercury DAC but had no drivers attached to it. I chose to install them completely manually by picking a category of audio devices and then using "Have disk..." which I pointed towards the inf files in the unpacked driver directory and from the list that appeared I selected "Mercury DAC 1". Sound playback started working afterwards but I really tested nothing apart from the fact that 48khz audio playback worked. It was just an experiment as I use OS X for audio work anyway.

BuckieJoe,
were you on Win 7?

It worked for me. Do this....

[_Models]
"hiFace TWO"=_Install, USB\VID_0C60&PID_000B
"hiFace TWO"=_Install, USB\VID_0C60&PID_000C

[_Models.ntamd64]
"hiFace TWO"=_Install, USB\VID_0C60&PID_000B
"hiFace TWO"=_Install, USB\VID_0C60&PID_000C

and

[_Models]
"M2Tech hiFace TWO UAC2"=_Install, TUSBAUDIO_ENUM\VID_0C60&PID_000B&KS
"M2Tech hiFace TWO UAC1"=_Install, TUSBAUDIO_ENUM\VID_0C60&PID_000C&KS

[_Models.ntamd64]
"M2Tech hiFace TWO UAC2"=_Install, TUSBAUDIO_ENUM\VID_0C60&PID_000B&KS
"M2Tech hiFace TWO UAC1"=_Install, TUSBAUDIO_ENUM\VID_0C60&PID_000C&KS

It seems that this doesn't work anymore. I run into an issue at step 6. When I extract the file downloaded from the Blue website there is only the .exe file, no .inf files. It seems Blue has updated their driver package. Anyone know how to make this work now?

The Thesycon UAC2 drivers are the same thing. I found another company that uses them and they are separate files that can be altered as per the instructions in post 1. Here is where I found them........

Wavelength Audio, USB DACS, Setup information for 24/192

It works, but you must disable driver enforcement first, please read this How to Disable/Enable Driver Signature Enforcement in Windows 8 and 8.1

Worked on Windows 10, just make sure you make the changes in the two configuration files, "tusbaudio" and "tusbaudiokf", which aren't labeled as ".inf".

Hi, friends.

(sorry for my english, it's sometimes bad))

Before buying my Apogee 96k mic, I thought that this topic will help me to connect it with my tablet PC on Win 8.1

But NO.
All day I have strong headache with editing these .inf files, plugging/unplugging mic, but the "Setup requires that the device is plugged in...." message was again and again.

So, I was little disappointed, and decide to try other methods.

And first method I tried was right.
Ok..
Guuys...

One thing that we need it's just ... freeware ASIO4ALL drivers. And nothing else.
Really, it works.

Just download, install it and then in your DAW's Audio Setup set your Apogee 96k mic as record device. That's all.

Of course, there will one trouble - you may not be able to listen , when your DAW works under the Asio4All drivers. But I found the solution for that trouble on youtube - https://www.youtube.com/watch?v=VHoyLsON3iU

On Windows 10 the above will work, but you need to turn on driver signing checks. This is because when you tamper with the .inf files, the hashes change and become unsigned.

You can disable this check by running the following in a command prompt: bcdedit.exe /set nointegritychecks on

You will need to restart the computer after this and then run the installer.

I'd got success using Yeti drivers on Windows 7 as described above but had had problems doing the same on Windows 10. After several hours of tryings I've found the following solution for Win10.
1. Disable integrity check (bcdedit.exe /set nointegritychecks ON + bcdedit.exe /set TESTSIGNING ON + reboot)
2. Load drivers from Wavelength Audio from here https://www.usbdacs.com/hs24192/hs24192.html
3. Edit drivers' *.inf files (modify VID/PID as described above).
4. Run setup.exe using troubleshooting/compatibility mode.
5. When setup asks, plug in the Mic96k (at this moment don't press "next" at the setup program but switch to the device manager and remove just appeared Mic96k from the device list).
6. Press "next" at the setup program and complete the process.

That's all. I'm not sure that every step should be done exactly as described but I decided not to spend any more time if it works.

Best!