|
lazer_chicken posted:Are there any known problems with newer windows 10 and older directx packages? I've got a brand new out of the box laptop (Acer Nitro 5) with 1803 on it and I'm trying to play far cry 4. Every time steam tries to launch the game, it tries to install the june 2010 directx package, which silently fails, and then the game crashes with missing directx dlls. If I try to install that directx package manually, I get an error that says "an internal system error occurred" and it tells me to check DXError.log, which naturally doesn't exist, and DirectX.log, which has nothing useful in it. I've tried the package that came from steam, and both the full and web versions downloaded from microsoft, with the same error. try enabling 'direct play' under legacy components under windows features. this is under programs and features in the legacy control panel.
|
# ¿ Nov 25, 2018 19:08 |
|
|
# ¿ Apr 26, 2024 12:23 |
|
Less Fat Luke posted:This is such a minor thing but I don't get why Windows wakes up my monitor to show a lock screen every time I RDP to my computer. This has always been the case with Windows desktop versions. They only allow for a single user to be logged into one terminal interface/desktop session at a time. This means that if even you are logged into your machine and then log into the machine remotely your previous session will lock. This does not happen with Windows Server as it as a remote login features and doesn't affect the local desktop unless too many remote users log in at the same time, then people start getting locked out. I believe the default for Server is 2 users.
|
# ¿ May 24, 2020 04:17 |
|
Less Fat Luke posted:It's not the locking that I question, the system is already locked - it's waking a monitor that's completely asleep that's the weird thing. Ah, your question as not phrased very well, but I digress. You need to go into your power settings and edit the plan settings for the display. Just set the display power down/off to never.
|
# ¿ May 24, 2020 04:26 |