Launch Pad 2 Driver

[Shima Costar]

Iwanted to know if anyone could help me out with this issue, i just updgraded my laptop's OS from Vista to Win 7 and the only driver that i noticed that its being missing its the one for the Quick Launch Buttons.

I appriciate your post however the driver you suggested did not work on either of the two DV 6000 that I tried it on. One was running Win7 Ultimate x64 and the other had Win7 Home (32 bit) installed on it.

I've purchased a new XtremPro 96kHz/24bit USB headphone interface to replace my old 48kHz max nuForce headphone interface. The XtremPro didn't get recognized by Cakewalk, so I switched to the WDM/KS driver, and now when I launch Cakewalk it goes through the audio interface setup but won't run Cakewalk. No obvious Cakewalk processes in Task Manager (running Wn11). I don't have a way to switch driver types since I can't open the Preferences dialog from within Cakewalk, and I've not found any files or registry settings that contain the driver settings (no, I've not changed anything - yet).

That did it. Thanks a bunch @scook!

I also got the onboarding dialog, which I didn't want, so I ended the Cakewalk task, set OnboardingShown to 2 and fired up Cakewalk successfully with my old working settings.

If I remember correctly, "unplugging" the device on which Cakewalk was stuck have enabled me to choose different one. That was with one of virtual interfaces inside virtual machine, but I think that should work with real device on real computer as well. Probably disabling the interface in Windows also helps.

@azslow3 Kind of an unnecessary PS for someone using RME and Sound Devices. I sometimes need a dongle that would allow me to edit 96kHz/24bit projects on headphones without additional hardware beyond a laptop. Do I wish it was ASIO compliant? Sure. I'm open to suggestions.

You have probably misunderstood my point (or humor in which it was packed). I just mean such devices are not targeting the same applications as specialized music creation interfaces nor have the quality/stability of RME. In other words such problems can be expected.

That did it. Thanks a bunch @scook!

I also got the onboarding dialog, which I didn't want, so I ended the Cakewalk task, set OnboardingShown to 2 and fired up Cakewalk successfully with my old working settings.

With all due respect, I don't think it's a Cakewalk bug if your audio driver hangs the app

However, your point is taken - within limits there are things that can be done to mitigate bad audio driver behavior. I'm not sure if it would help in your case however.

In WDM mode we're at the mercy of how Windows drivers interact with the app if the driver deadlocks there isn't much the app can do. However perhaps we can remember an improper shutdown and reset the driver mode on next launch. Also did you already try launching in safe mode?

I couldn't spot the variable in the Registry as suggested above, so tried a reboot into Windows10 safe mode , after which I was able to start Cakewalk fine and re-set the driver mode to ASIO. Once rebooted in normal mode, all was OK. Phew.

@Noel Borthwick - I also think that Cakewalk ought to figure out when it is caught in a driver issue loop, and offer the user some way to switch drivers (eg to ASIO) on a restart - this issue seems too easy to fall into, and then novice users are lost . Cheers !

I suspect this is a well understood issue by some, but I'm a little confused how this is supposed to work and to my surprise, I don't see this widely reported as a problem and can't find a solution online, so I suspect I'm just doing something stupid.

I've used RST for at least 14 years, maybe longer (don't recall when I started using on-board RAID as good-enough in place of a dedicated card) for monitoring RAID integrity, tuning cache levels, rebuilding volumes, etc., across dozens of systems. I know that more recently (a few years ago, under Windows 10) Intel and Microsoft moved from the Intel-provided GUI to the one in the Microsoft Store, the "Intel Optane Memory and Storage Management" application. What I don't understand is what powers the back-end, the actual RAID monitoring software or drivers. I assume that's why I am getting the following error preventing the app from launching. The listed error code doesn't map to anything that seems relevant: other than not being able to launch the app to check the settings, everything seems to be running fine.

