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
What is your antivirus program ?
Check this list from top to bottom. Read it all very carefully. Besides antivirus programs, do you have ANY other software listed there ?
https://support.steampowered.com/kb_article.php?ref=9828-SFLZ-9289
You did not answer my other question.
Do you have Steam and games set as exceptions in Avast ?
This is just one reason why I never install Steam inside any UAC protected folders. I always install Steam in its own folder all by itself.
I will ask you again, and if you do not answer, I will have to assume that I cannot help you...
Except that you can move your Steam out of any UAC protected folders. See this...
https://support.steampowered.com/kb_article.php?ref=7418-YUBN-8129
If you could please be more specific as to what fixed this issue for you, it could help others in the community that see your thread and have a similar problem. Thanks.
when you launch the game or steam and if gives you the UAC permission page, it will have a show more tab at the bottom, click that. and it will say choose when to be notified in there in very light text. click that and slide the bar to never notify.
Better late than never but thank you for this quick fix ✌️
why we know because post is from 2016
UAC turn off in win10 is not a option, its use it to ID a user, and app need it for user identification.
This post is outdate and wrong in so many ways.
a 2016 post with win7 migrated issue into win10, i bet.