Native Access Won't Launch (Not Responding)

Hi Everyone,

I know this has been a common in the past and I've tried to read through all the info I can find, but so far nothing has worked. That's why I am creating a new thread here.

My computer:
Custom Built
Windows 10 Pro
Motherboard: MSI Gaming Edge AC Z390
Processor: Intel i7 8700k
RAM: 32GB DDR4

Native Access was working fine for me a few days ago. Yesterday (or the day before), Windows kept telling me I was way behind on updates and that my system wouldn't be supported if I didn't update (I'm paraphrasing that, obviously). I didn't think too much about it and was just annoyed with it, so I clicked update.

Well, ever since then I haven't been able to open Native Access. When I try it just appears as a white window and says "not responding" after 5 or 10 seconds.

Things I've tried:
- Restarting the computer
- Running NA in administrator mode
- Uninstalling and reinstalling NA
- Disabling my internet connection
- Right clicking NA and "Troubleshoot Compatibility"
- Disabling all Firewalls

At this point, I'm not sure what else to try. Do you guys have any suggestions?

 

https://www.tenforums.com/tutorials/113380-enable-disable-controlled-folder-access-windows-10-a.html

You could try to disable the ransomware protection temporarily if it is enabled. It protects the user folder but also prevents programs to write there, but normally you'll get a prompt in the right zone (click outer right in taskbar a sign like a written paper, there are some status things) and then you can set the programs as trusted. Maybe it is that issue cause if I remember correctly this was optional and not set on but with an update it is set on.

Uwe

 

Is this only Native Access or are more programs misbehaving? What happens if you try to load an instrument or whatever you got in stand alone mode and then load a standard preset or something you set up?

 

Thanks for the quick replies!
Uwe303 - I just tried your suggestion. I checked and the ransomware protection is off. I turned it on and allowed Native Access, but still not working. So I turned it off, and again still no luck.

ShelLuser - Yes, only Native Access is giving me issues. I can use the rest of my computer, software, plugins, virtual instruments, etc... as normal.

I still have some NI instruments that I haven't installed yet though. That is why I am needing Native Access to work.

 

Have you checked again manually for updates as long as there is not one left.

Uwe

 

Uwe303 - I just checked. Apparently, there were some updates available. However, after running the updates nothing has changed. Native Access still will not run.

 

I don't follow... how could you use N.A. to check for updates if it doesn't run?

 

I apologize for not being clear.

I was referring to Windows updates.

 

I apologize as well because when re-reading I also noticed that I was a little dense up there and overlooked the topic.

OK... what happens if you just let things running? So, leave the white window as-is and wait for 5 - 10 minutes?

This may sound silly, but I'm dead serious. Sometimes it can stall and it might take a while before it comes up with an actual error message. Unfortunately it doesn't seem to keep a log (I checked) but... wait a second...

Ok... so what happens if you try this (don't worry: this is non-destructive):

• Start a file browser ('explorer.exe') and then go to: "%appdata%\..\local\Native Instruments\Native access\cache".
• You'll see 2 folders (so I assume): "network_cache" and "qmlcache", delete both.
• If you don't trust this action: cut & paste them into another folder outside the appdata area.
  • For the record: I never give advice which I wouldn't follow myself (if I do I'd mention the risks), in this case both folders will be automatically recreated by the application. So no reason to worry.
• Try starting Native Access again.

Does this have any effect?

Cache is temporary data which the program stores for faster (future) retrieval, that's the theory anyway. But cache can also work against you if something "bad" happened and found its way into the cache; then the "bad stuff" would always surface as soon as the cache got read and processed.

Do note: I have no idea if this will have an effect, but it does seem logical to me that it could.

Hope this can help!

PS: it it still reacts the same: please leave it running for 10 or so minutes to see if it spits out any kind of error.

 

I've managed to fix the problem. I found this link - https://support.native-instruments....-Installing-or-Starting-Native-Access-WIZARD-

The Native Access Wizard recommended me doing what you said and deleting the cache folder, but that didn't work. So, it then recommended me unplugging the second monitor in a dual-screen setup if I was using one (which I am). So I did that and restarted Native Access... and it worked.

I have no idea why this would have any effect on the app running, but it did apparently.

ADVICE TO NATIVE INSTRUMENTS ( Matt @ NI ) - It'd be great if this Native Access Wizard Tool was more easily accessible through your website. But I've never heard of it until I found a link to it on an online forum. It helped me solve my problem and I'm guessing it could help many others as well.

To everyone else, especially ShelLuser - Thank you for all your help! Sometimes forum communities can be degrading and quite the opposite of helpful. I appreciate all your input in helping me through this. Thank you

 

This worked for me also!!! (I had the blank NI Access window screen at startup as well)
Thank you for sharing this helpful solution! I would've never guessed this could actually work..

BR, Peter


EDIT:

Native Access starts up correctly (update search + automatic login) ... but really only if i use my main notebook screen and disconnect my second screen every time i start Native Access. This seems to be a bug. caseyleesharp: is it like that also on your computer?
Matt @ NI : Is this a known bug?

 

I just ran into the very same issue. After a couple of hours searching the interweb for answers I finnaly found that, in my case any way, that it was completely caused by have two monitors. As soon as I turned off my second monitor it launched and is working just fine. While it was finally open I started the second monitor back up and it continued to run without issue. Why a second monitor causes this problem is beyond me but that is was resolved the problem.

What this means, though, is i have to turn off my second monitor anytime i want to use NA to work correctly. Once it opens up I can then turn on my second monitor........Hope this helps

Ron

 

Ron Coleman

yeah, i have the exact same issue lately.
it looks like this

https://free-picload.com/images/2020/10/08/Zwischenablage01cea018c4144e0983.md.jpg

 

Yep, thats it.......just not extend to the second monitor, launch NA, then extend to the other monitor......thats what worked.....crazy.....most composers normally use two monitors.

 

@all

can someone chime in who is beta testing Native Access and open a bug report on this in the NI beta forum?

 

This has been bugging me for a couple of weeks. I'm pleased to report that there is a simple fix that does not involve having to disconnect the video cable from your second monitor. It's worked for me, but BACK UP YOUR REGISTRY before you try this, just in case.

In regedit, go to
Computer\HKEY_CURRENT_USER\SOFTWARE\Native Instruments\Native Access

and find the string "WindowGeometry". Its value should be "@Rect(xxx xxx xxx xxx)" where the x's are two-, three- or four-digit numbers.

The first pair of numbers will be the x and y coordinate of the top left hand pixel of the window. Let me guess: in your registry, the x-coordinate has somehow been set to 3800 or so?

The second pair of numbers are the window dimensions in pixels, horizontally and vertically.

So in the registry editor, right-click on WindowGeometry, select "modify" and change the string value to:

@Rect(0 0 870 600)

Close regedit, run NativeAccess. It should work fine with the window appearing in the top left-hand corner of your first monitor.

Cheers
Chris

 

thx!

I have another workaround: I set the notebook monitor as primary desktop (1) and the external monitor as secondary. Then the GUI of Native Access and some VST plugins show up again normal.

Peter

 

WOW...Yes, Peter is right. Setting your primary monitor will allow NA to work.
Right-click on display and select "Display Settings"
Select the #1 monitor as primary
Start NA

Incidentally, this isn't the only program I found with this issue recently. "Wolfenstein New Order" (it's a game) has exactly the same issue. However, the difference is that the game HASNT BEEN IN ACTIVE DEVELOPMENT FOR HALF A DECADE.

Seriously tired of the lame bugs with NI products. I spent quite a bit of $ with them. The audio portion of their software is good but the coding ... not so. Don't get me started about 2 hours of getting Komplete Audio ASIO working on a brand new PC install. (the trick is you have to do things in order or you are removing / upgrading drivers by hand)

 

Thank you Chris! This is the only thing that worked for me. My monitors were already set up as primary and secondary, and resetting did not help. Your RegEdit fix did the trick.