Nainstalovat Steam
přihlásit se
|
jazyk
简体中文 (Zjednodušená čínština)
繁體中文 (Tradiční čínština)
日本語 (Japonština)
한국어 (Korejština)
ไทย (Thajština)
български (Bulharština)
Dansk (Dánština)
Deutsch (Němčina)
English (Angličtina)
Español-España (Evropská španělština)
Español-Latinoamérica (Latin. španělština)
Ελληνικά (Řečtina)
Français (Francouzština)
Italiano (Italština)
Bahasa Indonesia (Indonéština)
Magyar (Maďarština)
Nederlands (Nizozemština)
Norsk (Norština)
Polski (Polština)
Português (Evropská portugalština)
Português-Brasil (Brazilská portugalština)
Română (Rumunština)
Русский (Ruština)
Suomi (Finština)
Svenska (Švédština)
Türkçe (Turečtina)
Tiếng Việt (Vietnamština)
Українська (Ukrajinština)
Nahlásit problém s překladem
A good idea would be to stop using UpdatePack 7 and stop trying to endorse piracy.
Its not going to be that complicated. The main reason Steam client lost support on Windows 7 is because of qt which is to do with UI so all that fancy UI that does not mean anything is the main reason.
Well its probably more than that internally like to many reasons holding the client back to continue support for an EOL client but i know qt is one of the major reason as its dead on 7 and UI issue will be the first issues to make ppl complain that are obvious broken issue to users.
Other Devs can work around that. The very worst case someone could easily make a wrapper for steamCMD and do it that way and it will be just that but with a UI.
This will never fail because SteamCMD is a command line and you need to download the binary to updated it, which means you will always have the most up to date version with all the features. The whole point to SteamCMD is so steam can run anywhere well not anywhere but i mean on systems windows based that struggle with a UI can use it.
Many of the social features would be lost doing that but it would still see user on OS earlier than 10 being able to log into steam and download an play games.
aye this is why people running the beta under windows 7 has been opt-out and the client downloaded the stable branch.
UpdatePack7 contains updates that are explicitly labeled ONLY for Windows Server and Windows Embedded Standard 7. Normally these updates would not be possible to install inside of Windows 7 on their own. UpdatePack7 allows these updates to be installed when they otherwise would never be possible to install without UpdatePack7. The latest updates inside of UpdatePack7 are not for Windows 7, not designed for Windows 7, and are not compatible with Windows 7.
There is not 1 single update released by Microsoft explicitly for "Windows 7" since Feb 2023. There are no recent updates for Windows 7 that could possibly be installed by UpdatePack7. It can't possibly update Windows 7 as there is no update for Windows 7 that exists. Literally does not exist at all.
UpdatePack7 claiming to have updates for Windows 7 is not actually updating anything. As I said before: It takes updates for Windows Server and Windows Embedded Standard 7 then MODIFIES the installer package to disable the operating system check and install those updates inside of Windows 7.
I write only true and factual information. None of my thoughts. None of my opinions. No conjecture. Only facts. It is a fact: UpdatePack7 does not update Windows 7.
rofl
https://i.postimg.cc/265wzrrB/Capture.jpg
https://i.postimg.cc/CLwjYw7M/Capture.jpg
https://i.postimg.cc/28Yx6QkD/Capture.jpg
2024-10 Security Only Quality Update for Windows Embedded Standard 7 for x64-based Systems (KB5044321)
Nom: windows6.1-kb5044321-x64_7844dd833100025740c4a93838e9ed288d267c0d.msu
Taille: 65555945 octets : 62 MiB
SHA256: 6f8720852eef1d04d31c60747fc95a00f9dee862855177cee2655ec5f7985677
2024-10 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5044321)
Nom: windows6.1-kb5044321-x64_7844dd833100025740c4a93838e9ed288d267c0d(1).msu
Taille: 65555945 octets : 62 MiB
SHA256: 6f8720852eef1d04d31c60747fc95a00f9dee862855177cee2655ec5f7985677
both files are exactly the same files as you can see with their respectiv sha256 ,and also same name from the second screenshot despite they have been labelled for a different sku ;)
i can imagine , that you do not know what a sha256 on a file means , it's not a surprise as you just circling about a name you gladly can read correctly despite both files are the SAME EXACT FILE, and both are working for server 2008r2 and windows 7 embedded.
https://en.wikipedia.org/wiki/SHA-2
And mikeysoft did not even bother to change the download name of both of them ( screenshot 2)
I don't limp along on an outdated operating system and I've not pirated anything in 16 years.
That still does not protect users from compatibility issues though, if they ever change something on the backend regardless of the version and your outdated client does not know what that new change is or how to interrupt it, it will mean that the client stops working or becomes intermittent or xyz issue etc.
Say they change some functionality on the backend and it means only new updated clients that are past window 7 are only able to accommodate that function? yeah then it will mean all those outdated clients will stop working.
Just try to launch the steam client from 2013? which imo is the best client well you can't, what about the ones before that. Yeah exactly not possible.
I imagine that it will take a long while before that point happens. the 2019 XP client still can boot and perform very basic functions so the current retail Sep 2024 build for 7/8.1 will probably work for years to come and by the time it stops. I assume that Win7 will be obsolete for absolutely everything anyway