[scrypt]

Hate to mention something I normally wouldn't bray about in public, but I want to be certain it won't be a Gilmorean Liteknot for anyone else.

I happen to own a last-gen iFi iDSD Nano (the model is unimportant) and flog a Windows 10 Pee Sea in an orifice environment (don't arsk). To use the festive Nano in that space, I needed to download iFi's driver software from ziss vebpage:

https://ifi-audio.com/downloads/

Direct Link

Partly because the link led to an .exe file, Symantec flagged it as a threat. For that reason, I had to contact the IT security team. An hour later, a team member told me that specialists had analyzed the file and determined it was malicious.

The verdict was unavoidable: I couldn't use my DAC at work.

I told my IT interlocutor that I'd used the Nayno with my previous Peeled Sea. Panting and fanning himself, he explained that no one had detected the malicious file with the older security measures used on System 7, but with tighter ones impleMINTY!mented, they now were able to do their job and the file really was malicious. This wasn't simply a generic warning from Symantec, they warbled.

Is this a problem for anyone else who uses Cyst-Hem 10? Has anyone else tried to download the aforeheaded file recently and gotten the same resulks? If so, perhaps said file should be spiffed, rem-oofed or replaced.

Also:

Was this issue addressed in the newer driver software, which I dimly recall (but perhaps it was all a microbial fashion shoot involving a miniaturized Val Kolton and a snowmote who styled V's mane with tiny rose gold chopsticks) couldn't be used with the older models?

(Link to that pore vew)

 

[scrypt]

In the words of my aye doctor (whose diction is slightly eccentric), this whole thing strikes me as flinkety. I'm not quite sure what flinkety means, but if anyone can solve this driver dilemma, it's that zesty man in ultra-natty attire at iFi.

 

[robm321]

I downloaded the latest driver's from iFi's website. I haven't had any issues with it. I know the risk of allowing a virus into the network can get IT people very nervous. They tend to not risk anything. I seriously doubt it's an issue.

Unfortunately, that doesn't solve your problem.

 

[scrypt]

Still, that could help to dissolve someone else's problem, in which case, I'd revel in the resolution vicariously.

I agree that it can be irksome to an individual with hardware when IT peepholes err on the side of banishment. I most soitenly understand their channeling panic, however.

(More feedback from others could be enlightening, too (hint, wangle).)

 

[theveterans]

• Why not use another transport with SPDIF output that is compatible with your IT's policy and feed it to the iFi

Edit: just found out it's only USB. You're pretty much out of luck unless you use your smartphone or any other DAP with USB out.

 

[technobear]

I've just rechecked this with Microsoft Security Essentials and it indeed shows up as a Trojan. I've opened a ticket at iFi support.

 

[scrypt]

I've just rechecked this with Microsoft Security Essentials and it indeed shows up as a Trojan. I've opened a ticket at iFi support.

Thanks for the validation. Has anyone else checked the .exe file using Essentials?

After I visit the Woundos machine at my grillfiend's place, I'll open a ticket if I get the same result. If not, I'll do my best to alert iFi to the issue. It would be nice if I were able to use my iDSD at work again.

 

[technobear]

You can still get the previous driver:

http://ifi-audio.com/wp-content/uploads/data/driver/iFi (by AMR) HD USB Audio Driver 2.26.exe

It seems to have no issues.

 

[scrypt]

You can still get the previous driver: http://ifi-audio.com/wp-content/uploads/data/driver/iFi (by AMR) HD USB Audio Driver 2.26.exe

It seems to have no issues.

Thanks, TB. I'll give the Old Chub a gyre.

One thing that makes me hesitate is the slender poss that iFi will consider the issue and fix it. I want my next convo with IT to be our last on this top-ick.

 

[iFi audio]

Hi all,

Just to be clear, let us reply again what we've already stated about our software and viruses. Well, it's a false positive. We use multiple anti virus software, including Avast, Avg, Microsoft, Mcafee, TrendMicro Housecall and Kaspersky to verify our uploads.

We long discontinued our use of Symantec and Sophos. What is perhaps most telling that each anti-virus software that flags our driver as virus attributes it another virus.

So either our driver is infected with 7 different viruses, each of which is picked up only by one specific antivirus software and missed by all the market leaders (and our own scans), or it is a false a positive.

Cheers,
iFi Team

 

[technobear]

Hi all,

Just to be clear, let us reply again what we've already stated about our software and viruses. Well, it's a false positive. We use multiple anti virus software, including Avast, Avg, Microsoft, Mcafee, TrendMicro Housecall and Kaspersky to verify our uploads.

We long discontinued our use of Symantec and Sophos. What is perhaps most telling that each anti-virus software that flags our driver as virus attributes it another virus.

So either our driver is infected with 7 different viruses, each of which is picked up only by one specific antivirus software and missed by all the market leaders (and our own scans), or it is a false a positive.

Cheers,
iFi Team

That's all very well but I am currently unable to download the driver because the anti-virus (Microsoft Security Essentials) bins it straight away. We're not all about to change or disable our anti-virus so that we can download and install your driver.

Let's also be clear that the driver is not the problem here. The installer .exe is the problem. It needs to be resolved.

 

[iFi audio]

That's all very well but I am currently unable to download the driver because the anti-virus (Microsoft Security Essentials) bins it straight away. We're not all about to change or disable our anti-virus so that we can download and install your driver.

Let's also be clear that the driver is not the problem here. The installer .exe is the problem. It needs to be resolved.

Roger that, we'll have a look ASAP.

 

[scrypt]

That's all very well but I am currently unable to download the driver because the anti-virus (Microsoft Security Essentials) bins it straight away. We're not all about to change or disable our anti-virus so that we can download and install your driver.

Let's also be clear that the driver is not the problem here. The installer .exe is the problem. It needs to be resolved.

Roger that, we'll have a look ASAP.

Good to ken. How's that aforementioned "look" going, since I have precisely the same issue as technobear, and other iFi users must experience it as well?

 

[technobear]

I've sent the driver installer file to the Windows Defender Security Intelligence Team at Microsoft for further analysis. In the meantime, the only way to download and run it is to disable the anti-virus while you do it. The driver itself, once installed, is fine. It's only the installer that is causing issues.

 

[jmpsmash]

I had exactly the same problem you saw, my work PC has anti-virus that quarantines the iFi driver .exe immediately after download.

If you are able to use another system, say your home system and given you trust iFi that their software is indeed NOT malicious, you can run the .exe from your non-work system. As the .exe is essentially just an extraction program, you can copy the driver files over once the actual driver files are extracted. and then you can go to your work PC's device manager, select the iFi device, and the install the driver there.

That worked for me.