Spectrasonics and Windows Update

Discussion in 'Omnisphere' started by One Reason, Jul 26, 2026 at 5:23 PM.

  1. One Reason

    One Reason Audiosexual

    Joined:
    Jun 11, 2011
    Messages:
    2,780
    Likes Received:
    801
    Location:
    Where I dont want to be
    This may be in the wrong section, please feel free to re-designate if so.

    So. to keep this short and sweet, I have suffered many many de-authorizations to my Spectrasonics cracked apps.. mainly Stylus RMX and Omnisphere 3.

    Drove me fucking Insane until I correlated these events, finally, and once and for all, to the fact that there had been a recent voluntary, or involuntary update to Windows 11.

    Not only did i have to get them re-auth'ed but I had a hell of a time DOING that as the R2R fixes would not work correctly etc..

    That said, if you are having probs. with Spectrasonics, or ANY other software going 'unlicensed' periodically...then please try shutting down Windows updates either temporarily or permanently.

    You can employ multiple diff. methods and all of these are covered here.

    Hope this helps ... someone.

    Cheers! :wink:


     
    Last edited: Jul 26, 2026 at 7:29 PM
  2.  
  3. quadcore64

    quadcore64 Audiosexual

    Joined:
    Jun 13, 2011
    Messages:
    2,025
    Likes Received:
    1,120
    This issue is affecting other software as well. Including 'Legit' software.

    Noticed that Windows had reversed ownership to system.

    Had to use Take Ownership & also remove read-only from all Spectrasonics & Omnisphere folders.

    Once done, I did the following:

    - In the R2R instructions, you are directed to run C:\Program Files\Spectrasonics\Omnisphere.exe
    - click request authorization
    - select everything after the equals sign in your browser window. Example:
    =SmMY%256QnT%3dXyx38KlPUBqkTBx%3fB8
    - run the new WM_Spectrasonics.r2rwm activator
    - paste the challenge code & click generate
    - go back to the Omnisphere.exe window & click Paste
    - restart Omnisphere.exe

    Edit:
    A quick way to take ownership is the following registry entry Copy everything between the spoiler tags (including spaces), paste into a text file & save as Take_Ownershp.reg .

    Windows Registry Editor Version 5.00

    [HKEY_CLASSES_ROOT\Directory\shell\TakeOwnership]
    @="TakeOwnnership"

    [HKEY_CLASSES_ROOT\Directory\shell\TakeOwnership\Command]
    @="cmd.exe /c takeown /f \"%1\" /r /d y"

    Double-click the saved file & hit OK to allow the new entry. You should now have a right-click menu selection for Take Ownership. Time saver going forward.
     
    Last edited: Jul 26, 2026 at 10:50 PM
  4. saccamano

    saccamano Audiosexual

    Joined:
    Mar 26, 2023
    Messages:
    2,400
    Likes Received:
    1,014
    Location:
    CBGB omfug
    This is a widely known fact. Even for those who are not running an internet connected production box. Please let this be known now - no one "needs" windows autonomous updates!! When you do a build all you need to do is DOWNLOAD a single cumulative update from the catalog and apply it manually. Then run a PS script to completely disable the entire win update infra and be done with it. It is NOT needed and will most likely fuck more shit up than it would ever fix along with transfer of telemetry back to the mothership, along with un-doing every single privacy hole you have plugged up until then... Keep in mind that if you're running offline KMS activation (IMO, the only way to fly) any cumulative package you apply dated after 11/25 (inclusive), ms disabled KMS in all subsequent cumulative packages.
     
    Last edited: Jul 27, 2026 at 12:32 AM
  5. One Reason

    One Reason Audiosexual

    Joined:
    Jun 11, 2011
    Messages:
    2,780
    Likes Received:
    801
    Location:
    Where I dont want to be
    Good stuff y'all., thankya.
     
Loading...
Loading...