How Do I Stop Forced Updates To The Beta Version?

[Iluviel]

So again I will say, I was NOT on beta but it forced this update. The question still remains. How to we go back? I do not want Beta and was not clicked for Beta.

If you really want to do this, you can risk re-installing the current stable version of Vortex over the Beta version you currently have installed. That may result in complications with your environment though.

 

Opting into Beta does help us with developing the application and is appreciated. If you're experiencing issues with the Beta build, fixes will be along shortly.

[NineTails1mod]

 

So again I will say, I was NOT on beta but it forced this update. The question still remains. How to we go back? I do not want Beta and was not clicked for Beta.

If you really want to do this, you can risk re-installing the current stable version of Vortex over the Beta version you currently have installed. That may result in complications with your environment though.

 

Opting into Beta does help us with developing the application and is appreciated. If you're experiencing issues with the Beta build, fixes will be along shortly.

 

Thank you for your response. I will try that right away.

[Guest deleted34304850]

So again I will say, I was NOT on beta but it forced this update. The question still remains. How to we go back? I do not want Beta and was not clicked for Beta.

i have a laptop that i use for messing about with stuff. on that laptop i've got vortex set to beta.

i have another laptop that i use for playing games. on that laptop i have vortex set to stable.

 

i only got notified about a software update on the laptop where i'm in the beta channel. i pulled it down, installed it - knowing full well its beta because it told me so when i pulled it down.

i installed it, ran through a few verifications i've developed over the years, found an issue and reported it - you can see it on github, here; https://forums.nexusmods.com/index.php?/topic/7332636-how-to-post-request-support-for-vortex/

 

on my other laptop the stable vortex hasn't shown me any updates at all.

 

i wonder what makes your stable track vortex the same as my beta track vortex? i hope you sent in diagnostics so this can be tracked down. i think that would be extremely helpful.

[coldsun1187]

 

So again I will say, I was NOT on beta but it forced this update. The question still remains. How to we go back? I do not want Beta and was not clicked for Beta.

i have a laptop that i use for messing about with stuff. on that laptop i've got vortex set to beta.

i have another laptop that i use for playing games. on that laptop i have vortex set to stable.

 

i only got notified about a software update on the laptop where i'm in the beta channel. i pulled it down, installed it - knowing full well its beta because it told me so when i pulled it down.

i installed it, ran through a few verifications i've developed over the years, found an issue and reported it - you can see it on github, here; https://forums.nexusmods.com/index.php?/topic/7332636-how-to-post-request-support-for-vortex/

 

on my other laptop the stable vortex hasn't shown me any updates at all.

 

i wonder what makes your stable track vortex the same as my beta track vortex? i hope you sent in diagnostics so this can be tracked down. i think that would be extremely helpful.

 

My experience yesterday was this:

 

Vortex updated automatically - no surprise there - I had it set that way I think and its been doing that for some time. The surprise was being updated to BETA in the Vortex tab. I don't remember selecting that option, so the only thing I can think is I downloaded a beta and installed it that way or I selected it and didn't realize I did it (both user error on my part). That said, I also believe it is very possible it updated me to beta and I was in the stable track and if so, that should get looked into. Folks like NineTails here, who aren't as computer experienced as some of us, could break their install completely. For me, just installing the latest stable fixed things despite the warnings and error messages. For now. I'm going to reinstall everything in the future anyhow, so its no big deal. I mentioned it earlier, but at least two other people in my Discord reported this problem. Let's not make assumptions they are up to no good and assume that they are just inexperienced with computers and just need some help. Thanks and have a good day.

[showler]

Not that long ago a problem with GitHub resulted in a lot of people getting unwanted Beta updates. So, the "sucks to be you, it's your own fault" responses are a little lacking.

 

If you do end up with an unwanted and broken Beta, is "wait until we fix the Beta or push through a new stable version" really the only advice that is given?

[Guest deleted34304850]

Not that long ago a problem with GitHub resulted in a lot of people getting unwanted Beta updates. So, the "sucks to be you, it's your own fault" responses are a little lacking.

 

If you do end up with an unwanted and broken Beta, is "wait until we fix the Beta or push through a new stable version" really the only advice that is given?

that issue is NOTHING to do with this, so, nice conflation but 100% irrelevant. What next, are you going to cite LOG4J or SPRING? I mean, the world's your lobster here Rodney, you can cite any error you like and try to conflate them should you wish.

 

beta software is labelled beta for a reason - it needs to be tested and issues reported. then, once those issues are reported, diagnosed and fixed, an update is pushed out - so YES, that's the only advice given.

again - for the hard of reading and comprehension - if you don't want BETA softare, don't set yourself up and choose it (which by the way is 100% on the user not the program).

[showler]

The people that had the BETA pushed on them by the GitHub error DID NOT CHOOSE TO BE ON THE BETA. It was the result of an error outside of their control and their should be a way for them to fix that problem once it happens.

[Tannin42]

The github issue was outside our control as well. Users could have changed the update channel in the time since then, we, on our end could do nothing.

 

Having said that: Obviously you're supposed to be able to switch back to stable without having to reinstall, this was broken since 1.5 and curiously it never came up. It should be fixed in 1.6.1 though so now, if you toggle to stable, it should ask you to "update" to the latest stable version.

You'll get a stern warning of the risks of downgrading so I'd strongly advice you consult the forum before you do, with some upgrades it may break your setup downgrading to an older major version but we don't intentionally make it impossible.

[showler]

Thank you. I get that sometimes the Beta will have fundamental changes that make going back to Stable a bad idea, but the narrative lately has been that this is always the case. Which seemed very unlikely. You're not always going to be changing something that makes changes on that order.

 

And I was reasonably certain that you had recommended switching back to the Stable channel in the past, so not being able to do so at all seemed weird.

 

I'm glad it was just an error.

 

And, just so I'm very clear, I never thought that something like the GitHub error was something you should have any control over. But it is something that can happen and I was wondering what the advice in a case like that should be?

[Tannin42]

Well no but you should always _assume_ a downgrade by a major version isn't safe until you see it confirmed by a dev that it is about that specific downgrade (as in: just because I said a year ago that downgrading 1.4 -> 1.3 is safe does not imply in any way shape of form that 1.6 -> 1.5 is also safe).