So if you trust your software developer and use his products make him a favor and report the flagged software as a false positive to your AV must be using ESET/NOD32 since currently it's the only AV engine that detects the installer as malicious. One problem remained: Since Microsoft introduced Vista, all drivers for 64bit.

It's actually a catch 22 for small developers. Virtual MIDI driver for Windows 7 up to Windows 10, 32 and 64 bit with the. But it's not likely many people will use it since it's flagged. This means programs are flagged as potentially malicious until many people use it. Regarding your AV problem: Nowadays AV solutions tend to be very paranoid and use so called 'reputation based' heuristics. In order to find this folder, Right-Click > Properties on the softwares shortcut. First, you must find the installation folder of the software (the software giving the dll error) you are going to install the dll file to. It installs as a MIDI Output device and forces itself as MIDI device 0. Method 2: Copying the Midimap.dll File to the Software File Folderlink. Why is the installer making my AV software go ape?! Maybe I should just stick with VirtualSynth as it can do the samething and doesn't seem to trigger my AV.Ĭurrent versions of VirtualMidiSynth cannot do the same thing on Win8/10 as CoolSoft MIDIMapper because of the completely missing default midi mapper. CoolSoft MIDIMapper is the missing (and needed) MIDI Mapper for Windows 8, 8.1, 10.

Microsoft midi mapper windows 8