Problems with Windows 10 and Komplete Audio 6 Mk 1 driver

sylpre
sylpre Member Posts: 28 Member
edited April 12 in Other Software & Hardware

Sometime at the end of 2024, Microsoft released an update for Windows 10. Since then, Windows has repeatedly kicked out the audio driver. I have tried many things with the help of ChatGPT, which has not yet helped to solve the problem. You always have to disconnect and reconnect Komplete Audio 6. Just annoying! It can't be that we now have to constantly buy new hardware just because Microsoft thinks it has to release new updates every now and then that cause our studio technology to stop working.

Tagged:

Answers

  • Vocalpoint
    Vocalpoint Member Posts: 3,580 Expert
    edited April 12

    If you are using this driver (which appears to be the only one):

    image.png

    This device (and its driver) dates to Feb 2011 - which is 4 years prior to the first release of Windows 10 - making this a Windows 7 driver - at best.

    And if you are assuming that this driver would somehow still be fully supported within Windows 10 22H2 - which is 11+ years after that device/driver was released - that is probably wishful thinking as well.

    Really do not think MS is out to get you - more like 12 years has gone by and MS is not even aware this device still exists.

    Finally - just saw this Reddit post - from 12 days ago (with an official NI response) indicating that Komplete Audio 6 has now reached EOL (End of Life):

    image.png

    Probably time to consider a new device

    VP

  • LostInFoundation
    LostInFoundation Member Posts: 5,262 Expert
    edited April 12

    Newer driver is available (4.2.0) and it’s stated for Windows 7 and above.

    You can find it in “DRIVERS & OTHER FILES” official NI page:

    https://www.native-instruments.com/en/support/downloads/drivers-other-files/

    On the same page you can also find Device Updater 1.7.0, from 23.07.2018

  • Vocalpoint
    Vocalpoint Member Posts: 3,580 Expert
    edited April 12
    https://community.native-instruments.com/discussion/comment/221312#Comment_221312

    Thanks LIF - My bad. Should work fine.

    VP

  • LostInFoundation
    LostInFoundation Member Posts: 5,262 Expert
    edited April 12

    I hope. I posted just the existence of newer driver (and the device updater)… not that sure that it will solve the issue.

    We don’t even know if he is maybe already using this version of the driver

  • sylpre
    sylpre Member Posts: 28 Member
    https://community.native-instruments.com/discussion/comment/221327#Comment_221327

    Thank you for your reply. I'm already using this version.

  • Vocalpoint
    Vocalpoint Member Posts: 3,580 Expert
    https://community.native-instruments.com/discussion/comment/221425#Comment_221425

    Well - if this device is EOL (as I previously indicated) AND Windows 10 (and some update) has caused this - it is highly unlikely that NI will start coding a new driver at this juncture.

    Suggest you contact NI Support and see what can be done. This is your only option at this point.

    VP

  • sylpre
    sylpre Member Posts: 28 Member

    How can I get in touch with the Native Instruments support? Since they left Germany there is no support hotline anymore or support e-mail contact or something. At least I can't find it.

  • LostInFoundation
    LostInFoundation Member Posts: 5,262 Expert

    This is the link for Traktor section of Support. Remember to log in at the bottom of the page in order to have access to chat (during office time) or open a ticket

    https://support.native-instruments.com/hc/en-us/sections/15449821909021

  • sylpre
    sylpre Member Posts: 28 Member

    Update: A couple of days ago I have deactivated the Windows systems sounds and since then I don't have any problems with that anymore. I don't know if this caused that problem or something else. But now everything works as it should be.

  • LostInFoundation
    LostInFoundation Member Posts: 5,262 Expert

    Thank you for reporting back

  • sylpre
    sylpre Member Posts: 28 Member

    Update 2: The "Watchdog Violation" bluescreen appears again. Deactivating the Windows system sounds was obviously not the solution. I did some research and found out that the whole thing is quite complex. It could be caused by all sorts of things. But it definitely seems to be down to some kind of driver. I think it's about time the IT industry came up with a better solution. There's always something that needs updating again and again. Back in the day, 25 years ago, you’d get maybe one or two updates for the entire system per year. These days, you get a message every week, sometimes even twice a week, just to update the web browser. All we want are systems we've built ourselves or had custom-made that work – and keep working – until the end, without constantly running into problems just because another update has broken the system. It's really starting to get on my nerves.

  • Vocalpoint
    Vocalpoint Member Posts: 3,580 Expert

    "All we want are systems we've built ourselves or had custom-made that work – and keep working – until the end, without constantly running into problems just because another update has broken the system"

    This is very easily accomplished. Simply never update anything once you get to a solid state and keep on rolling. If you are allowing Microsoft (in this case) to install updates in any way - you should be prepared for chaos.

    MS has no idea you are using an audio interface from 2011 and cannot ensure any updates they do - to their own OS - will affect you. By allowing updates - you are opening the door to trouble.

    If you want a guaranteed environment - shut down Windows updates, unplug your network cable and rock on. The system should continue to work fine - potentially forever - if you leave it alone.

    VP

Back To Top

Categories