Are Windows XPS updates breaking stuff and violating privacy through Reactor?

lilpil
lilpil Member Posts: 9 Newcomer
in Reaktor

One XPS Win update broke touchscreen while using Reactor seemed weird timing but the last Update came while playing Reactor again. I don't play all time but Sunday night is chill time. First mic came on w/out prompt. This continued w/Reactor closed, but trying to reopen would show already open?! Then PC keyboard Midi failed, then sound out put. All other AV tech on PC function normally. Just Reactor. Scope showed sound, then this failed. Uninstall/re attempts NI shows installed but path shows nothing, says "Open"; but can't open. How to flush these remnants and break lockout?

Answers

  • lilpil
    lilpil Member Posts: 9 Newcomer

    1000 unseen requests for mic over days; log says?! no mic prompts?!

  • lilpil
    lilpil Member Posts: 9 Newcomer

    It had Reactor running invisibly in background, essentially, the mic going on and off; on jitter.

    On noticing/addressing it through permissions, the app broke. NA is seeing PC ghosts and will not download fresh or uninstall or relocate fresh tools … a "bug" …

  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 12,467 mod

    I'm not sure to understand everything here. Have you reied the following? My NI Software Crashes at Startup (Windows)

    If that didn't help, please try to summarize the issue, include screenshots if needed.

    On noticing/addressing it through permissions, the app broke. NA is seeing PC ghosts and will not download fresh or uninstall or relocate fresh tools … a "bug" …

    I'm particularly confused about this part.

  • Studiowaves
    Studiowaves Member Posts: 634 Advisor

    Did you by chance recently update to Window11 24h2 ? They did some major changes that might be throwing things off.

  • lilpil
    lilpil Member Posts: 9 Newcomer

    To summarize: Last two forced Windows updates during Reactor use seems to have caused, first the touchscreen to fail; then the next update caused a background version to run which elicited thousands of mic requests w/out prompt. I only noted because mic was jittering on/off on the toolbar some days later. The background Reactor could not be shut off; instead, a second instance would open and crash. I went into my PC permissions and noted a new bar saying certain desktop apps may access mic; which didn't exist before. The original mic permissions were still off; as I would rarely use onboard PC mic for rec Reactor. On rescinding this new "permission", all onboard NI tools broke. NA sees remnants somewhere; despite un/reinstall; registry wipe, etc. The new tech is more expensive and less secure than ever, insidious exploits everywhere. I use a recovered Reactor to still build; but NA is stuck on those ghostly, nonexistent remnants, so … no more updates w/out a firmware re; ig :(

  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 12,467 mod
    https://community.native-instruments.com/discussion/comment/184502#Comment_184502

    I would suggest to contact our support regarding this issue, they might need to have a deeper look in your system. Maybe start with our installation/Native Access support: https://bit.ly/NI_support_NA

  • lilpil
    lilpil Member Posts: 9 Newcomer

    Yes, it is the Windows behind this. This Sunday's "Update" broke the driver for the right speaker, now. Really, it is a greedy/punishing withdrawal of "services" _ this XPS is still brand new, babied and never used; but when fired up w/out paying a minimum $130 US/mo. "warranty", this is what happens with delivery of 'maintenance' courtesy of censorious criminal oligarchs. I never had a problem w/ NI. I will replace the toxic Win firmware and run Linux off a pen drive.

  • colB
    colB Member Posts: 958 Guru
    https://community.native-instruments.com/discussion/comment/187916#Comment_187916

    If what you are spouting was true, there would be hundreds, maybe thousands of other users with the same problems. Some fairly large proportion of them would complaining here in the forum, kneejerk reacting about how NI suck, and threatening to leave or whatever…

    Where are they?

    It's much much more likely to be a combination of hardware setup and OS setting causing some sort of incompatibility.

    Just because a issue started immediately after an update doesn't mean that the update is at fault. It is just as likely that there was an existing problem with your setup that wasn't tripping the older versions up, but the new version is more sensitive to that type of problem - probably because the earlier lack of sensitivity was a security hazard.

    …and FWIW, if you can't get Windows to work smoothly, you're gonna have sooo much fun with Linux ;-)

Back To Top

Categories