Menu
The Windows 10 Remote Desktop Connection app allows you to connect to other computers or devices that are connected to your local network or that are on the Internet and have a public IP address. For example, you can use the Remote Desktop Connection app to connect to a colleague’s computer from your desk or to your work computer when you’re using some other computer or device.
Connect remotely to another computer on the network
Here’s how to use Remote Desktop Connection to connect remotely to another device:
If Remote Desktop Connection says that it can’t connect to the remote computer, check whether the remote computer is turned off, whether it isn’t available on the network, or whether remote connections are disabled on it.
Allow remote access to your Windows 10 computer
By default, Windows 10 doesn’t allow remote access to your computer or device. If you need this kind of access, you must manually enable it. Here’s how:
I've noticed that Office 365 (version 16.0.7167.2060) running on a remote computer is very slow when I connect from a PC running Remote Desktop (version 10.0.14393.187) and Windows 10 (Pro version 1607).
The PC I'm connecting to is running Windows 7 Enterprise SP1. Office 365 applications take 3-6 seconds to refresh. All other applications refresh in less than a second. Office 2010 applications refresh fine.
I can connect to the same computer from a Mac with Remote Desktop and performance is fine. I can connect to the same machine from a PC running Windows 7 and the performance is fine. I've used the Windows store version of Remote Desktop and I have the same problem.
I've tried connecting from a different PC with Windows 10 and Remote Desktop and I have the same problem. Has anyone else experienced this issue?
user345866
Dwayne DriskillDwayne Driskill
1 Answer
Try changing the Display Setting in Remote Desktop Connection to a lower setting than Highest (32bit). I changed mine to True Colour 24bit and performance improved ten fold.
Before I did that, I found Word Macros could take over 1 minute to run. It was also quicker to type information instead of Copy/Paste from Excel.
Now, yes it works again!!!!
user693234user693234
Not the answer you're looking for? Browse other questions tagged windows-10remote-desktopoffice365 or ask your own question.
RECOMMENDED: Click here to fix Windows errors and improve PC performance
The desktop context menu or popularly known as desktop right-click menu which appears when you perform a right-click on the empty area of Windows 10 desktop is useful to quickly access Settings and display settings, show/hide desktop icons, sort desktop items, and create New folder on desktop.
Ever since the release of Windows 10, which happened about ten months ago, several users have been complaining about the slow desktop context menu. According to users who have been experiencing this issue, when you perform a right-click on the empty area of the desktop, the context menu doesn’t appear instantly. The context slowly appears after about 4 seconds.
If you’re also experiencing the slow desktop right-click menu issue in Windows 10, you will be happy to know that the problem can be fixed in a few minutes. In most cases, the desktop context menu takes longer than usual time to appear because of the integrated third-party items like Intel graphics card properties and NIVIDIA Control Panel.
Fix to slow desktop context menu in Windows 10
Follow the given below directions to remove third-party entries from the desktop context menu and fix the slow desktop right-click issue in Windows 10.
Method 1 of 2
Step 1: In the Start menu or taskbar search box, type Regedit and then press Enter key to open Registry Editor. If you see the User Account Control dialog, please press Yes button.
Step 2: Once the Registry Editor is launched, navigate to the following key:
HKEY_CLASSES_ROOTDirectoryBackground shellexContextMenuHandlers
Step 3: Under, ContextMenuHandlers, several folders will appear.
Step 4: In order to remove Intel Graphics Properties and Graphics Options entries, you need to delete igfxcui and igfxDTCM folders. To delete a folder, simply right-click on it and then click Delete. Click Yes when you see the confirmation dialog.
Likewise, if your PC has NVIDIA graphics hardware, you will see NvCplDesktopContext under ContextMenuHandlers. Simply right-click on it and then click Delete.
You may close the Registry Editor now.
Step 5: The desktop context menu should now appear instantly, without any delay. If not, restart your PC once.
Method 2 of 2
Those of you who don’t want to play the Registry can use a free utility called ShellExView to remove those entries from the desktop context menu. Here is how to download and use ShellExView on Windows 10.
Step 1: Visit this page and download the latest version of ShellExView. Note that the download link appears towards the end of the page.
Step 2: Extract the zip file, and then run the shellexview.exe file by double-clicking on it. Click Yes button when you see the User Account Control prompt.
Step 3: The tool will take a few seconds to scan your PC for context menu entries.
Step 4: Finally, look for the entry named NVIDIA CPL Context Menu Extension, right-click on it and then click Disable.
Likewise, if you have Intel graphics, under Extensions, look for two entries named TheDesktopContextMenu Class and TheDesktopContextMenu Class and disable them by right-clicking on them and then clicking Disable. You might need to restart Windows Explorer once or perform a reboot to see the change.
Our how to make the Stat menu open faster in Windows 10 guide might also be of interest to you.
Hi, my name is Kim and I herd cats.. where cats in this case are High DPI issues. I've been working to get more information out there on DPI issues, like bribing the Product Group to write some awesome technical blogs about the fun of High DPI. (Ok - didn't have to bribe) getting public KB articles and other posts published and fielding questions from various groups on the status of many of the DPI problems. DPI and RDP is one that has come up often of late and I wanted write this to help people have the best possible experience with Windows 10, high resolution monitors and remote desktop connections.
Disclaimer - I know High DPI issues can be pretty complicated and ugly. But many DPI issues can be mitigated. This article isn't meant to address the difficulties in truly fixing DPI issues in code or discuss known bugs. It is meant to offer best practices to result in optimal performance for Remote Desktop sessions using Windows 10 1607 with multiple monitors.
For reference and for examples in this blog, I'm use a Surface Book with a Surface dock connected to a Dell 34' wide 4k monitor. I also connect to several remote systems, both Hyper-V VMs and physical systems. I'll stick with Surface Dock for simplicity and familiarity, but this applies to any high resolution devices and companion hardware.
Key points
Definitions
Tools I'm using
User scenarios
One of the key considerations to avoid or mitigate DPI issues is knowing your scenarios. If you are considering buying a Surface Book, think of how you will be using the device. If it’s a sit-on-couch-binge-Netflix device/take notes in a meeting device, you won't notice any DPI issues. If you get a Surface Dock to go with it and have it docked, lid closed, most of the time, you won't see many DPI issues. But if you move around, dock/undock or connect to other systems via remote desktop protocol (RDP), or both, you'll probably run into Bad behavior.
The Bad behavior comes into play for two reasons. Hardware configuration(monitor) changes or the difference in resolution between the Surface and connected monitors is large. The latter can be addressed by using a monitor that matches or comes close to the resolution of the device. For example, my Surface Book does 3000x2000 and my external monitor does 3440x1440. When I connect to the dock, most applications look fine and will move between the monitors without noticeable burps. To combat the first issue, hardware changes, it is always best to logoff off, connect the dock, then logon and configure the displays as you want to use them. Key: You can return to this baseline at any time by logging off, docking, and logging on.
This is key. Winlogon starts when a user logs on. At that time, the existing hardware configuration is noted and DPI for that session is set. When applications are launched they use this information. When the hardware configuration changes mid-session, DPI is revised, but many applications are (currently) not aware enough to adjust. This is admittedly over-simplifying how it works, but the easiest way to think about it is that DPI is tied to the logon session. Key: If monitors change then create a new windows session = best experience.
Let's say you get a brand new Surface Book and Dock and 4k external monitor to connected to the dock - there's still some housekeeping to do (after you take time to enjoy the unboxing and new device smell - brand new keyboards are awesome and will never be that clean again!) Updates! Every release of Windows 10 has had DPI improvements. It's always best to be at the latest (currently its 1607. Which stands for year 2016, month 07. 1511 was November 2015, the first version, 1507 is July 2015 etc etc. This numbering convention will continue with future releases) Cumulative updates are also important. They typically do not introduce new features but they may provide bug fixes that improve behavior. Then, finally, hardware updates. Firmware updates for the Surface Book/Pro series will come down via Windows Updates. You will also need to check for updates to the Surface Dock. Key: always make sure you're troubleshooting new issues, not something that has already been fixed.
Remote desktop adds another layer of complexity to the situation. There are two RDP tools I'll compare here. First there is the Win32 app 'Remote Desktop Connection' or MSTSC.exe. This is an older application and does not scale well itself.
The second is Remote Desktop Preview App and is available in the Windows Store. There is both a normal and preview beta version. The one I'm working with here is the Preview version. Modern apps scale for free so this RDP client will always present itself as the right size.
Best RDP results with single monitors
Single monitor RDP scenarios are mostly unexciting when it comes to DPI issues so I'll keep it short.
Using MSTSC from a Surface Book to a remote system is not too problematic. The MSTSC client itself will behave on a single monitor. The behavior of the remote system will vary depending on the resolution of that system. You can control that in MSTSC settings under Display.
The same is true for the Remote Desktop Preview. Connections will be fine with little to no DPI issues. You can also control the display options for each session.
The only DPI issue in single monitor connections is more of an after-effect of an RDP session. Let's say you're working from home on the Surface Book and you RDP to your computer in the office. Everything looks great. When you're done you disconnect the RDP session instead of logging off the session.
The next day you go into the office and logon to that computer directly. The session is still active from yesterday, still thinking it is displaying to a 3000x2000 monitor. The display will be Bad especially if the monitor is much lower resolution. Logging off/on will fix it. Again, this is because the hardware configuration for that Windows session changed and cycling a logon will force the DPI to reset.
Best RDP results with multiple monitors
It gets a bit trickier when you have multiple monitors setup on your local system and use RDP.
To start:
External Monitor
3. Use Microsoft Remote Desktop App Preview instead of MSTSC.exe
Once you have the above sorted out, make sure the configuration is lookin' good. This goes back to the Key Points above:
Next, fire up the connection to the remote machine. When you make that connection, remember you might be connecting to an existing session. Before making any judgements or adjustments to the display settings in the Remote Desktop app make sure to log off the remote session (not disconnect) and log back on. Once that is done both the local and remote sessions will be optimized for your current hardware configuration.
At this point, if the remote session view isn't quite your jam, make adjustments to the display settings options. Make sure to log off the remote session each time until it looks just right.
I typically match up the Windows Start button icons and taskbar items to make sure I'm close to good. You can see the MSTSC frame does not scale well, but the remote desktop can be adjusted to display very close to the local desktop.
Random Tidbits
Remote Desktop Preview App. This app is in beta and while some think that means buggy, it also means there is active worked being done to it. Since it's an app in the Store, it will update automagically.
And since it’s a modern app you can move it from monitor to monitor and it will adjust and scale on the fly.
Sliding a modern app from the 34' to the Surface Book, you will see there is a critical mass point where the app tips over to use the display settings on the Book. Top of the screen is my external monitor, bottom is the Surface Book. Captured with SnagIt
During the move: Bridging the app between 2 screens may be messy depending on which screen it is using for display settings. Here's a shot of the Remote Desktop Preview moving to the larger screen. The App still is using the Surface Book's settings, as you can see the Start Button and the Remote Desktop frame are right-sized, while the taskbar on the larger screen seems tiny. One the App is completely on the larger screen it will then adjust to look great there.
You can also resize the window as needed. Note: I have seen the remote session screen get stuck while resizing. This is not a feature, but part of the wonderful Beta-ness.
Larger Remote session
Simply Slideshow features 'Ken Burns' (Pan & Zoom) effects to transition pictures during your slideshow. Users can add folders or files to either play the slideshow in sequence or in random order and start the slideshow immediately without delay even with tens of thousands of pictures. In addition, Simply Slideshow offers one feature that no other software have done before-Wallpaper Slideshow. As long as you have a windows based PC connected to it. Shuffle slideshow windows 10.
The app saves desktop connections (MSTSC does this too, but I like the options in the App better) This means you can create multiple connections to the same remote machine. Each connection can be setup to have unique display (and more) settings. For example: I'm working from hotel, no extra monitors or dock and I connect remotely to my office. I can setup that RDP connection and save it as Computer-Solo and I set the display settings to 'Choose for me'. But when I work from home I have multiple monitors, a better connection and I work mainly on my external monitor. I save this connection as Computer-Multimon.
Summary
I love long blogs posts as much as I love DPI issues. (sorry!) But devil is in the details when it comes to conquering Bad behavior. I can't stress some items enough. Various hardware/software configurations can make it difficult to clearly identify exactly what specific pains people are feeling. I've reviewed a majority of DPI support cases that have come in on Windows 10 since launch and know it's hard to address all the Bad behavior.
But every Windows 10 release is a step forward. Skype for Business and Office 2016 updates have be released and Modern/UWP apps scale for free.
Windows 10 Remote Desktop Slow Refresh
DPI reference links:
Windows 10 Remote Desktop Client Slow
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |