Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
(Though im assuming you tried this and im being completly useless, sorry.)
yeah no worries its nice to know an unpin and repin worked for some ppl so ill see if i can find out why
Someone knows an other fix?
Using Windows 10 Education.
its been a little bit so there may be another one that showed up again, or happened again for another reason here recently
you can always try changing from the Public Branch updates, over to the BETA updates, or if you are already on the BETA Branch for steam client updates, then yes it might actually be helpful to change back to the Public Branch of steam, although theres a couple steps to do so all the old steam programs files get cleared and will use all the Public Branch
=
i say that cuz ever since the Library Update in late 2019 (or at least thats when i noticed it, may have been happening that way for a little longer before that though), it seems as though steam doesnt use the BETA updates system how its traditionally meant to be useful
Normally in a program / service that sets up and allows users to use a BETA build, will get all new updates that are applied, but then when its time to call the changing of a certain updates functions complete, they collect the bug reports sent to them with the internal reporting function of the program itself, and also any feedback they got on certain problem topics that needed to be worked on multiple times in the updates until its good to go for majority of OS and different variations in Hardware, then they pass the newly cut and slimmed down update all at once with the problems removed
Now in steam . . . its just 2 diffenent update points i guess you could say, for example, using the BETA branch i wake up and have a bug like Taskbar Icon Stacking that, 1 week later we get another update that fixes it but also make another bug with something else that really F's stuff up and i cant use steam, if i then changed my client to the Public branch i would have the Taskbar Icon Stacking again but avoided the big bug stopping me from using steam, then after the public branch is updated and i get a F'ed up steam again i could update to the BETA branch and hopefully the next update fixed it, otherwise then your screwed until the 1st BETA branch that fixed the problem . . .
either way you slice it though at best its neglectful action on steams part, or they are intentionally attempting to mislead users into the function of the Update Branchs / Builds option
=
to the point they may as well :
1)- not even have the 2 and just have 1 and the users have to deal with it, which wouldnt surprise me cuz its their recent MO
2)- or they should relabel them to Primary Branch updates and Secondary Branch updates, cuz thats way more accurate than Public and BETA, not that 1 or the other is any more functional or not, its just 2 sets of the latest builds so that if users have specific issues with 1 cuz of their Hardware or any ridiculously high number of crazy things that could have caused the effect lol, but thats not generally / traditionally what BETA and Public meant in terms of the tech industry, or i guess more specifically Program Versions / Builds
=
and if it really is just a History kind of format, why dont they provide a page with all the update Builds and Dates for users to pick and change between? then just have it so if something big is changed functionally so any older Steam Build before a certain date / version wont work properly with newer systems, they could just remove / void all those updates before that are no good
although they wouldnt really have to cuz if it doesnt work at all when a users goes to launch Steam then they just have to get the newest update and then change back to one that doesnt have that issue, but it would be more a common courtesy
. . . . . oh thats right lol stupid me, that would be giving customers / users control over their products, and that just makes no damn logical, moral, or even just practical common sense in the tech industry ( -_-)