1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

Please STOP installing all NI drivers!

Discussion in 'MASCHINE Area' started by TRW, Dec 19, 2017.

  1. The Sarge

    The Sarge NI Product Owner

    Messages:
    643
    +1 to the topic

    wanted to check the update of some Maschine Expansions and doing some try-outs in Cubase and this welcomes me with: "new drivers found, which one do you wanna use...including Maschine MK3"
    unfortunately I´ve got only a Maschine MK2 - why the hack were drivers for MK3 and Guitar-Rig etc. installed as Audio-drivers???
    my system was running, before the updates, perfectly - now I´ve got "no response from Cubase.exe or HALion.exe"....thanks NI for NOTHING!!!
     
  2. CakeAlexS

    CakeAlexS NI Product Owner

    Messages:
    5,431
    To be fair the only thing that will happen is disk space being taken up. In order to run the drivers you need the actual hardware. The only way this could be related to your system being unstable is if you are running out of disk space.
     
    • Like Like x 1
  3. Masch1ne

    Masch1ne NI Product Owner

    Messages:
    317
    The only time this bothers me is when I'm changing interface and I have 15 to scroll through 12 of them I dont even own. Other than that I'm not too fussed.
     
  4. The Sarge

    The Sarge NI Product Owner

    Messages:
    643
    Cubase/Steinberg-software seems to be sensitive to unlogical changes ;)
    I know that I need the hardware to use the drivers, and due to not having this hardware my system even don´t need those - but why NI installing software which is not necessary for my system? <- that´s the boring and making me angry point
    and to your memory-assumption: I´ve got 91GB free at my system-SSD, I think enough to handle disk-space-problems
    nevertheless thanks for your help
     
  5. CakeAlexS

    CakeAlexS NI Product Owner

    Messages:
    5,431
    I don't know what happened but the drivers do NOT actually run or install unless you plug in the correct hardware. This is all to do with Windows OS and nothing to do with your applications. All NI is basically copying over the driver packages.

    Cubase does has virtual ASIO drivers that can often cause problems and need uninstalling, I would check that.
     
    • Like Like x 1
  6. CakeAlexS

    CakeAlexS NI Product Owner

    Messages:
    5,431
    • Informative Informative x 1
  7. The Sarge

    The Sarge NI Product Owner

    Messages:
    643
    ok, I´ll try to fix it on weekend
    thanks for help again
     
    • Like Like x 1
  8. Engin Ypsilon

    Engin Ypsilon New Member

    Messages:
    3
    It seems it's on us, to solve this "issue" ...

    On Windows, you can use the Exploit-protection service, just add all the unnecessary Drivers and block them ...

    Code:
    <?xml version="1.0" encoding="UTF-8"?>
    <MitigationPolicy>
    
      <AppConfig Executable="Traktor Audio 2 MK2 Driver Setup PC.exe">
        <DynamicCode BlockDynamicCode="true" AllowThreadsToOptOut="false" Audit="false" />
        <ImageLoad BlockRemoteImageLoads="true" AuditRemoteImageLoads="false" BlockLowLabelImageLoads="true" AuditLowLabelImageLoads="false" />
      </AppConfig>
    
      <AppConfig Executable="Traktor Audio 6 Driver Setup PC.exe">
        <DynamicCode BlockDynamicCode="true" AllowThreadsToOptOut="false" Audit="false" />
        <ImageLoad BlockRemoteImageLoads="true" AuditRemoteImageLoads="false" BlockLowLabelImageLoads="true" AuditLowLabelImageLoads="false" />
      </AppConfig>
    
      <AppConfig Executable="Traktor Audio 10 Driver Setup PC.exe">
        <DynamicCode BlockDynamicCode="true" AllowThreadsToOptOut="false" Audit="false" />
        <ImageLoad BlockRemoteImageLoads="true" AuditRemoteImageLoads="false" BlockLowLabelImageLoads="true" AuditLowLabelImageLoads="false" />
      </AppConfig>
    
      <AppConfig Executable="Traktor Kontrol D2 Driver Setup PC.exe">
        <DynamicCode BlockDynamicCode="true" AllowThreadsToOptOut="false" Audit="false" />
        <ImageLoad BlockRemoteImageLoads="true" AuditRemoteImageLoads="false" BlockLowLabelImageLoads="true" AuditLowLabelImageLoads="false" />
      </AppConfig>
    
      <AppConfig Executable="Traktor Kontrol F1 Driver Setup PC.exe">
        <DynamicCode BlockDynamicCode="true" AllowThreadsToOptOut="false" Audit="false" />
        <ImageLoad BlockRemoteImageLoads="true" AuditRemoteImageLoads="false" BlockLowLabelImageLoads="true" AuditLowLabelImageLoads="false" />
      </AppConfig>
    
      <AppConfig Executable="Traktor Kontrol S2 MK2 Driver Setup PC.exe">
        <DynamicCode BlockDynamicCode="true" AllowThreadsToOptOut="false" Audit="false" />
        <ImageLoad BlockRemoteImageLoads="true" AuditRemoteImageLoads="false" BlockLowLabelImageLoads="true" AuditLowLabelImageLoads="false" />
      </AppConfig>
    
      <AppConfig Executable="Traktor Kontrol S4 MK2 Driver Setup PC.exe">
        <DynamicCode BlockDynamicCode="true" AllowThreadsToOptOut="false" Audit="false" />
        <ImageLoad BlockRemoteImageLoads="true" AuditRemoteImageLoads="false" BlockLowLabelImageLoads="true" AuditLowLabelImageLoads="false" />
      </AppConfig>
    
      <AppConfig Executable="Traktor Kontrol S5 Driver Setup PC.exe">
        <DynamicCode BlockDynamicCode="true" AllowThreadsToOptOut="false" Audit="false" />
        <ImageLoad BlockRemoteImageLoads="true" AuditRemoteImageLoads="false" BlockLowLabelImageLoads="true" AuditLowLabelImageLoads="false" />
      </AppConfig>
    
      <AppConfig Executable="Traktor Kontrol S8 Driver Setup PC.exe">
        <DynamicCode BlockDynamicCode="true" AllowThreadsToOptOut="false" Audit="false" />
        <ImageLoad BlockRemoteImageLoads="true" AuditRemoteImageLoads="false" BlockLowLabelImageLoads="false" />
      </AppConfig>
    
      <AppConfig Executable="Traktor Kontrol X1 MK2 Driver Setup PC.exe">
        <DynamicCode BlockDynamicCode="true" AllowThreadsToOptOut="false" Audit="false" />
        <ImageLoad BlockRemoteImageLoads="true" AuditRemoteImageLoads="false" BlockLowLabelImageLoads="true" AuditLowLabelImageLoads="false" />
      </AppConfig>
    
      <AppConfig Executable="Traktor Kontrol Z1 Driver Setup PC.exe">
        <DynamicCode BlockDynamicCode="true" AllowThreadsToOptOut="false" Audit="false" />
        <ImageLoad BlockRemoteImageLoads="true" AuditRemoteImageLoads="false" BlockLowLabelImageLoads="true" AuditLowLabelImageLoads="false" />
      </AppConfig>
    
      <!--
    
    
      The only driver i need, but on my MacBook! My PC is more like a Server, not your Driver trashcan!
      Thx for the unnecessary work, hopefully all this drivers get brandmarked as Malware in all Antivirus ishes ...
      Phase Needles don't work properly, Software-Updates fuqs up the entire day ... and for what?
    
      I'm using this Software since "Final Scratch" around 2004-2005, and it was never that worse ...
    
    
      <AppConfig Executable="Traktor Kontrol Z2 Driver Setup PC.exe">
        <DynamicCode BlockDynamicCode="true" AllowThreadsToOptOut="false" Audit="false" />
        <ImageLoad BlockRemoteImageLoads="true" AuditRemoteImageLoads="false" BlockLowLabelImageLoads="true" AuditLowLabelImageLoads="false" />
      </AppConfig>
    
      -->
    </MitigationPolicy>
    
     
  9. ntula

    ntula NI Product Owner

    Messages:
    2,318
    No longer installs all those drivers on a Mac... but when it did, years back, i would just manually delete them if i forgot to deselect the check box about installing them... the new hardware does not need drivers to connect to the usb units, but native access installs a launch daemon that acts like a server called “helper” and it runs 2 background apps called NIhardware AGENT and NIHOSTING AGENT that the software requires - these are not drivers or extensions for the OS but you could say they are drivers/extensions directly for the software... and you can set them to auto launch and you can quit them. What i used to do was create an “extensions disable” folder in my system (library} and move extensions i was not using , or unsure if i was, into. The problem was even if you delete them, update will re-install them... if you are running legacy software, you may need to figure out where exactly everything is installed on a pc (on the Mac there is an app called “pacifist” that inspects installer and as well lets you manually install, or not install) i am sure on the pc side there is a similar thing and as well directories you can directly manage. If you only need one driver but is installs all the drivers for a respective type of device, then do a “name” search of the driver it installed, to find the directory location, that you need and set aside or remove the ones you do not. I remember this being an issue back when i was using earlier version of KOMPLETE, KORE, and the MK1 that i had to correct manually in the directories.
     
    Last edited: Feb 5, 2021
  10. Uwe303

    Uwe303 Well-Known Member

    Messages:
    6,942
    Cool will try that tomorrow - thx

    Uwe
     
  11. Engin Ypsilon

    Engin Ypsilon New Member

    Messages:
    3
    Sadly, you can't import the Data, i've posted. But with the names given, you can block, what you don't need. For example:
    Code:
      <AppConfig Executable="Traktor Audio 2 MK2 Driver Setup PC.exe">
       <DynamicCode BlockDynamicCode="true" AllowThreadsToOptOut="false" Audit="false" />
       <ImageLoad BlockRemoteImageLoads="true" AuditRemoteImageLoads="false" BlockLowLabelImageLoads="true" AuditLowLabelImageLoads="false" />
      </AppConfig>
    
    From the first line, you need the value from Executable: "Traktor Audio 2 MK2 Driver Setup PC.exe". With this, you can block this driver specifically, without effecting anything else. The Exploit-Service is in (I've a german OS, so they surely be named different)
    Code:
    Settings  >  Updates & Security  >  App- & Browsercontrol  >  Tab: Programmsettings

    You have to make a rule for each driver, you want to block. I've activated (checked) the first three rules given, when adding a new rule by "Programname". If the drivers are already installed, uninstall them first, because after adding to Exploits, they get completely blocked for any action.
     
  12. ntula

    ntula NI Product Owner

    Messages:
    2,318
    Why not just delete or move/rename the extension period. If you do not need it, just delete it instead of blocking it...
     
  13. Engin Ypsilon

    Engin Ypsilon New Member

    Messages:
    3
    Because i've done delete them countless times (it's not even "a" thing that you have to delete, but a dozen), after each new installation, or update, or what ever ... at one point, you're just done with "deleting" ...
     
  14. ntula

    ntula NI Product Owner

    Messages:
    2,318
    I used to go through this when I could still use kore, until I discovered a way to manually install it. it is always better to not install or remove than to rely on a "gatekeeper" to block.