Sunday, 21 June 2015

Removing Word jump links in Windows 8.1

I had a problem recently where I could not remove a document from the list of documents pinned to the Word app icon on my taskbar in Windows 8.1.  I hunted around the web and found various solutions which were either inaccurate or went too far.  This is my solution based on my own experimentation but as usual, YMMV.  (Note that it is preferable to try using the right-click and "unpin from this list" option before doing this but that did not work for me). 

First, navigate to %Appdata%\Microsoft\Windows\Recent\AutomaticDestinations.  One point some solutions do not make clear is that you pretty much have to paste that text into your File Explorer address bar or into the run dialog box (Win key + R).  I could not navigate using point and click on the directory tree because the "Automatic Destinations" folder did not show up, even though I have File Explorer set to show system and hidden folders. 

Secondly, find the file that holds the information for the app that you wish to clean up.  Some solutions just say to delete all files in the AutomaticDestinations folder.  That will work but it will get rid of your pinned items for all programs, which is excessive if you are only having a problem with one program, say Word, like me.  For 32-bit Word 2010, the file is called a7bd71699cd38d1c.automaticDestinations-ms.  Note that the file is different for each app and indeed it seems, each version of each app. You can find a handy list of the IDs from which the file name can be constructed here

Thirdly, delete that file or perhaps more cautiously, move it to another location.  This should leave you with a Word icon on the taskbar with no recent files and no pinned items.  If you realise moving it was a mistake, I expect you can copy the file back, but I have not tested that.

One of the solutions I found suggested that it was possible to edit the automaticDestinations-ms files to fix errors but I could not work out how to do that.  While you can read the files in a text editor, they have a swag of unreadable characters so I would not be confident about that.

No comments:

Post a Comment