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
So what is the point of having a background process it if it doesn't do anything?
It's there for when Virtual Desktop is running, that way there's no UAC prompt to give it admin rights, which is needed to capture certain things (such as UAC prompts when you launch a program that needs admin rights). He was saying it doesn't do anything when Virtual Desktop isn't running, not that it never does anything.
Prior the application installed a "Virtual Desktop Service" that was set to automatic, but could be stopped. If you set it to disabled or manual it would set itself back to "automatic" when you ran the program.
Now the service is permanently set to "Disabled" but still starts with Windows and cannot be stopped. This is despite the program being set NOT to start with Windows.
Why does this service need to be constantly running in the background? Why can it not be stopped at-will?
Please note, I'm not in any way implying this is malicious behavior, I don't believe it is. But I would much prefer the option to set it to manual and have it start only as-needed.
I am also noticing VD Always starting with windows even tho i have it set in the options not to start and i have the setting Start minimized ... i dont care if it starts but i dont want to have to close/minimize it every windows start up... This started happening after a Windows update a few days ago...
I realized after I posted that that this is a different version of VD than what's in the Quest store, so this may not apply - but mine sorted itself out after a reinstall. I had to manually remove it, because even uninstall didn't get rid of the service.