Presonus and ASIO Drive issue on windows

A friend of a friend who is remote is having some audio issues with a windows machine running HW 8.

Upon startup she gets the following:

The following audio or MIDI (or USB-MIDI) interface device(s) can’t be accessed, but Hauptwerk is configured to use them:
• ASIO: Studio USB ASIO Driver
• Studio 1824c MIDI In

And sent a picture of the following message as well:

Could not stop MIDI IN port ‘Studio 1824c MIDI In’. (Operating system message: There is no driver found on your system., code 6 hex 6)

I personally run on Mac, so this is a little foreign to me.

Does she just need to re-install the “ASIO: Studio USB ASIO Drive”?

She is not techy at all, so thinking she did not go in and play with any of the configurations, she said it just started happening a couple months back.

Any advice I can give her would be appreciated.

Scott

It means the PC doesn't see the audio/MIDI interface at the time, so Hauptwerk can't use it. Either Hauptwerk is being started before Windows has time to configure the interface after login, or the interface has a fault. Device Manager should show whether Windows sees the device. Reinstalling the software/drivers for the audio/MIDI interface and updating its firmware would be some first steps to try.

This isn't uncommon. I have to delay starting Hauptwerk for my audio interface to start first, and the time varies from 15 to 20 seconds after logging in. Sometimes I also have to power my MIDI interface off and on again, after logging in and trying to run HW, before Windows and HW can use it.

[mdyde]

Hello Scott,

To add to Mark's list, regarding the "Could not stop MIDI IN port", this post also has some suggestions that might be relevant (e.g. don't plug in/unplug devices whilst Hauptwerk is running, and also disable Windows USB sleep):

viewtopic.php?f=4&t=21171&p=158052#p158052

Oh, I ignored the loss of a previously connected interface. Sorry. Then it can't be that HW is being started too soon.

[mdyde]

I think Scott might have meant that the two errors occur on different occasions? If so, one of those problems might indeed be launching Hauptwerk to soon after the PC is starting up.