Ozone not working after Native Access update 12.1

WilliamAshley

So I have Ozone elements as well as standard from Komplete Signature Series for FL Studio. I noticed today that Ozone is not working and even after I uninstall Ozone from windows app and features it still shows as installed in native access. Reinstalling doesn't fix the issue. When I load Ozone it initially seems to load but then freezes fl studio's GUI and the whole program's gui gets locked out. This did not previously occur. Something has caused this plugin to start crashing FL Studio with a non visible window. Saving a project that has ozone loaded results in that project crashing on loading, and the ozone wrapper ends up just being a black screen and the entire fl studio gui is locked out. Keyboard doesn't work and mouse can't interact.

I've been told the source of the issue is with Native Instruments not FL Studio.

My native access seems to have updated to the most recent version when it was launched As far as I can tell it is just Ozone that isn't launching properly. Are there some services required to be running for Ozone to load? Is this connected to the internet or something? Guitar Rig 7 loads fine but Ozone just utterly fails to launch properly and corrupts the project. This bug more or less derailed my day.

Jeremy_NI

Make sure to completely uninstall Ozone following these steps: How to Uninstall Native Instruments Software from a Windows Computer

Then reinstall from here:

Download Ozone 11 Standard:

Windows OS: https://downloads.izotope.com/product_download/iZotope_Ozone_Standard_v11_0_1.exe

Mac OS: https://downloads.izotope.com/product_download/iZotope_Ozone_Standard_v11_0_1.dmg

If that doesn't solve the issue please get in touch here: https://bit.ly/Izo_support_ozone

WilliamAshley

Yes I uninstalled and reinstalled ozone but it didn't initially fix it. What fixed standard for me was to uninstall all ozone applications including imager and eq as well as standard and elements. Then I uninstalled native access, rebooted. Reinstalled native access, the reinstalled standard and eq and standard was working again. I then "repaired" the elements copy and it then loaded ok. However after I reinstalled iZotope Vinyl I encountered the bug where the GUI froze out again.

As far as I understand this has to do with microsoft webview and utilities as the error screen is showing up in task manager in webview. I am not sure if it has to do with windows putting the plugin into utility mode or some type of GPU process on my Ryzen 7 system using AMD internal gpu it is happening on a mini PC Ser 7 pro with AMD Radeon 780M GPU. While uninstalling ozone in windows apps and uninstalling native access then reinstalling did fix the bug for ozone loading, after repairing elements and installing vinyl from izotope product manager, as I only have certain plugins through iZotope product manager not native access, the same bug occured - I think this time the same bug that occured in ozone occured in vinyl but I don't 100% know if it was vinyl as I only think vinyl was loaded in this project not any other native instruments plugin - but the gpu lockout did occur after this. Note that it is being triggered I think by some type of edge webview process linked to the plugin when I think the GPU gets called not 100% sure but the GUI of the plugin is all black when loading and it seems like there is some type of unfilled interupt that locks FL Studio's gui out. Midi and midi transport continues to work through external devices but the mouse and keyboard stop functioning when this happens with FL Studio. So its like the GUI and mouse and keyobard get locked out. Playback continues through my ASIO device and midi devices continue commuicating with FL Studios engine but it crashes FL Studios GUI. The weird thing is there is some type of delay before it kicks in when it is loading so I was able to quickly able to get into the mixer after reloading this time, it seems like something triggers is — perhaps when the plugin is reengaged from being in a smart disable state or I am not sure if there is some type of validation process that gets routed to online verification when the plugin is loaded even after it is installed and verified, but it almost seems like the plugin is trying to phone home and this causes the GUI of the plugin to crash and FL Studio to get locked out when whatever this process is fails through webview not 100% sure.

Is it possible that these plugins crash when they fail to connect with NI servers for some type of verification process? It may be unrelated but error.html seems to pop up in task manager when this crash happens with the NI plugins. While I think ozone is working again I have this same issue with iZotope vinyl now I think or something is causing this exact same crash in another NI related plugin.

WilliamAshley

BTW I will start a process with ozone support but I am thinking it may have to do with sometype iZotope and NI verification through webview that may have dependencies that can't be met and it is some type of interrupt that locks out the graphics processes until it is filled.

WilliamAshley

Note these are all registered plugins that previously worked, so it feels like something in the update broke them.

WilliamAshley

Also I am curious what happens if a plugin that multiple copies are owned is installed in both native access and izotope product portal can it cause it to check both programs for status resulting in some type of bug?

Jeremy_NI

@WilliamAshley My knowledge on Ozone is quite limited, if you're in touch with Izo's support please continue with them until a solution is found.