I run RAID 1 on the computer in question (others run RAID 5 and RAID 10). I set that up in the BIOS (various MoBo's, but this one happens to be MSI, using Intel's Z790 chipset). In order to install Windows, I need to install the RAID drivers from the f6vmdflpy-x64 folder, which is the same process I've used for more than decade. Without the drivers added during install, the Windows installer doesn't even see the drive and won't install. So I know that from the moment of install, it's using the Intel drivers. So far, so good.

Then, once Windows us up and running, I can install the Intel Driver and Support Assistant and the Intel Optane Memory and Storage Management apps. The Intel D&SA used to also update RST, but now it seems to ignore it and only address networking and embedded graphics. The Optane Memory and Storage Management app seems to require a current version of the RST software to be able to provide a report on the RAID array and drives.

Also SOMETIMES, the Intel Optane Memory and Storage Management starts and runs fine without that error. I think, but I'm not sure, that it runs after a restart or maybe if I manually reinstall the RST from MSI for the motherboard (but those have never changed, so don't understand why it would work after a fresh re-install, then later report that I need to update the drivers as shown in that error message).

Where am I supposed to get that and how do I keep it up to date, now that the Intel D&SA no longer updates it? I really don't want to have to restart the computer every time I want to check on the RAID drivers. Or am I looking at this all wrong and there's a different way I should handle this now that Intel has changed how this works (like maybe the Intel Optane Memory and Storage Management isn't even the right tool for this)?

Please be aware that Intel DSA was designed for products manufactured by Intel, such as Intel NUCs, not for OEM systems (Original Equipment Manufacturers). In any case, the Intel RST drivers are provided by the OEM, since Intel drivers are generic. You can find the Intel RST generic drivers in the Download Center.

Note: We recommend checking with your System Manufacturer and using the driver software provided by them to avoid potential installation incompatibilities. Intel supplies generic versions of RST Drivers for general purposes. Computer manufacturers might have changed the features, incorporated customizations, or made other changes to the RST driver software or software packaging.

Typical Intel screw up on these support forums. It's like your goal is to close the tickets before users can actually get a resolution. I had specifically told you that I needed time to test. Does your insulting fast closure help you earn a bonus for a speedy resolution, when all you've done is screw over you customer? Again... (this is about the third or fourth time you've done this in the past couple of years, others relating to your video drivers fighting with Microsoft Update).

Now that I've had a chance to observe this across a few restarts, I can see that it ALWAYS works after a restart, and seems to always fail after a few days of being up and running. I don't know that this is Intel's fault, but this is the ONLY app that has this problem. So something causes the Intel Optane Memory and Storage Management application to no longer be able to launch after a while. As far as I can tell, the drivers are still working just fine, it's just the Intel Optane Memory and Storage Management application won't launch.

Therefore, my work-around, if I want to launch Intel Optane Memory and Storage Management application to check on my RAID drive status, is to restart the computer. That's not acceptable and Intel should be more concerned about understanding and fixing this defect.

Note that the rest of your "answer" did not directly address my question anyway. I had asked "Where am I supposed to get that and how do I keep it up to date, now that the Intel D&SA no longer updates it? I really don't want to have to restart the computer every time I want to check on the RAID drivers. Or am I looking at this all wrong and there's a different way I should handle this now that Intel has changed how this works (like maybe the Intel Optane Memory and Storage Management isn't even the right tool for this)?"

In the Intel RST drivers at Intel.com, the only ones I see that are newer, dated in 2023, show a version number of 19.5.2.1049.4 or 19.5.2.1049.5, but those appear to be for NUC systems or CLI access only. Which one of those should I use with the Intel Z790 chipset on a regular 13th gen i9 system for a RAID 1 configuration?

Today, I have installed version # 19.5.2.1049.5 from -rapid-storage-technology-driver-installation-software-with-intel-optane-memory-11th-and-12th-gen-platforms.html?wapkw=rst. It appears to show the same version and date I had previously. I have restarted and everything seems to work fine now, but it ALWAYS works fine after a restart, so because nothing appears to have changed, I expect this problem is not fixed (but would love to be wrong about that).

3a8082e126