1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

Please Update Native Access to Ignore Missing 32bit VST's

Discussion in 'NATIVE ACCESS' started by rdalcroft, 18/6/21.

  1. rdalcroft

    rdalcroft NI Product Owner

    Messages:
    84
    Now that you are removing 32bit Versions of Vst(s)

    Please can you at lease update Native access, so that it does not show (Repair) For these 64bit only Vsts.

    It looks bad, and makes you think there is something wrong with Native access or your setup.

    Why wasn't this done first? Native Accrss.png
     
    rdalcroft, 18/6/21
    #1
  2. paul doolan

    paul doolan NI Product Owner

    Messages:
    87
    I had the same, i just reinstalled them under the repair tag and all is good.
     
    paul doolan, 18/6/21
    #2
  3. rdalcroft

    rdalcroft NI Product Owner

    Messages:
    84
    Until you close and restart native access. I thought the same, lol
     
    rdalcroft, 19/6/21
    #3
  4. Headfirstonly

    Headfirstonly New Member

    Messages:
    10
    Yup. FM8, Massive and the updated FX series now all spawn a "repair" flag in Native Access. It doesn't exactly instil confidence in the product, does it?
     
    Headfirstonly, 19/6/21
    #4
  5. rdalcroft

    rdalcroft NI Product Owner

    Messages:
    84
    I’m thinking they’re waiting until they have updated all apps, and removed all 32bit plugins, and possibly released all vst3 updates before maybe updating native access.
    Bit of a bummer, I never thought I was OCD, until this. Lol.
     
    rdalcroft, 19/6/21
    #5
  6. rdalcroft

    rdalcroft NI Product Owner

    Messages:
    84
    you will need to uninstall them manually then install again from Native Access. Its because a reinstall does not remove the entry in the registry for the 32 bit location.
     
    rdalcroft, 22/10/21
    #6
    • Like Like x 1
  7. Alphagem-O

    Alphagem-O NI Product Owner

    Messages:
    31
    Same problem here :(. Does manually uninstalling the individual plugin fix the issue for good, or does it return eventually.

    Also, how do you best uninstall those manually -- via Windows Control Panel or elsewhere? Thanks!
     
    Alphagem-O, 3/11/21
    #7
  8. DeepThumb

    DeepThumb NI Product Owner

    Messages:
    188
    It's not a problem so just ignore them. I'm quite confident that they will vanish in 5 years or so. ;)
     
    DeepThumb, 3/11/21
    #8
    • Like Like x 2
  9. Blindeddie

    Blindeddie Well-Known Member

    Messages:
    3.665
    Yup, just uninstall like you would any other program through control panel then reinstall through NA.
     
    Blindeddie, 3/11/21
    #9
    • Like Like x 1
  10. rdalcroft

    rdalcroft NI Product Owner

    Messages:
    84
    yes. Uninstall them one by one through add/remove programs. Or Apps if windows 10.
    Then once uninstalled. Go back into Native Access and it will list them to be installed again. Install them.

    no the issue will be gone for good.
    All it is, is an entry in the registry of windows pointing to the location of where the 32 bit vst’s were installed. But because they have now been removed. Native Accra still looks for them.

    mots really bad programming from native instruments. They should have removed that registry entry when they updated the vst’s.
     
    rdalcroft, 4/11/21
    #10
  11. Alphagem-O

    Alphagem-O NI Product Owner

    Messages:
    31
    Thank you for the replies! Manually uninstalling the plugins one by one via the Control Panel, then reinstalling through Native Access solved it for me, at least for now. Much appreciate your help and guidance.

    I hate to say it, but I'm not surprised ...
     
    Alphagem-O, 4/11/21
    #11
    • Like Like x 1
Tags: