Pinned RDP Wonkyness

I originally posted this question here:
Windows 10 Insider forum question

Even though I believe that it might be a Windows 10 desktop/taskbar issue, was told in that thread by an MS Support Engineer that it's a general technet question and should be here so here goes:

I've run into some weirdness that I can't seem to figure out.  I use a lot of RDP connections so I pinned RDP to the taskbar (this was a fresh install of Windows 10, build 10041), and as I use it it creates a list of recently used connections... so far so good.  If I try to pin those connections, it replaces the machine name with the application name (mstsc.exe), and will not let me un-pin them:

Image

They don't work either, when I click on them I get:

Image

Anyone know what is going on/how to fix it?  Even just how to remove the pins so I can see the connections that I use often again?




  • Edited by mpikas Friday, April 24, 2015 8:14 PM
April 24th, 2015 8:11pm

MP

10041 (and 49) have issues.  I would first update to 10061 which came out yesterday and is much more stable.

Free Windows Admin Tool Kit Click here and download it now
April 24th, 2015 8:21pm

I'm not sure what stability really has to do with it, since it's not like it's crashing or something... but it doesn't matter.  I updated to 10061 and it's still identical, nothing changed, still can't unpin it.

April 25th, 2015 9:43am

Hi,

I tested in 10061 and seems issue remains in this build. Please submit a feedback via Windows Feedback App to our development team and hope this issue can be fixed via future updates.

Thanks for your support.

Regards

Free Windows Admin Tool Kit Click here and download it now
April 27th, 2015 8:19am

Well, at least you confirmed that it's not just me.

Even if it is a problem, is there some way of removing them?
April 29th, 2015 5:59pm

Even if it is a problem, is there some way of removing them?

FWIW I would try running ProcMon to see if it would expose whatever the implementation is for that, e.g. whether registry or file access.  That would refine your symptom description and help give you more information to help you devise a feasible workaround.

Alternatively since ProcMon seems to be less useful than it once was, whether due to optimization or evasion, you may have to try using some other traces.  E.g. this command pipeline gives a list

netsh  trace  show  providers  |  sort  /+40  |  clip

Then Paste that into a Notepad window and save it for future finds.   ; )

For example

C:\Users\VMUSER\documents>findstr /i "remo rdp" "Netsh Trace Providers Sorted.txt"
{20C46239-D059-4214-A11E-7D6769CBE020}  Microsoft-Windows-Remote-FileSystem-Log
{51734B23-5B7E-4892-BA8E-45BC110B735C}  Microsoft-Windows-Remote-FileSystem-Monitor
{1B8B402D-78DC-46FB-BF71-46E64AEDF165}  Microsoft-Windows-RemoteApp and Desktop Connections
{5B0A651A-8807-45CC-9656-7579815B6AF0}  Microsoft-Windows-RemoteAssistance
{1139C61B-B549-4251-8ED3-27250A1EDEC8}  Microsoft-Windows-RemoteDesktopServices-RdpCoreTS
{3903D5B9-988D-4C31-9CCD-4022F96703F0}  Microsoft-Windows-RemoteDesktopServices-RemoteFX-Synth3dvsc
{741C6BE3-F74B-4E4D-88E7-5CE3A35FAEB3}  Microsoft-Windows-RemoteDesktopServices-RemoteFX-VM-User-Mode-Transport
{F1394DE0-32C7-4A76-A6DE-B245E48F4615}  Microsoft-Windows-RemoteDesktopServices-SessionServices
{1A870028-F191-4699-8473-6FCD299EAB77}  Microsoft-Windows-Remotefs-Rdbss
{127E0DC5-E13B-4935-985E-78FD508B1D80}  Microsoft-Windows-TerminalServices-RdpSoundDriver
{C76BAA63-AE81-421C-B425-340B4B24157F}  Microsoft-Windows-TerminalServices-RemoteConnectionManager
{54FFD262-99FE-4576-96E7-1ADB500370DC}  Microsoft-Windows-Wordpad
{D4199645-41BE-4FD5-9D71-A612C508FDC6}  RdpCore Api Trace
{D4199645-41BE-4FD5-9D71-A612C508FDC7}  RDPEncComTrace
{5A966D1C-6B48-11DA-8BDE-F66BAD1E3F3A}  TS Rdp Sound End Point Trace
{04C6E16D-B99F-4A3A-9B3E-B8325BBC781E}  Windows Remote Management Trace

Good luck

Free Windows Admin Tool Kit Click here and download it now
April 30th, 2015 1:07am

This is fixed in build 10074, but you have to clear out the jump list for it to work.   I use the instructions here http://www.eightforums.com/tutorials/9611-jump-lists-reset-clear-windows-8-a.html   It's not a Microsoft site, but it covers it pretty well and it definitely works for Windows 10 -- 10074.    
April 30th, 2015 5:56pm

huh, Bob, I'm quite honestly stumped...

I went to the page that you linked and tried right clicking and removing them like they showed and it didn't work, no remove option, only unpin and if you chose it it just highlighted it yellow and it was still there when I brought up the menu again.  

I grabbed the bat file and used the locations listed in it (figuring that i'd open the directories and manually delete), and, well they didn't exist (I'm wondering if the profile has to not be in use at the time or something), but then when I ran the batch file it did work... 

I hate mysteries.  I'm betting there is an easy explanation but I don't know what it is.
Free Windows Admin Tool Kit Click here and download it now
May 2nd, 2015 11:42pm

>I went to the page that you linked and tried right clicking and removing them like they showed and it didn't work,   Yeah, I noticed that too, I should have mentioned it.  It's because the jumplist was actually corrupted.   >I grabbed the bat file and used the locations listed in it (figuring that i'd open the directories and manually delete), and, well they didn't exist (I'm wondering if the profile has to not be in use at the time or something), but then when I ran the batch file it did work...   I used the bat file.   Did you run it as administrator?  You need to do that.  

No problem deleting those when you are logged into the profile.

May 3rd, 2015 12:00am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics