Battery 4 Factory Library Install Fails using NA 2

Niktoman
Niktoman Member Posts: 3 Newcomer
in Battery 4

I hope the NI folks read this. I’m sorry to be so jaded with the user community who didn’t cause these problems.

The Battery 4 Factory Library install process using NA 2 currently fails due to an ISO file mount problem. I am using a brand new Win10 install that is perfectly clean with brand new ASUS/Intel hardware. Just to note, new/updated Win10 builds require things like GPT partition tables along with UEFI boot. I have installed or deinstalled nothing that would impact CD/DVD filter drivers, virtual or otherwise. So, I just want to get this straight, the NI solution for the install bug is for me to edit my virgin Win10 System Registry and “repair” the disk mounting filter settings? You’ve got to be kidding!! This is the only solution? I can’t believe this!! Read on….

I am building a new DAW from an old DAW that had Battery 4 installed (using Win10). So, I have the Factory Library from the old install and I copied it to the new DAW content drive. I can access the kits and the samples from new Battery 4 through navigation but I cannot set the library as the default because the Scan button is greyed out in Edit>Preferences>Library, so the library does not show up in Battery 4. Is this something the Factory Library install sets? Is there a way to “repair” this situation?

While I have been writing this, the same mount error has occurred for the India product install. In that case, it’s not a content library, it’s the whole product.

Just tell me there is no alternative to these installation bugs but to edit my Registry. That’s all I want to know. And btw, the Microsoft article warns that doing the filter driver edits might break other things.

Answers

  • Vocalpoint
    Vocalpoint Member Posts: 2,718 Expert

    You have bigger issue here if more than one library is failing.

    I too have a brand new Windows 10 22H2 install on 2024 Intel/ASUS Hardware and have never seen anything referencing an ISO file mount problem, filter drivers and so on.

    Can you post a screen cap of the error - as this is not a normal error that I have ever seen in my travels and I have been building DAWs and using NI products - since 2002.

    Including Battery, India and all the rest of the usual suspects.

    VP

  • Niktoman
    Niktoman Member Posts: 3 Newcomer

    Vocalpoint: Thanks for your reply. Win10 22H2 x64v1 is what I installed four days ago. It was a squeaky clean install. I too have decades of build experience. Let's not discuss how far back I go.

    Just to review, using NA 2, I successfully installed the Battery4 app, Grandeur, and Kontakt 8 (free version). The products that failed were Battery 4 Factory Library and India. Not everything fails, so what do the failing install processes have in common? I'm not asking you, but someone at NI knows. 

    I will update this post tomorrow with more info. Based on NI info, the error msg leads directly to the NI post shown below. In my original post, I mentioned the troublesome Microsoft info referenced in this NI post.

    I have Acronis full images taken at multiple restore points throughout this build and one is immediately after the squeaky clean Win10 install.

    Vocalpoint: Thanks for your reply. Win10 22H2 x64v1 is what I installed four days ago. It was a squeaky clean install. I too have decades of build experience. Let's not discuss how far back I go.Just to review, using NA 2, I successfully installed the Battery 4 app, Grandeur, and Kontakt 8 (free version). The products that failed were the Battery 4 Factory Library and India. Not everything fails, so what do the failing install processes have in common? I'm not asking you, but someone at NI knows.

    I will update this post tomorrow with more info. Based on NI info, the error msg leads directly to the NI post https://support.native-instruments.com/hc/en-us/articles/115005761245-Native-Access-Error-Message-Error-while-mounting-disk-image. In my original post, I mentioned the Microsoft info referenced in this NI post.

    I have an Acronis full image taken at multiple restore points throughout this build and one is immediately after the Win10 install.

  • Niktoman
    Niktoman Member Posts: 3 Newcomer

    I restored my boot partition to the point immediately after Win10 was cleanly installed and nothing else was installed. The NI products installed cleanly. So I then restored to the point right before I previously started installing the NI products. I checked and found that only Explorer was opening ISO files. This time I succumbed to the Registry change outlined in the link mentioned above (NI won’t let me post a link). Everything works now. So if a previous install somehow triggered a virtual CDROM mount filter problem then it had to have something to do with Steinberg or GForce products. Those were the only things installed prior to NI and they installed cleanly. I’m still not happy about the time I spent on this problem and I suggest NI is using an install process that will see lots of future problems unless it is changed.

Back To Top

Categories