Win10 reports driver UNSIGNED and will not install

Still no success after 20+ hours working at this!!

The Cymatics fix (install KB3194496) doesn’t work. Only possibility is to go back to Win10/v1511 or Win8.1, which I cannot do.

So I’m stuffed and have a $1000 brick since I cannot use the uTrack24 for its intended use.

There is onus on Cymatic (or Archwave) to understand what’s wrong and either release a driver that WILL load (I’ve installed several properly-signed drivers today, so it can be done) or admit that USB isn’t going to be an option until MS sort things out.

Okay – further to this – I’ve emailed you a ZIP containing both the installation EXE (as downloaded from your site this morning with win7/Chrome) and a minidump following the bluescreen.

Interestingly, although you say you released new drivers in September 2016, the minidump shows that the two drivers that were installed are timestamped 10/11/2015 – these would be system timestamps, suggesting that they’re the wrong drivers.

Thanks.

Remember that I’m installing on a completely virgin win10 installation, so there would be no previous drivers. But, even after installation, the drivers are not located in WindowsSystem32drivers – they are only in the cymaticaudiouTrack24 folder. Deleting all of this (and searching the driver

If I examine the drivers in more detail, I do see that they are signed by Archwave Technology BV, and dated 5 September 2016. The Inf file date has 11/9/2015 with the version, 6.18.0 but the minidump dates them the following day at 10/11/2015 (first is US mm/dd/yyyy but second is rest-of-world dd/mm/yyyy)

Although I write software, I’ve not written drivers and I don’t know where or how the data is encoded in the .SYS files.

Clearly the fact that everything is perfect under v1511 but not under v1607 suggests that there’s a significant problem running under the latter. Whether it’s v1607 or the uTrack24 drivers is difficult to say, but also it seems odd that you can install to a virgin v1605 with no problem whereas I can’t. Maybe there’s some interaction between the uTrack and some other driver.

It’s also interesting that, going through exactly the same process, I was previously just getting driver signature issues – now I just get bluescreens.

However, other than locking myself into v1511 from now on, I really don’t know what else to do!

Well – it seems like there are two problems here, and the (genuine) unsigned driver issue was masking the bluescreen.

Initially it was definitely that the signature was invalid on v1607 (under v1511 it was fine) – and I now know why and can replicate and fix it thanks to PreSonus technical support who said that there was a problem if their driver is downloaded using IE11 or Edge. Initially it had been fine for me on v1607 (I’d been installing from a memory stick), but It was suddenly showing the same “unsigned driver” issue when installed from a download.

The solution was simply to download it using Chrome or Firefox – it installed just fine.

This was clearly what was happening to the uTrack24 driver. It was getting installed/initialised, but wouldn’t run because its signature was not recognised. As a result, the bluescreen issue didn’t show itself.

During the multiple reinstalls of Win10 I had unwittingly worked around this problem by grabbing the driver installation file from an old XP computer and put it on a memory stick.

The uTrack24 driver was now getting installed, which revealed the bluescreen issue (which also only happens on v1607 and not on v1511).

I’m glad that you’ve now been able to replicate this problem and I look forward to seeing a fix.

But it’s worth being aware that, when it does get fixed, it will probably still not install on v1607 if the installation file is downloaded with IE11 or Edge (this would appear to be an issue of which MS has been aware for some time, but hasn’t fixed).

I hope this helps