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
I know that in Windows 10 you can prevent this popup from appearing OR you make it less secure. I believe what this article says about Windows 10 still applies to Windows 11.
https://www.cnet.com/tech/computing/how-to-run-everything-in-administrator-mode-and-why-you-shouldnt-do-it/
I strongly recommend trying to see if the "do not dim" option works before disabling it entirely. Ideally you would leave this on the default setting. The Windows User Account Control feature is really handy when launching games that want to install DRM. It's sort of like a bouncer double checking with you before allowing a program to do some handiwork on your house.
I suggest asking around on other forums geared towards solving OS-specific problems. The official Microsoft help forums are sometimes useless or locked behind a login that requires a phone number, but aren't a bad place to seek help. I'd also recommend the forums on Tom's Hardware as the people there are high quality. Make sure to give your computer specs, Windows 11 edition & update version, and a good description of the problem.
https://forums.tomshardware.com/
Even if you select do not dim, unless you launch Steam as Administrator you may not be even able to click on those dialogs.
If remote play is running with local user account permissions then once the desktop elevates they indeed lose the ability to send input to it. The APIs that can be used in Windows to forward key presses can only forward to processes that you have equal access to.
Makes sense, no? Wouldn't want arbitrary programs being able to inject keystrokes into a root shell, now would we?
The solution to this would be to have Steam's remote play go through an equally high privileged process, at which point the ability to inject key strokes would be available again.
Except, that is of course a huge security vulnerability and exploit just waiting to happen. (And after the last two they had, I'd sure hope Valve have learned their lesson in playing it steady and safe.)
Now granted yes you don't blindly want to just give any software high level permission access, but in some cases you do depending what the app in question, and why want to give it that permission, and not like we can't config things to restrict permissions to doing things such as launching CMD, or such, but again just depends what, why, and how with app in question.
So in hindsight it was pretty obvious that running stuff as admin would solve this, it worked, but still kinda weird. I dont have this problem in windows 10 or linux. So is it just that windows 11 is more heavyhanded than windows 10 when it comes to security?
I'll have to aways remember to run programs as admin unless i want to freeze my inputs, which could be catastrophic when i need to work remotelly on my computer since i would need to travel for up to an hour just to allow my remote app to work then back again. I'm seriously considering going back to windows 10 just for that. Most of the time i'll be next to the computer so ill just need to take up to 2 cats out of my lap which is also a bummer.
Now that i think about it, it kinda made my pc less safe since i have to give apps all of the privileges in order to solve this annoyance. Oh well. Although you could argue that if the app control your inputs it already has access to everything.
For now my problem is mostly solved, but thanks for the tip, tomshardware was very helpful to me in many occasions in the past.
https://www.youtube.com/watch?v=e3qRQOCWp-Q
Video just explaining incase you thought of this at some point, and better to explain to you ahead of time so know not recommended to use.
UAC turn off just basically bypass pop up allowing you to do things you wanted without being asked everytime, but apps will not automatically get admin level it get permissions to do things want it instead of needing to ask for it, but if it need higher level then yes admin needed, which if have UAC off, and set app to have admin on launch, then it just run as admin with no pop up just like you said.
Initially the popup for UAC didn't show because such popups are painted on a secure desktop. A second desktop projected on top of the original one. By default nothing running in the original one can see or interact with the secure one. This is a security measure that is aimed at trying to prevent malware from eavesdropping the UAC prompt for your credentials. But it means that legit applications like Steam and its remote play can't do that either.
When you 'disabled' UAC it doesn't actually disable anything. It just meant the process won't need UAC to prompt for permission to elevate. Rather, when requested it will just do so.
But when it does, the process elevates to the session 0 security level and any program running under the normal session 1 user mode security level will no longer be able to send keystrokes to the process running in session 0 or communicate with it using various other inter-process communication methods.
This is why your inputs 'froze' when you had only 'disabled' UAC. Basically, the session 1 process implementing Steam remote play was just stopped cold from sending input to the elevated process now running in session 0 context by the OS's security boundaries.
By also running Steam and all its associated processes elevated to administrator, they run within the same security context again and input can be piped through.