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
I mentioned in my post that I tried deleting the caches in both Steam and Chrome already. Unless you are talking about some other function then the built in options to clear cache in settings > downloads and settings > web browser?
Good new folks, I fixed it with a combination of two things.
1) Goto C:\Users\Your name here\AppData\Local\Steam\htmlcache and delete the entire htmlcache folder. Do not use or rely on the option in steam settings to clear the cache.
2) Run "steam://flushconfig" in the command prompt window. This will start steam, and once you login, manually flush the downloads cache. It will tell you that it's doing this, and that you will need to login again once it's done.
This worked for me. The problem it seems, was a bad web certificate called "DST Root CA X3"
I'm not sure what caused this problem, but I suspect it may have had something to do with a failed update to GoG launcher/store earlier in the week. This is only my speculation, I have no proof. Things are working again, I'm happy. Good luck!
how did you fix the issue on the mobile app?
technocaly your post should be locked by a steam moderator. this is well known issue, and again proof outdate OS is dead, and there is nothing steam can do to keep them alive, steam is the problem for allowed it to work, you have live on borrow time, and technicaly make havok for use a outdate system.
steam cant and will not fix things that not made by steam, it will only open the door for all other things people think is a steam problem just like you do now.
as i recall that "DST Root CA X3" is a pure win7/8 issue only.
and why none will reply here, your post is from 9 Jun, 2022, this said it all, and actual has nothing to do with me, be happy someone tell you this. because noone else will.
You need to go to unoffcial fix or unoffcial patch, and here is the problem who is responsible for that.
and this is why steam has a issue with past system, KILL them lesser havok from such user that poisen every post they make, ( stop think i hate past OS win7 was best OS before win10 and so can you say to all of them before.
All steam old post before win10 shoud be read only, can actual be a issue with bad advice that get issue with newer system, because many forget even hardware is diffrent in top of this.
ps.
Dont forget that Network "DST Root CA X3" is in many places and not only a win7/8 issue but if i recall correctly other system just update it, problem is how can it even not get update before run out, thats right they was not resposible for it.
And what prevent other pc user in the world to install a old outdate win7 with the issue Nothing, and why wifi and network aient working. ( your are outdate by default windows7 freshly installed OS )
this is another reason why steam will terminate win7/8 its service. its over to many issue with past system, ( its a steam choise , has nothing to do with me or this post or OP even)
gl to any user that still use win7/8 but you need to do a effort to tell you are , or steam, will force a system check, because you can actual make havok in every steam forum. and im sure it will be made anyway, because we cant see here what system you are in a post.
OP said he is on win10, that mean its not update, truth point at itself.
I get what your saying here, you actually were not being offensive or anything like it so thank you for staying human. I just need to add I use Linux and these commands still work, yet it could be on another discussion those commands :) I believe it's just added worry here as the concern is valid to a point, we might be able to make a more professional topic covering this for future users though, hopefully ;)