I cannot launch Native Access

Of course it's significant.

But thousands of people like me are using it just fine. I start it up shortly after a reboot and it's usually up and running until the next time I reboot, usually a week or two later. So being accusatory is not going to help you. Yes, sometimes NA has problems. But for many, it has been reliable, especially the newer versions of it. So please treat this as a "can-do opportunity", and maybe we can get you going.

Both you and the OP need to help us help you.

1. Please provide your OS and version.
2. What version of NA did you install?
3. Did you see any unusual messages during the installation of NA? Perhaps something about dependencies or admin authority?

That's a start. Please provide that info and we'll see if somebody here can come up with ideas for you.

Yo BIF, I appreciate you stepping in to help and I understand how I may have sounded accusatory while thinking I was expressing some exasperation. Nonetheless, I will try to be as considerate as possible, which I usually am. 😉

I wasn't certain how long it would take to solve my issue, if it could be solved at all in the time frame I was wanting. So, after a couple of hours of using the Deployment Image Servicing and Management (DISM) tool among several others, and operating from a clean Win11 install partition on a separate SSD I keep purely for emergencies, I determined the culprit was a particular .dll as follows:

ChatGPT: "The msvcp140.dll file is a Dynamic Link Library (DLL) file associated with the Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, and 2019. It is part of the Microsoft Visual C++ runtime library and provides standard C++ library functions, such as input/output stream handling, algorithms, and utilities, which are used by applications and programs developed with Microsoft Visual C++." Reinstalling MVC++ didn't help, so I used another technique.

The problem likely occured while I was running Native Access 2 and my CPU hung while running (ironically) Cubase 13 Pro thereby forcing me to make a cold restart. On reboot, apparently NA2 would not launch because it 'thought' it was already running due to a condition stored in msvcp140.dll which resides in \Windows\System32. Strangely, Task Manager indicated NA2 was running (when it wasn't) and would not permit me to exit the 'running' app.

After a number of experiments, the solution was a complete uninstall of NA2 using Native Access 2 uninstall.exe, then replacing the problematic msvcp140.dll with a known good one from my donor Win11 partition while running Win11 from the donor drive. Then restarting the problematic CPU and reinstalling NA2. Launch succeeded yet took a bit longer than normal for a credentials check and then went into initial refresh-plugins etc mode for 30 minutes (much too long but I gave it plenty of time). I stopped it by simply clicking X on the app then I was able to restart it perfectly, ID, serials and all my sounds and plugins fully restored and functional.

Whew! I'm glad I avoided a complete Win11 clean reinstall on account of one locked .dll file. I don't know whether I found a bug in NA2 but I hope the devs are watching and can give an opinion.

So BIF, when's the next time you'd like me to wash your car?

Your friend,

Marty McFly

😃

They regarded my successful temporary solution for the problem after an extensive bug hunt… replacing msvcp140.dll with a clean version. In my case NA2 would not launch after a system freeze because NA2 was permanently locked into an "on" state. Were my previous posts too lengthy, perhaps?