umbral thorn
As the title says, after updating the driver, it takes several minutes for the driver to start without manually starting it from Windows Services. I'm wondering whether this behavior is intentional or not.
The default service startup type is set to "Automatic (Delayed)".
I have attached two screenshots showing what it looks like when DSX starts.
Virtual Driver takes too long to launch automatically
gaunt cargo
Hmm thanks, I will take this into account before showing any warnings/errors. Driver should continue to work without issues
umbral thorn
Sure thing, thanks (the driver is working without issues)
flat root
isn't the service configured to start with windows?
spark prism
The service is perfectly fine
There's no need to treat these diagnostics as a blocking action on app startup
So this is self inflicted damage 😉
flat root
ok i mean a yellow warning saying some things might not work can be concerning for ppl
gaunt cargo
There’s no block, just warning. But maybe it is a bit extreme with the health check
spark prism
ok i mean a yellow warning saying some things might not work can be concerning f...
I agree, hence my remark it's overkill to even be there this early
It is normal on Windows for stuff to start concurrently and with different delays for decades
gaunt cargo
True, I’ll just focus on driver installed or not, updates, and license check to see if expired to auto renew.
spark prism
Why not just run that stuff 30 seconds after app boot, problem solved
gaunt cargo
Good idea 👍🏼
flat root
dw about it
spark prism
That's not what that service is for
flat root
the driver does the heavy lifting
spark prism
It's completely unrelated to emulation
