Guess if you used that firmware upgrade shortcut in program group fram EVAL installation and process said okay you should be there.
Then there seems two ways to check your current firmware, one is if you have the shortcut at bottom right side for TUSBAudio control Panel then open that and go to its "Info" tab to see firmware version, example is the blue below which is how it looks on my Win7 for v6.F2 aka 1226, If one is on Win10 native UAC2 driver then there is no TUSBAudio control Panel then go to Win10 device manager and open XMOS device that have symbol as a USB terminal (forget the XMOS device that have speaker symbol) then on details tab shift proberties to same as below and version should be listed in lowest window there, one could imagine after upgrade a unplug replug of USB connector will refresh OS to probe for the new firmware version.
View attachment 23583
Yes you should uninstall EVAL version, but whether to use native Win10 UAC2 driver or the rather old v224 driver is up to you. Would imagine a native driver code written by same company that have written code for OS itself should be the preference but was it myself running Win10 i would do a physical analog loopback test to another input port using for example free REW to check everything looks right and if it doesn't then try v224 and make the same loopback test to get peace in mind, say this because first Win10 build that had build in native UAC2 driver worked not very good on a ASUS U7, sound was different than used to and after a loopback test one could see impulse response was scary weird and phase was nothing but grass, but maybe they fixed that since or that U7 hardware is not up to protocol other than use driver from ASUS.
Thank you. I uninstalled the eval version and then went back in and reinstalled v224. It has been working fine for me. Version via the info screen is 1.02.
Last edited: