pasterjm.blogg.se

1. #WHERE CAN I GET NVIDIA CONTROL PANEL WINDOWS 8.1 PRO INSTALL#
2. #WHERE CAN I GET NVIDIA CONTROL PANEL WINDOWS 8.1 PRO DRIVERS#

User Accounts - same settings (local admin, etc) + UAC disabled Based on the information from #1 above, I have compared the following settings between the two machines and have set them to be exactly the same: Sort of configuration issue between the two machines.Ģ. I have tested running cmd, installing apps, etc, etc and I have been able to do everything just as I should. From the problematic Win8.1 Pro machine, I have RDP'd (via mstsc /admin) to my other Win 8.1 Pro machine. In order to attempt to resolve this problem, I have done the following troubleshooting:ġ. From my Mac using Microsoft Remote Desktop app and ensuring I select the "Connect to Console session" option Another Windows 8.1 Pro running mstsc /admin and just normal mstscĢ. I have tried this from the following different setups:ġ. The user I am logging in as is a local administrator and I am connecting to (or at least I am trying to) connect to the console session of the machine.

#WHERE CAN I GET NVIDIA CONTROL PANEL WINDOWS 8.1 PRO INSTALL#

I can't install software, I can't access any form of system setting, I can't power on VMs in VMware Workstation, etc. In addition, I can't do any kind of administrative function on the machine I am RDP'ing. "The application was unable to start correctly (0xc0000142). Properties, etc I get the following error: For example if I start Command Prompt, or try and access any Control Panel item, or System Once I am logged in and can access and use the machine, no matter if I am connected to the console session of the machine or not, I can't run most applications.

#WHERE CAN I GET NVIDIA CONTROL PANEL WINDOWS 8.1 PRO DRIVERS#

Note: I have done some research on issues # 1 & 2 and I think this is because of my Nvidia drivers - as I have a Nvidia GTX660 Ti installed.Īlthough issues #1 and #2 are annoying, they are nothing like the issue I am experiencing below:ģ.

If there is no user logged in already, then when I connect I get a black screen and then never actually see the desktop, therefore I have to reboot the machine, physically log into the machine and then I am able to RDP successfully.

If the user is already logged in, when I connect I get a black screen for a few minutes before I can actually see the desktop, etcĢ.

First off, I know that most of the issues I am about to list below should technically be resolved if I connect to the console or admin session of my machine, howeverġ. I have a number of issues when connecting to my Win8 Pro (and now Win8.1 Pro) machine via RDP.