vMix Forums
»
General
»
General Discussion
»
Huge Problems after 24H2 Update
Rank: Member
Groups: Registered
Joined: 11/21/2024(UTC) Posts: 11  Location: Ockfen Thanks: 2 times
Was thanked: 1 time(s) in 1 post(s)
|
Hello !
Anyone else facing issues after the Microsoft 24H2 and 2025-01 Updates ? - vMix came up with a Message, that the hardware has been modified and that it needs a reactivation of vMix. Just imagine !
Had similar problem with my waves plugins as well, as after installing the updates in Windows, something changed in the way the hardware is recognized and that deactivated all of waves plugins. Funfact: These plugins can only be recovered once a year, so I am forced to turn of all Windows Updates to minimize the risk, that after the next updates, the same or similar issue will come up again...
I am working as IT support and also at my workplace, we had hundreds of computers, where 24H2 was not installing properly and had to be forced to install by a repair installation from the Windows Image... Sorry Guys, but Microsoft is more and more bullshitting and this is not acceptable ! High time for vMix to change OS plattform...
Cheers
Marco
|
 1 user thanked MRedZac for this useful post.
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 11/14/2012(UTC) Posts: 273  Location: Finland Thanks: 141 times
Was thanked: 15 time(s) in 13 post(s)
|
Originally Posted by: MRedZac  Sorry Guys, but Microsoft is more and more bullshitting and this is not acceptable ! High time for vMix to change OS plattform... +1
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 7/4/2021(UTC) Posts: 337  Thanks: 8 times
Was thanked: 51 time(s) in 42 post(s)
|
Originally Posted by: MRedZac Funfact: These plugins can only be recovered once a year, so I am forced to turn of all Windows Updates to minimize the risk, that after the next updates, the same or similar issue will come up again... Look up what the registration is tied to. Now you know how to overcome that issue moving forward, if this happens again. Originally Posted by: MRedZac High time for vMix to change OS plattform... To what? Because if you want to talk about Waves plugins, Mac users have far more issues with needing to buy the upgrade plan to make their plugins work again than Windows users do. Mac updates, even outside the very plugins that you yourself mentioned which have a reputation for breaking with Mac updates, are far more likely to break software than Windows updates are. So that's certainly not the answer to that problem. And switching to Linux or any Linux offshoots are just going to cost them marketshare, because people will just move to a competitor before they move their entire OS to Linux to keep using vMix. So what's that leave?
|
|
|
|
|
|
Rank: Member
Groups: Registered
Joined: 11/21/2024(UTC) Posts: 11 Location: Ockfen Thanks: 2 times
Was thanked: 1 time(s) in 1 post(s)
|
Originally Posted by: WaltG12 Originally Posted by: MRedZac Funfact: These plugins can only be recovered once a year, so I am forced to turn of all Windows Updates to minimize the risk, that after the next updates, the same or similar issue will come up again... Look up what the registration is tied to. Now you know how to overcome that issue moving forward, if this happens again. Originally Posted by: MRedZac High time for vMix to change OS plattform... To what? Because if you want to talk about Waves plugins, Mac users have far more issues with needing to buy the upgrade plan to make their plugins work again than Windows users do. Mac updates, even outside the very plugins that you yourself mentioned which have a reputation for breaking with Mac updates, are far more likely to break software than Windows updates are. So that's certainly not the answer to that problem. And switching to Linux or any Linux offshoots are just going to cost them marketshare, because people will just move to a competitor before they move their entire OS to Linux to keep using vMix. So what's that leave? Concerning Waves registration: It was tied to the internal network card and after the update it was tied to wifi card instead and it was not possible to revert it back to the internal lan card... Concerning OS: You are obviously not informed yet, that Microsoft is about to move Windows completely into the cloud. There will be no "offline" Windows on computers anymore the way we know it now, soon. Anyway, Microsoft is constantly losing market shares. They came from over 95% and now they barely have 65-70% left... If they go on following their plans to move Windows completely into the cloud, their shares will even drop faster... I am also not talking about to stop development for Windows, but at least it would make sense to start linux developement in parallel to be prepared for day X to come... And this day WILL come, that's a matter of fact or what you think all this Windows 365 topic is about...!?
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 12/24/2021(UTC) Posts: 588  Location: athens Thanks: 146 times
Was thanked: 79 time(s) in 75 post(s)
|
Windows 10 until the sun rises in the west! Practically, no one is forcing us to upgrade to Windows 11. My only personal hope is that vMix doesn't "abandon" us and make future versions exclusively for Windows 11 and beyond. If, in the future, Windows 13-14 improve (after all, Microsoft is known for failures like Vista, etc.), then yes, we can move forward.
|
|
|
|
|
|
Rank: Member
Groups: Registered
Joined: 6/11/2020(UTC) Posts: 15 Location: San Francisco Was thanked: 2 time(s) in 2 post(s)
|
We have Windows Updates disabled on all of our vMix servers and I would never allow Windows to do any auto updates on any of our production machines. When we do decide to updates, they are tested on one of our dev boxes, evaluated carefully to see if there is any impact on vMix and several other apps and then and only then do we manually update our servers.
Never had an issue..
|
|
|
|
|
|
Rank: Member
Groups: Registered
Joined: 3/2/2019(UTC) Posts: 20  Location: Littlehampton Thanks: 1 times
Was thanked: 2 time(s) in 2 post(s)
|
Bumping this thread as linked to our experience. Cannot believe we are the only ones. https://forums.vmix.com/...1-24H2-update#post117681DMack, you say: Quote:We have Windows Updates disabled on all of our vMix servers and I would never allow Windows to do any auto updates on any of our production machines. When we do decide to updates, they are tested on one of our dev boxes, evaluated carefully to see if there is any impact on vMix and several other apps and then and only then do we manually update our servers.
Never had an issue.. I do try to turn-off windows update in services.msc but Microsoft still manage to get their nags through to update. In our case, an unsuspecting user went forwards with the update and now we are left with a machine that cannot access the audio inputs! Unfortunately, this device is being used for streaming daily and so we are waiting for a weekend to either roll-back, re-install vMix or use the back-up machine (which is running Windows 10, ironically). Wanted to gauge the Community's views before deciding which order to tackle things in! :) Thanks to all.
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 12/24/2021(UTC) Posts: 588 Location: athens Thanks: 146 times
Was thanked: 79 time(s) in 75 post(s)
|
Originally Posted by: stevethornley Bumping this thread as linked to our experience. Cannot believe we are the only ones. https://forums.vmix.com/...1-24H2-update#post117681DMack, you say: Quote:We have Windows Updates disabled on all of our vMix servers and I would never allow Windows to do any auto updates on any of our production machines. When we do decide to updates, they are tested on one of our dev boxes, evaluated carefully to see if there is any impact on vMix and several other apps and then and only then do we manually update our servers.
Never had an issue.. I do try to turn-off windows update in services.msc but Microsoft still manage to get their nags through to update. In our case, an unsuspecting user went forwards with the update and now we are left with a machine that cannot access the audio inputs! Unfortunately, this device is being used for streaming daily and so we are waiting for a weekend to either roll-back, re-install vMix or use the back-up machine (which is running Windows 10, ironically). Wanted to gauge the Community's views before deciding which order to tackle things in! :) Thanks to all. The problem is that you use old vmix version. 24 is 4 versions back and latest 28 version is 10 times better.Vmix 27 and 28 work ok at windows 11 24H2. If you do daily streaming the 60$ that need to update are a fair amount of money and worth it Although i avoid personally windows 11 not because only vmix but in generally because i like the "if work dont change it" but i know if my pc breaks i will need new pc with windows 11 or used HW.
|
|
|
|
|
|
Rank: Advanced Member
Groups: Registered
Joined: 12/14/2018(UTC) Posts: 133  Location: Clermont-Ferrand Thanks: 30 times
Was thanked: 9 time(s) in 8 post(s)
|
Originally Posted by: stevethornley Bumping this thread as linked to our experience. Cannot believe we are the only ones. https://forums.vmix.com/...1-24H2-update#post117681DMack, you say: Quote:We have Windows Updates disabled on all of our vMix servers and I would never allow Windows to do any auto updates on any of our production machines. When we do decide to updates, they are tested on one of our dev boxes, evaluated carefully to see if there is any impact on vMix and several other apps and then and only then do we manually update our servers.
Never had an issue.. I do try to turn-off windows update in services.msc but Microsoft still manage to get their nags through to update. In our case, an unsuspecting user went forwards with the update and now we are left with a machine that cannot access the audio inputs! Unfortunately, this device is being used for streaming daily and so we are waiting for a weekend to either roll-back, re-install vMix or use the back-up machine (which is running Windows 10, ironically). Wanted to gauge the Community's views before deciding which order to tackle things in! :) Thanks to all. Indeed, even if users have had problems with this update, you might want to update your version of vMix instead of blaming Windows 11 directly...
|
|
|
|
|
|
vMix Forums
»
General
»
General Discussion
»
Huge Problems after 24H2 Update
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
Important Information:
The vMix Forums uses cookies. By continuing to browse this site, you are agreeing to our use of cookies.
More Details
Close
