Broken jump lists on Windows 10












3















I have noticed that all my taskbar and start menu jump lists are broken. They are broken in a very specific way:




  • The items show up, but clicking them does nothing (clicking dismisses the jump list, but does not open the corresponding app)

  • None of the items show a context menu when right-clicked (an empty gray box appears, as if an empty context menu appeared)

  • Jump lists and the context menus work in safe mode


My problem is very similar (if not identical) to the one described in Windows 10 Taskbar JumpList Issue, Not working and in Taskbar > File Explorer > Context Menu failing me and in the related Reddit post and in the related forum post. However, I have more information on the potential cause and more attempted solutions.



There are also two related posts on Microsoft Answers: related post on Microsoft Answers and the other related post, but none of the solutions worked for me (or for the original posters).



I noticed this in Anniversary Update, after updating Visual Studio. Then, I updated to April Update, which fixed the issue. Now, I updated Visual Studio (from 15.6 to 15.7) and it is broken again. The jump lists are broken on both the taskbar and start menu, and they are broken for all apps (both desktop and store).



Things I tried:




  • Deleting all files from the AutomaticDestinations directory

  • Deleting some files from the AutomaticDestinations directory

  • Resetting jump lists from settings

  • Reinstalling all Store apps with a PowerShell script

  • Running sfc /scannow

  • Running dism with restore health option

  • Pinning items

  • Restarting the computer

  • Restarting in safe mode and then restarting again

  • Disabling Internet Explorer

  • Using the Start Menu troubleshooter: It finds corruptions, but does not apply a fix

  • Copying TileDataLayer folder from different computers and then repairing

  • Creating a new user account (this also does not work)

  • Repairing Visual Studio (it just made Visual Studio slower)

  • Restoring the original AppData folder location and creating a junction point to it from the other partition

  • Removing all junction points related to Visual Studio

  • Completely removing all versions of Visual Studio and fresh installing Visual Studio 2017

  • Installing April Update

  • Installing October Update

  • Using the ShellExView to disable all shell extensions with Context Menu flag and all shell extensions whose File Created time and CLSID Modified Time was after the problems started occurring

  • Running the recommended script Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml"} which helps fix similar problems

  • Posting an issue on the Visual Studio feedback site and through the Feedback Hub application and waiting for a fix

  • Removing all CD/DVD mounting software

  • Turning jump lists on and off in the Settings

  • Setting the JumpListItems_Maximum in the registry

  • Using msconfig to test different startup configurations (disabling all non-Microsoft services – jump lists do not work, diagnostic startup – jump lists do not work; safe-mode – jump lists work)

  • Disabling OneDrive (both in startup and from Group Policy) – interestingly, the items that are opened from OneDrive do work; but all other items do not (both clicking and the context-menu).

  • Removing all Anti-Virus software


I have some junction points on my C: drive (all in Program Files and ProgramData).



It also seems that Cortana shortcut button (WinKey+C) gets broken whenever jump lists are broken (which is usually within a few days after repair installing Windows 10).



Can anyone provide any clues or suggestions?



Edit 1 (After restoring the default AppData folder)



A peculiar thing happens when accessing the Recent Items folder: when accessed by navigating directly to it in explorer, it does not contain the CustomDestinations and AutomaticDestinations folders, but when accessed by entering the same directory into Run the folders are visible along with many items that do not appear in jump lists.



Edit 2 (After repairing Windows installation)



Even though reupdating system to April Update resolved the problem, the question remains, since the actual cause of the problem is unidentified and I expect it to happen again after another Visual Studio update.



Edit 3 (After a few days)



After about two days of working properly after doing the repair install, my jump lists are not working again. All the history items are shown, but they are again unclickable and the context-menus are empty. Obviously, doing a repair install every few days is not an option. During the few days that the jump lists worked properly, I did not install anything on my system.



Edit 4 (After removing Visual Studio and removing junction points)



After opening Visual Studio 2017 and running a UWP (Microsoft Store) app with a debugger attached, my jump lists were destroyed again.



I decided to remove both Visual Studio 2015 and Visual Studio 2017 and reinstall Visual Studio 2017, remove all junction points I had (I had some junction points for Visual Studio installation), reinstall Visual Studio 2017 and repair install Windows. Removing Visual Studio installations and the junction points did not fix the issue. Repair installing did, as noted in the answer. However, setting up a scheduled task to reinstall Windows ever few days is really not a solution.



Edit 5 (After updating Visual Studio to 15.7.3)



The jump lists are broken again. They have been working for almost a few weeks. After Visual Studio update the jump lists show the same broken behavior.



Edit 6 (After updating Windows 10 to October 2018 Update)



Fixed for five days and then broken again. Possibly related to Visual Studio again. They seem to break when a UWP application is deployed.



Edit 7 (After meddling with startup configuration)



After trying to disable shell extensions, startup items and services, by various means (including msconfig, ShellExView, the Task Manager, the Registry Editor and the Services application), I have concluded that the only state in which the Jump Lists work is safe mode.



Edit 8 (After the insightful answer by Zenithies)



I have realized that I have many 10000, 10001 and 10016 errors in the Event Log. The 10000 and 10001 errors occur after attempting to click on a jump list item. Below are the errors.




Unable to start a DCOM Server: {C82192EE-6CB5-4BC0-9EF0-FB818773790A}.



Unable to start a DCOM Server: {9AA46009-3CE0-458A-A354-715610A075E6} as Unavailable/Unavailable.



The application-specific permission
settings do not grant Local Activation permission for the COM Server application with CLSID {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} and APPID {15C20B67-12E7-4BB6-92BB-7AFF07997402}




After going through the registry, I identified one of these to be the RuntimeBroker component. I proceeded to see the corresponding component service and noticed I had duplicate entries for rundll32.exe and RuntimeBroker components similar to the Runtime DCOM Server appears twice post. When trying to modify permissions I get the following error.




One or more of the permission entries attached to Registry Value has an unrecognized type and can not be displayed.




The jump list issues can be circumvented by manually calling the jump list component. However, the permission issue still exists and the cause is probably one of the Windows updates, considering that the Runtime Broker component service is duplicated and has a different ID.






windows windows-10 taskbar start-menu jumplist







share|improve this question

























  • You will need to remove Visual Studio and reinstall it in order to fix this problem. Worth pointing out this honestly sounds like an issue with your configuration, specifically, the junction points you have configured.

    – Ramhound
    May 9 '18 at 22:14











  • @Ramhound Are you sure this is a solution? Do you know, from experience, that it is indeed the issue? I really don't want to reinstall Visual Studio if I don't have to.

    – Igor Ševo
    May 10 '18 at 17:01











  • If I was not fairly confident, about the reason this problem even happens, I wouldn't have suggested it that solution. However, I don't believe in submitting single sentences as an answer, to any question especially to a problem that is as nuanced as this one.

    – Ramhound
    May 10 '18 at 17:16













  • I will give it a try. Thanks.

    – Igor Ševo
    May 11 '18 at 21:55











  • Repairing did not work.

    – Igor Ševo
    May 13 '18 at 15:41
















3















I have noticed that all my taskbar and start menu jump lists are broken. They are broken in a very specific way:




  • The items show up, but clicking them does nothing (clicking dismisses the jump list, but does not open the corresponding app)

  • None of the items show a context menu when right-clicked (an empty gray box appears, as if an empty context menu appeared)

  • Jump lists and the context menus work in safe mode


My problem is very similar (if not identical) to the one described in Windows 10 Taskbar JumpList Issue, Not working and in Taskbar > File Explorer > Context Menu failing me and in the related Reddit post and in the related forum post. However, I have more information on the potential cause and more attempted solutions.



There are also two related posts on Microsoft Answers: related post on Microsoft Answers and the other related post, but none of the solutions worked for me (or for the original posters).



I noticed this in Anniversary Update, after updating Visual Studio. Then, I updated to April Update, which fixed the issue. Now, I updated Visual Studio (from 15.6 to 15.7) and it is broken again. The jump lists are broken on both the taskbar and start menu, and they are broken for all apps (both desktop and store).



Things I tried:




  • Deleting all files from the AutomaticDestinations directory

  • Deleting some files from the AutomaticDestinations directory

  • Resetting jump lists from settings

  • Reinstalling all Store apps with a PowerShell script

  • Running sfc /scannow

  • Running dism with restore health option

  • Pinning items

  • Restarting the computer

  • Restarting in safe mode and then restarting again

  • Disabling Internet Explorer

  • Using the Start Menu troubleshooter: It finds corruptions, but does not apply a fix

  • Copying TileDataLayer folder from different computers and then repairing

  • Creating a new user account (this also does not work)

  • Repairing Visual Studio (it just made Visual Studio slower)

  • Restoring the original AppData folder location and creating a junction point to it from the other partition

  • Removing all junction points related to Visual Studio

  • Completely removing all versions of Visual Studio and fresh installing Visual Studio 2017

  • Installing April Update

  • Installing October Update

  • Using the ShellExView to disable all shell extensions with Context Menu flag and all shell extensions whose File Created time and CLSID Modified Time was after the problems started occurring

  • Running the recommended script Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml"} which helps fix similar problems

  • Posting an issue on the Visual Studio feedback site and through the Feedback Hub application and waiting for a fix

  • Removing all CD/DVD mounting software

  • Turning jump lists on and off in the Settings

  • Setting the JumpListItems_Maximum in the registry

  • Using msconfig to test different startup configurations (disabling all non-Microsoft services – jump lists do not work, diagnostic startup – jump lists do not work; safe-mode – jump lists work)

  • Disabling OneDrive (both in startup and from Group Policy) – interestingly, the items that are opened from OneDrive do work; but all other items do not (both clicking and the context-menu).

  • Removing all Anti-Virus software


I have some junction points on my C: drive (all in Program Files and ProgramData).



It also seems that Cortana shortcut button (WinKey+C) gets broken whenever jump lists are broken (which is usually within a few days after repair installing Windows 10).



Can anyone provide any clues or suggestions?



Edit 1 (After restoring the default AppData folder)



A peculiar thing happens when accessing the Recent Items folder: when accessed by navigating directly to it in explorer, it does not contain the CustomDestinations and AutomaticDestinations folders, but when accessed by entering the same directory into Run the folders are visible along with many items that do not appear in jump lists.



Edit 2 (After repairing Windows installation)



Even though reupdating system to April Update resolved the problem, the question remains, since the actual cause of the problem is unidentified and I expect it to happen again after another Visual Studio update.



Edit 3 (After a few days)



After about two days of working properly after doing the repair install, my jump lists are not working again. All the history items are shown, but they are again unclickable and the context-menus are empty. Obviously, doing a repair install every few days is not an option. During the few days that the jump lists worked properly, I did not install anything on my system.



Edit 4 (After removing Visual Studio and removing junction points)



After opening Visual Studio 2017 and running a UWP (Microsoft Store) app with a debugger attached, my jump lists were destroyed again.



I decided to remove both Visual Studio 2015 and Visual Studio 2017 and reinstall Visual Studio 2017, remove all junction points I had (I had some junction points for Visual Studio installation), reinstall Visual Studio 2017 and repair install Windows. Removing Visual Studio installations and the junction points did not fix the issue. Repair installing did, as noted in the answer. However, setting up a scheduled task to reinstall Windows ever few days is really not a solution.



Edit 5 (After updating Visual Studio to 15.7.3)



The jump lists are broken again. They have been working for almost a few weeks. After Visual Studio update the jump lists show the same broken behavior.



Edit 6 (After updating Windows 10 to October 2018 Update)



Fixed for five days and then broken again. Possibly related to Visual Studio again. They seem to break when a UWP application is deployed.



Edit 7 (After meddling with startup configuration)



After trying to disable shell extensions, startup items and services, by various means (including msconfig, ShellExView, the Task Manager, the Registry Editor and the Services application), I have concluded that the only state in which the Jump Lists work is safe mode.



Edit 8 (After the insightful answer by Zenithies)



I have realized that I have many 10000, 10001 and 10016 errors in the Event Log. The 10000 and 10001 errors occur after attempting to click on a jump list item. Below are the errors.




Unable to start a DCOM Server: {C82192EE-6CB5-4BC0-9EF0-FB818773790A}.



Unable to start a DCOM Server: {9AA46009-3CE0-458A-A354-715610A075E6} as Unavailable/Unavailable.



The application-specific permission
settings do not grant Local Activation permission for the COM Server application with CLSID {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} and APPID {15C20B67-12E7-4BB6-92BB-7AFF07997402}




After going through the registry, I identified one of these to be the RuntimeBroker component. I proceeded to see the corresponding component service and noticed I had duplicate entries for rundll32.exe and RuntimeBroker components similar to the Runtime DCOM Server appears twice post. When trying to modify permissions I get the following error.




One or more of the permission entries attached to Registry Value has an unrecognized type and can not be displayed.




The jump list issues can be circumvented by manually calling the jump list component. However, the permission issue still exists and the cause is probably one of the Windows updates, considering that the Runtime Broker component service is duplicated and has a different ID.






windows windows-10 taskbar start-menu jumplist







share|improve this question

























  • You will need to remove Visual Studio and reinstall it in order to fix this problem. Worth pointing out this honestly sounds like an issue with your configuration, specifically, the junction points you have configured.

    – Ramhound
    May 9 '18 at 22:14











  • @Ramhound Are you sure this is a solution? Do you know, from experience, that it is indeed the issue? I really don't want to reinstall Visual Studio if I don't have to.

    – Igor Ševo
    May 10 '18 at 17:01











  • If I was not fairly confident, about the reason this problem even happens, I wouldn't have suggested it that solution. However, I don't believe in submitting single sentences as an answer, to any question especially to a problem that is as nuanced as this one.

    – Ramhound
    May 10 '18 at 17:16













  • I will give it a try. Thanks.

    – Igor Ševo
    May 11 '18 at 21:55











  • Repairing did not work.

    – Igor Ševo
    May 13 '18 at 15:41














3












3








3


2






I have noticed that all my taskbar and start menu jump lists are broken. They are broken in a very specific way:




  • The items show up, but clicking them does nothing (clicking dismisses the jump list, but does not open the corresponding app)

  • None of the items show a context menu when right-clicked (an empty gray box appears, as if an empty context menu appeared)

  • Jump lists and the context menus work in safe mode


My problem is very similar (if not identical) to the one described in Windows 10 Taskbar JumpList Issue, Not working and in Taskbar > File Explorer > Context Menu failing me and in the related Reddit post and in the related forum post. However, I have more information on the potential cause and more attempted solutions.



There are also two related posts on Microsoft Answers: related post on Microsoft Answers and the other related post, but none of the solutions worked for me (or for the original posters).



I noticed this in Anniversary Update, after updating Visual Studio. Then, I updated to April Update, which fixed the issue. Now, I updated Visual Studio (from 15.6 to 15.7) and it is broken again. The jump lists are broken on both the taskbar and start menu, and they are broken for all apps (both desktop and store).



Things I tried:




  • Deleting all files from the AutomaticDestinations directory

  • Deleting some files from the AutomaticDestinations directory

  • Resetting jump lists from settings

  • Reinstalling all Store apps with a PowerShell script

  • Running sfc /scannow

  • Running dism with restore health option

  • Pinning items

  • Restarting the computer

  • Restarting in safe mode and then restarting again

  • Disabling Internet Explorer

  • Using the Start Menu troubleshooter: It finds corruptions, but does not apply a fix

  • Copying TileDataLayer folder from different computers and then repairing

  • Creating a new user account (this also does not work)

  • Repairing Visual Studio (it just made Visual Studio slower)

  • Restoring the original AppData folder location and creating a junction point to it from the other partition

  • Removing all junction points related to Visual Studio

  • Completely removing all versions of Visual Studio and fresh installing Visual Studio 2017

  • Installing April Update

  • Installing October Update

  • Using the ShellExView to disable all shell extensions with Context Menu flag and all shell extensions whose File Created time and CLSID Modified Time was after the problems started occurring

  • Running the recommended script Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml"} which helps fix similar problems

  • Posting an issue on the Visual Studio feedback site and through the Feedback Hub application and waiting for a fix

  • Removing all CD/DVD mounting software

  • Turning jump lists on and off in the Settings

  • Setting the JumpListItems_Maximum in the registry

  • Using msconfig to test different startup configurations (disabling all non-Microsoft services – jump lists do not work, diagnostic startup – jump lists do not work; safe-mode – jump lists work)

  • Disabling OneDrive (both in startup and from Group Policy) – interestingly, the items that are opened from OneDrive do work; but all other items do not (both clicking and the context-menu).

  • Removing all Anti-Virus software


I have some junction points on my C: drive (all in Program Files and ProgramData).



It also seems that Cortana shortcut button (WinKey+C) gets broken whenever jump lists are broken (which is usually within a few days after repair installing Windows 10).



Can anyone provide any clues or suggestions?



Edit 1 (After restoring the default AppData folder)



A peculiar thing happens when accessing the Recent Items folder: when accessed by navigating directly to it in explorer, it does not contain the CustomDestinations and AutomaticDestinations folders, but when accessed by entering the same directory into Run the folders are visible along with many items that do not appear in jump lists.



Edit 2 (After repairing Windows installation)



Even though reupdating system to April Update resolved the problem, the question remains, since the actual cause of the problem is unidentified and I expect it to happen again after another Visual Studio update.



Edit 3 (After a few days)



After about two days of working properly after doing the repair install, my jump lists are not working again. All the history items are shown, but they are again unclickable and the context-menus are empty. Obviously, doing a repair install every few days is not an option. During the few days that the jump lists worked properly, I did not install anything on my system.



Edit 4 (After removing Visual Studio and removing junction points)



After opening Visual Studio 2017 and running a UWP (Microsoft Store) app with a debugger attached, my jump lists were destroyed again.



I decided to remove both Visual Studio 2015 and Visual Studio 2017 and reinstall Visual Studio 2017, remove all junction points I had (I had some junction points for Visual Studio installation), reinstall Visual Studio 2017 and repair install Windows. Removing Visual Studio installations and the junction points did not fix the issue. Repair installing did, as noted in the answer. However, setting up a scheduled task to reinstall Windows ever few days is really not a solution.



Edit 5 (After updating Visual Studio to 15.7.3)



The jump lists are broken again. They have been working for almost a few weeks. After Visual Studio update the jump lists show the same broken behavior.



Edit 6 (After updating Windows 10 to October 2018 Update)



Fixed for five days and then broken again. Possibly related to Visual Studio again. They seem to break when a UWP application is deployed.



Edit 7 (After meddling with startup configuration)



After trying to disable shell extensions, startup items and services, by various means (including msconfig, ShellExView, the Task Manager, the Registry Editor and the Services application), I have concluded that the only state in which the Jump Lists work is safe mode.



Edit 8 (After the insightful answer by Zenithies)



I have realized that I have many 10000, 10001 and 10016 errors in the Event Log. The 10000 and 10001 errors occur after attempting to click on a jump list item. Below are the errors.




Unable to start a DCOM Server: {C82192EE-6CB5-4BC0-9EF0-FB818773790A}.



Unable to start a DCOM Server: {9AA46009-3CE0-458A-A354-715610A075E6} as Unavailable/Unavailable.



The application-specific permission
settings do not grant Local Activation permission for the COM Server application with CLSID {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} and APPID {15C20B67-12E7-4BB6-92BB-7AFF07997402}




After going through the registry, I identified one of these to be the RuntimeBroker component. I proceeded to see the corresponding component service and noticed I had duplicate entries for rundll32.exe and RuntimeBroker components similar to the Runtime DCOM Server appears twice post. When trying to modify permissions I get the following error.




One or more of the permission entries attached to Registry Value has an unrecognized type and can not be displayed.




The jump list issues can be circumvented by manually calling the jump list component. However, the permission issue still exists and the cause is probably one of the Windows updates, considering that the Runtime Broker component service is duplicated and has a different ID.






windows windows-10 taskbar start-menu jumplist







share|improve this question
















I have noticed that all my taskbar and start menu jump lists are broken. They are broken in a very specific way:




  • The items show up, but clicking them does nothing (clicking dismisses the jump list, but does not open the corresponding app)

  • None of the items show a context menu when right-clicked (an empty gray box appears, as if an empty context menu appeared)

  • Jump lists and the context menus work in safe mode


My problem is very similar (if not identical) to the one described in Windows 10 Taskbar JumpList Issue, Not working and in Taskbar > File Explorer > Context Menu failing me and in the related Reddit post and in the related forum post. However, I have more information on the potential cause and more attempted solutions.



There are also two related posts on Microsoft Answers: related post on Microsoft Answers and the other related post, but none of the solutions worked for me (or for the original posters).



I noticed this in Anniversary Update, after updating Visual Studio. Then, I updated to April Update, which fixed the issue. Now, I updated Visual Studio (from 15.6 to 15.7) and it is broken again. The jump lists are broken on both the taskbar and start menu, and they are broken for all apps (both desktop and store).



Things I tried:




  • Deleting all files from the AutomaticDestinations directory

  • Deleting some files from the AutomaticDestinations directory

  • Resetting jump lists from settings

  • Reinstalling all Store apps with a PowerShell script

  • Running sfc /scannow

  • Running dism with restore health option

  • Pinning items

  • Restarting the computer

  • Restarting in safe mode and then restarting again

  • Disabling Internet Explorer

  • Using the Start Menu troubleshooter: It finds corruptions, but does not apply a fix

  • Copying TileDataLayer folder from different computers and then repairing

  • Creating a new user account (this also does not work)

  • Repairing Visual Studio (it just made Visual Studio slower)

  • Restoring the original AppData folder location and creating a junction point to it from the other partition

  • Removing all junction points related to Visual Studio

  • Completely removing all versions of Visual Studio and fresh installing Visual Studio 2017

  • Installing April Update

  • Installing October Update

  • Using the ShellExView to disable all shell extensions with Context Menu flag and all shell extensions whose File Created time and CLSID Modified Time was after the problems started occurring

  • Running the recommended script Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppXManifest.xml"} which helps fix similar problems

  • Posting an issue on the Visual Studio feedback site and through the Feedback Hub application and waiting for a fix

  • Removing all CD/DVD mounting software

  • Turning jump lists on and off in the Settings

  • Setting the JumpListItems_Maximum in the registry

  • Using msconfig to test different startup configurations (disabling all non-Microsoft services – jump lists do not work, diagnostic startup – jump lists do not work; safe-mode – jump lists work)

  • Disabling OneDrive (both in startup and from Group Policy) – interestingly, the items that are opened from OneDrive do work; but all other items do not (both clicking and the context-menu).

  • Removing all Anti-Virus software


I have some junction points on my C: drive (all in Program Files and ProgramData).



It also seems that Cortana shortcut button (WinKey+C) gets broken whenever jump lists are broken (which is usually within a few days after repair installing Windows 10).



Can anyone provide any clues or suggestions?



Edit 1 (After restoring the default AppData folder)



A peculiar thing happens when accessing the Recent Items folder: when accessed by navigating directly to it in explorer, it does not contain the CustomDestinations and AutomaticDestinations folders, but when accessed by entering the same directory into Run the folders are visible along with many items that do not appear in jump lists.



Edit 2 (After repairing Windows installation)



Even though reupdating system to April Update resolved the problem, the question remains, since the actual cause of the problem is unidentified and I expect it to happen again after another Visual Studio update.



Edit 3 (After a few days)



After about two days of working properly after doing the repair install, my jump lists are not working again. All the history items are shown, but they are again unclickable and the context-menus are empty. Obviously, doing a repair install every few days is not an option. During the few days that the jump lists worked properly, I did not install anything on my system.



Edit 4 (After removing Visual Studio and removing junction points)



After opening Visual Studio 2017 and running a UWP (Microsoft Store) app with a debugger attached, my jump lists were destroyed again.



I decided to remove both Visual Studio 2015 and Visual Studio 2017 and reinstall Visual Studio 2017, remove all junction points I had (I had some junction points for Visual Studio installation), reinstall Visual Studio 2017 and repair install Windows. Removing Visual Studio installations and the junction points did not fix the issue. Repair installing did, as noted in the answer. However, setting up a scheduled task to reinstall Windows ever few days is really not a solution.



Edit 5 (After updating Visual Studio to 15.7.3)



The jump lists are broken again. They have been working for almost a few weeks. After Visual Studio update the jump lists show the same broken behavior.



Edit 6 (After updating Windows 10 to October 2018 Update)



Fixed for five days and then broken again. Possibly related to Visual Studio again. They seem to break when a UWP application is deployed.



Edit 7 (After meddling with startup configuration)



After trying to disable shell extensions, startup items and services, by various means (including msconfig, ShellExView, the Task Manager, the Registry Editor and the Services application), I have concluded that the only state in which the Jump Lists work is safe mode.



Edit 8 (After the insightful answer by Zenithies)



I have realized that I have many 10000, 10001 and 10016 errors in the Event Log. The 10000 and 10001 errors occur after attempting to click on a jump list item. Below are the errors.




Unable to start a DCOM Server: {C82192EE-6CB5-4BC0-9EF0-FB818773790A}.



Unable to start a DCOM Server: {9AA46009-3CE0-458A-A354-715610A075E6} as Unavailable/Unavailable.



The application-specific permission
settings do not grant Local Activation permission for the COM Server application with CLSID {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} and APPID {15C20B67-12E7-4BB6-92BB-7AFF07997402}




After going through the registry, I identified one of these to be the RuntimeBroker component. I proceeded to see the corresponding component service and noticed I had duplicate entries for rundll32.exe and RuntimeBroker components similar to the Runtime DCOM Server appears twice post. When trying to modify permissions I get the following error.




One or more of the permission entries attached to Registry Value has an unrecognized type and can not be displayed.




The jump list issues can be circumvented by manually calling the jump list component. However, the permission issue still exists and the cause is probably one of the Windows updates, considering that the Runtime Broker component service is duplicated and has a different ID.






windows windows-10 taskbar start-menu jumplist




windows windows-10 taskbar start-menu jumplist






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 31 '18 at 16:36







Igor Ševo

















asked May 9 '18 at 20:45









Igor ŠevoIgor Ševo

1861516




1861516













  • You will need to remove Visual Studio and reinstall it in order to fix this problem. Worth pointing out this honestly sounds like an issue with your configuration, specifically, the junction points you have configured.

    – Ramhound
    May 9 '18 at 22:14











  • @Ramhound Are you sure this is a solution? Do you know, from experience, that it is indeed the issue? I really don't want to reinstall Visual Studio if I don't have to.

    – Igor Ševo
    May 10 '18 at 17:01











  • If I was not fairly confident, about the reason this problem even happens, I wouldn't have suggested it that solution. However, I don't believe in submitting single sentences as an answer, to any question especially to a problem that is as nuanced as this one.

    – Ramhound
    May 10 '18 at 17:16













  • I will give it a try. Thanks.

    – Igor Ševo
    May 11 '18 at 21:55











  • Repairing did not work.

    – Igor Ševo
    May 13 '18 at 15:41



















  • You will need to remove Visual Studio and reinstall it in order to fix this problem. Worth pointing out this honestly sounds like an issue with your configuration, specifically, the junction points you have configured.

    – Ramhound
    May 9 '18 at 22:14











  • @Ramhound Are you sure this is a solution? Do you know, from experience, that it is indeed the issue? I really don't want to reinstall Visual Studio if I don't have to.

    – Igor Ševo
    May 10 '18 at 17:01











  • If I was not fairly confident, about the reason this problem even happens, I wouldn't have suggested it that solution. However, I don't believe in submitting single sentences as an answer, to any question especially to a problem that is as nuanced as this one.

    – Ramhound
    May 10 '18 at 17:16













  • I will give it a try. Thanks.

    – Igor Ševo
    May 11 '18 at 21:55











  • Repairing did not work.

    – Igor Ševo
    May 13 '18 at 15:41

















You will need to remove Visual Studio and reinstall it in order to fix this problem. Worth pointing out this honestly sounds like an issue with your configuration, specifically, the junction points you have configured.

– Ramhound
May 9 '18 at 22:14





You will need to remove Visual Studio and reinstall it in order to fix this problem. Worth pointing out this honestly sounds like an issue with your configuration, specifically, the junction points you have configured.

– Ramhound
May 9 '18 at 22:14













@Ramhound Are you sure this is a solution? Do you know, from experience, that it is indeed the issue? I really don't want to reinstall Visual Studio if I don't have to.

– Igor Ševo
May 10 '18 at 17:01





@Ramhound Are you sure this is a solution? Do you know, from experience, that it is indeed the issue? I really don't want to reinstall Visual Studio if I don't have to.

– Igor Ševo
May 10 '18 at 17:01













If I was not fairly confident, about the reason this problem even happens, I wouldn't have suggested it that solution. However, I don't believe in submitting single sentences as an answer, to any question especially to a problem that is as nuanced as this one.

– Ramhound
May 10 '18 at 17:16







If I was not fairly confident, about the reason this problem even happens, I wouldn't have suggested it that solution. However, I don't believe in submitting single sentences as an answer, to any question especially to a problem that is as nuanced as this one.

– Ramhound
May 10 '18 at 17:16















I will give it a try. Thanks.

– Igor Ševo
May 11 '18 at 21:55





I will give it a try. Thanks.

– Igor Ševo
May 11 '18 at 21:55













Repairing did not work.

– Igor Ševo
May 13 '18 at 15:41





Repairing did not work.

– Igor Ševo
May 13 '18 at 15:41










3 Answers
3






active

oldest

votes


















1














I cannot know exactly what changes were done to your Windows setup,
so cannot analyze their effects. Some Windows products don't work well
with sensitive folders replaced by junctions, and the installation
of Visual Studio is extremely massive, making lots of additions
and changes to the Windows system.



In such difficult cases to analyze,
the solution might be to use a big hammer - Repair Install.
This does an in-place upgrade without losing anything other than all installed Windows Updates. It requires the installed Windows to be able to boot
and to run the installation process. It is also very important to use
the Windows installation media of the same major version of Windows
as is installed. Run Windows Update afterward, as all updates will be lost.



There is no guarantee that this will fix all the problems,
since this is not a clean install. Many settings that you changed will
stay, so this is not a cure-all solution.
But it is better than the destructive
Reset
or
Refresh.



For directions on performing the Repair Install see the article
How to Do a Repair Install of Windows 10 with an In-place Upgrade.






share|improve this answer
























  • It seems that the jump lists have a tendency to self-destruct. After a few days of normal work, they are broken again.

    – Igor Ševo
    May 16 '18 at 9:43











  • Your setup is self-destructing. I hate to say, but it seems to me impossible to analyze the problem in a non-standard setup such as yours, especially since it doesn't happen elsewhere. I hate to say it, but since this big gun didn't do the job, a bigger one is required. My above link also refers to the Reset and Refresh options, where Reset may optionally at least keep your personal files. Before starting, take good backups including disk image (AOMEI recommended) and test the restoration CD/USB. Next time I suggest avoiding structural changes in Windows - other easy solutions exist, just ask.

    – harrymc
    May 16 '18 at 10:42



















1














Another workaround worth trying:



Checking the possible cause of trouble:




  • Click random jump list item that does not work a few times.

  • Run Event Viewer (ie: WinKey+R-> eventvwr.msc)

  • Check section Windows Logs -> System

  • If you can see bunch of errors with DistributedCOM source and ID 10000 and error message that reads as: Unable to start a DCOM Server: {C82192EE-6CB5-4BC0-9EF0-FB818773790A}, please continue:


Running JumpViewerExecuteHelper manually





  • WinKey+R

  • run: %SystemRoot%System32rundll32.exe shell32.dll,SHCreateLocalServerRunDll {c82192ee-6cb5-4bc0-9ef0-fb818773790a}

  • If this is root cause of your trouble, UAC will ask you for elevated permissions for rundll32.exe process

  • After confirm, your jump lists should be working. (until restart or logging-off)


If this is the case, you can now create a shortcut:



Adding startup shortcut





  • desktopRight Click->New->Shortcut

  • target: %SystemRoot%System32rundll32.exe shell32.dll,SHCreateLocalServerRunDll {c82192ee-6cb5-4bc0-9ef0-fb818773790a}, named JumpListFix or anything of your liking

  • copy shortcut into %appdata%MicrosoftWindowsStart MenuProgramsStartup location, so you don't have to run it manually after each boot.


Notes




  • I have same problem on two different machines with Win 10 Home and Pro, both October 2018, Home is fresh-install

  • When I tried: WinKey+R-> dcomcnfg.exe to check permissions on, I've got warning: The CLSID {c82192ee-6cb5-4bc0-9ef0-fb818773790a}, item C:WindowsSystem32rundll32.exe and title JumpViewerExecuteHelper has named value AppID, but is not recorded under \HKEY_CLASSES_ROOTAppid. Do you wish to record it?

  • Adding it have not fixed the problem, fiddling with JumpViewerExecuteHelper permissions with dcomcnfg.exe didn't any good either.






share|improve this answer


























  • In my case, I have duplicate entries for the RuntimeBroker in component services. Thank you very much. You've been extremely helpful. I think this problem is still not resolved, as I still cannot fix it at the root. I can only circumvent it temporarily.

    – Igor Ševo
    Dec 31 '18 at 16:38



















0














I used the Media Creation Tool to create a Windows 10 ISO file. I then ran an installation of April Update (even though I had April Update installed) to "upgrade" my computer. The installation finished and the problem is now resolved. However, this is not a real solution, considering that it is quite bothersome to have to reinstall Windows every time I update Visual Studio 2017.



I had submitted feedback through the Feedback Hub and a Microsoft engineer replied that the issue was fixed in build 17682. I have yet to confirm this.



Edit (October 2018)



I can confirm that the issue is not fixed in build 17763.1. I have submitted another report through Feedback Hub.



Edit (December 2018)



I have applied a fix from Zenithies's answer. However, this only circumvents the actual problem described in the last edit.






share|improve this answer


























  • I'm happy to know that my suggestion in the comment worked for you, but the normal practice is to invite the commenter to write the answer, and especially when a bounty is involved.

    – harrymc
    May 14 '18 at 11:17











  • I don't consider this an actual solution and don't really mean to accept my own answer. It did work, but it seems like an unnecessary effort for something seemingly simple. If by the day before the end of bounty period there is no other reasonable answer, you can write your suggestion as an answer and I will remove this one.

    – Igor Ševo
    May 14 '18 at 17:27











  • For a real "solution" one would need to know exactly what changes you have done to Windows that caused the problem, otherwise the only solution is the big hammer. In general, Windows has a very complex structure, too complex even for Microsoft to fully control. Even experts hesitate to make any changes, especially untested ones, since small changes may have unforeseen large effects. But I think that you have found that out by now ;)

    – harrymc
    May 14 '18 at 19:20











  • I'm fairly convinced that the installation of Visual Studio is what broke it, but I guess I'll have to wait for the next update. In any case, post your answer and if there isn't a better answer, the bounty points are yours.

    – Igor Ševo
    May 14 '18 at 19:47








  • 1





    I've got several versions of Visual Studio installed side-by-side and I update them regularly, with no problems with jump-lists, but my Windows setup is fairly standard with no added junctions. It's possible that the installation in your case was confused by these changes - Windows doesn't always handle junctions correctly.

    – harrymc
    May 14 '18 at 20:12













Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1321248%2fbroken-jump-lists-on-windows-10%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























3 Answers
3






active

oldest

votes








3 Answers
3






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














I cannot know exactly what changes were done to your Windows setup,
so cannot analyze their effects. Some Windows products don't work well
with sensitive folders replaced by junctions, and the installation
of Visual Studio is extremely massive, making lots of additions
and changes to the Windows system.



In such difficult cases to analyze,
the solution might be to use a big hammer - Repair Install.
This does an in-place upgrade without losing anything other than all installed Windows Updates. It requires the installed Windows to be able to boot
and to run the installation process. It is also very important to use
the Windows installation media of the same major version of Windows
as is installed. Run Windows Update afterward, as all updates will be lost.



There is no guarantee that this will fix all the problems,
since this is not a clean install. Many settings that you changed will
stay, so this is not a cure-all solution.
But it is better than the destructive
Reset
or
Refresh.



For directions on performing the Repair Install see the article
How to Do a Repair Install of Windows 10 with an In-place Upgrade.






share|improve this answer
























  • It seems that the jump lists have a tendency to self-destruct. After a few days of normal work, they are broken again.

    – Igor Ševo
    May 16 '18 at 9:43











  • Your setup is self-destructing. I hate to say, but it seems to me impossible to analyze the problem in a non-standard setup such as yours, especially since it doesn't happen elsewhere. I hate to say it, but since this big gun didn't do the job, a bigger one is required. My above link also refers to the Reset and Refresh options, where Reset may optionally at least keep your personal files. Before starting, take good backups including disk image (AOMEI recommended) and test the restoration CD/USB. Next time I suggest avoiding structural changes in Windows - other easy solutions exist, just ask.

    – harrymc
    May 16 '18 at 10:42
















1














I cannot know exactly what changes were done to your Windows setup,
so cannot analyze their effects. Some Windows products don't work well
with sensitive folders replaced by junctions, and the installation
of Visual Studio is extremely massive, making lots of additions
and changes to the Windows system.



In such difficult cases to analyze,
the solution might be to use a big hammer - Repair Install.
This does an in-place upgrade without losing anything other than all installed Windows Updates. It requires the installed Windows to be able to boot
and to run the installation process. It is also very important to use
the Windows installation media of the same major version of Windows
as is installed. Run Windows Update afterward, as all updates will be lost.



There is no guarantee that this will fix all the problems,
since this is not a clean install. Many settings that you changed will
stay, so this is not a cure-all solution.
But it is better than the destructive
Reset
or
Refresh.



For directions on performing the Repair Install see the article
How to Do a Repair Install of Windows 10 with an In-place Upgrade.






share|improve this answer
























  • It seems that the jump lists have a tendency to self-destruct. After a few days of normal work, they are broken again.

    – Igor Ševo
    May 16 '18 at 9:43











  • Your setup is self-destructing. I hate to say, but it seems to me impossible to analyze the problem in a non-standard setup such as yours, especially since it doesn't happen elsewhere. I hate to say it, but since this big gun didn't do the job, a bigger one is required. My above link also refers to the Reset and Refresh options, where Reset may optionally at least keep your personal files. Before starting, take good backups including disk image (AOMEI recommended) and test the restoration CD/USB. Next time I suggest avoiding structural changes in Windows - other easy solutions exist, just ask.

    – harrymc
    May 16 '18 at 10:42














1












1








1







I cannot know exactly what changes were done to your Windows setup,
so cannot analyze their effects. Some Windows products don't work well
with sensitive folders replaced by junctions, and the installation
of Visual Studio is extremely massive, making lots of additions
and changes to the Windows system.



In such difficult cases to analyze,
the solution might be to use a big hammer - Repair Install.
This does an in-place upgrade without losing anything other than all installed Windows Updates. It requires the installed Windows to be able to boot
and to run the installation process. It is also very important to use
the Windows installation media of the same major version of Windows
as is installed. Run Windows Update afterward, as all updates will be lost.



There is no guarantee that this will fix all the problems,
since this is not a clean install. Many settings that you changed will
stay, so this is not a cure-all solution.
But it is better than the destructive
Reset
or
Refresh.



For directions on performing the Repair Install see the article
How to Do a Repair Install of Windows 10 with an In-place Upgrade.






share|improve this answer













I cannot know exactly what changes were done to your Windows setup,
so cannot analyze their effects. Some Windows products don't work well
with sensitive folders replaced by junctions, and the installation
of Visual Studio is extremely massive, making lots of additions
and changes to the Windows system.



In such difficult cases to analyze,
the solution might be to use a big hammer - Repair Install.
This does an in-place upgrade without losing anything other than all installed Windows Updates. It requires the installed Windows to be able to boot
and to run the installation process. It is also very important to use
the Windows installation media of the same major version of Windows
as is installed. Run Windows Update afterward, as all updates will be lost.



There is no guarantee that this will fix all the problems,
since this is not a clean install. Many settings that you changed will
stay, so this is not a cure-all solution.
But it is better than the destructive
Reset
or
Refresh.



For directions on performing the Repair Install see the article
How to Do a Repair Install of Windows 10 with an In-place Upgrade.







share|improve this answer












share|improve this answer



share|improve this answer










answered May 14 '18 at 20:31









harrymcharrymc

256k14268568




256k14268568













  • It seems that the jump lists have a tendency to self-destruct. After a few days of normal work, they are broken again.

    – Igor Ševo
    May 16 '18 at 9:43











  • Your setup is self-destructing. I hate to say, but it seems to me impossible to analyze the problem in a non-standard setup such as yours, especially since it doesn't happen elsewhere. I hate to say it, but since this big gun didn't do the job, a bigger one is required. My above link also refers to the Reset and Refresh options, where Reset may optionally at least keep your personal files. Before starting, take good backups including disk image (AOMEI recommended) and test the restoration CD/USB. Next time I suggest avoiding structural changes in Windows - other easy solutions exist, just ask.

    – harrymc
    May 16 '18 at 10:42



















  • It seems that the jump lists have a tendency to self-destruct. After a few days of normal work, they are broken again.

    – Igor Ševo
    May 16 '18 at 9:43











  • Your setup is self-destructing. I hate to say, but it seems to me impossible to analyze the problem in a non-standard setup such as yours, especially since it doesn't happen elsewhere. I hate to say it, but since this big gun didn't do the job, a bigger one is required. My above link also refers to the Reset and Refresh options, where Reset may optionally at least keep your personal files. Before starting, take good backups including disk image (AOMEI recommended) and test the restoration CD/USB. Next time I suggest avoiding structural changes in Windows - other easy solutions exist, just ask.

    – harrymc
    May 16 '18 at 10:42

















It seems that the jump lists have a tendency to self-destruct. After a few days of normal work, they are broken again.

– Igor Ševo
May 16 '18 at 9:43





It seems that the jump lists have a tendency to self-destruct. After a few days of normal work, they are broken again.

– Igor Ševo
May 16 '18 at 9:43













Your setup is self-destructing. I hate to say, but it seems to me impossible to analyze the problem in a non-standard setup such as yours, especially since it doesn't happen elsewhere. I hate to say it, but since this big gun didn't do the job, a bigger one is required. My above link also refers to the Reset and Refresh options, where Reset may optionally at least keep your personal files. Before starting, take good backups including disk image (AOMEI recommended) and test the restoration CD/USB. Next time I suggest avoiding structural changes in Windows - other easy solutions exist, just ask.

– harrymc
May 16 '18 at 10:42





Your setup is self-destructing. I hate to say, but it seems to me impossible to analyze the problem in a non-standard setup such as yours, especially since it doesn't happen elsewhere. I hate to say it, but since this big gun didn't do the job, a bigger one is required. My above link also refers to the Reset and Refresh options, where Reset may optionally at least keep your personal files. Before starting, take good backups including disk image (AOMEI recommended) and test the restoration CD/USB. Next time I suggest avoiding structural changes in Windows - other easy solutions exist, just ask.

– harrymc
May 16 '18 at 10:42













1














Another workaround worth trying:



Checking the possible cause of trouble:




  • Click random jump list item that does not work a few times.

  • Run Event Viewer (ie: WinKey+R-> eventvwr.msc)

  • Check section Windows Logs -> System

  • If you can see bunch of errors with DistributedCOM source and ID 10000 and error message that reads as: Unable to start a DCOM Server: {C82192EE-6CB5-4BC0-9EF0-FB818773790A}, please continue:


Running JumpViewerExecuteHelper manually





  • WinKey+R

  • run: %SystemRoot%System32rundll32.exe shell32.dll,SHCreateLocalServerRunDll {c82192ee-6cb5-4bc0-9ef0-fb818773790a}

  • If this is root cause of your trouble, UAC will ask you for elevated permissions for rundll32.exe process

  • After confirm, your jump lists should be working. (until restart or logging-off)


If this is the case, you can now create a shortcut:



Adding startup shortcut





  • desktopRight Click->New->Shortcut

  • target: %SystemRoot%System32rundll32.exe shell32.dll,SHCreateLocalServerRunDll {c82192ee-6cb5-4bc0-9ef0-fb818773790a}, named JumpListFix or anything of your liking

  • copy shortcut into %appdata%MicrosoftWindowsStart MenuProgramsStartup location, so you don't have to run it manually after each boot.


Notes




  • I have same problem on two different machines with Win 10 Home and Pro, both October 2018, Home is fresh-install

  • When I tried: WinKey+R-> dcomcnfg.exe to check permissions on, I've got warning: The CLSID {c82192ee-6cb5-4bc0-9ef0-fb818773790a}, item C:WindowsSystem32rundll32.exe and title JumpViewerExecuteHelper has named value AppID, but is not recorded under \HKEY_CLASSES_ROOTAppid. Do you wish to record it?

  • Adding it have not fixed the problem, fiddling with JumpViewerExecuteHelper permissions with dcomcnfg.exe didn't any good either.






share|improve this answer


























  • In my case, I have duplicate entries for the RuntimeBroker in component services. Thank you very much. You've been extremely helpful. I think this problem is still not resolved, as I still cannot fix it at the root. I can only circumvent it temporarily.

    – Igor Ševo
    Dec 31 '18 at 16:38
















1














Another workaround worth trying:



Checking the possible cause of trouble:




  • Click random jump list item that does not work a few times.

  • Run Event Viewer (ie: WinKey+R-> eventvwr.msc)

  • Check section Windows Logs -> System

  • If you can see bunch of errors with DistributedCOM source and ID 10000 and error message that reads as: Unable to start a DCOM Server: {C82192EE-6CB5-4BC0-9EF0-FB818773790A}, please continue:


Running JumpViewerExecuteHelper manually





  • WinKey+R

  • run: %SystemRoot%System32rundll32.exe shell32.dll,SHCreateLocalServerRunDll {c82192ee-6cb5-4bc0-9ef0-fb818773790a}

  • If this is root cause of your trouble, UAC will ask you for elevated permissions for rundll32.exe process

  • After confirm, your jump lists should be working. (until restart or logging-off)


If this is the case, you can now create a shortcut:



Adding startup shortcut





  • desktopRight Click->New->Shortcut

  • target: %SystemRoot%System32rundll32.exe shell32.dll,SHCreateLocalServerRunDll {c82192ee-6cb5-4bc0-9ef0-fb818773790a}, named JumpListFix or anything of your liking

  • copy shortcut into %appdata%MicrosoftWindowsStart MenuProgramsStartup location, so you don't have to run it manually after each boot.


Notes




  • I have same problem on two different machines with Win 10 Home and Pro, both October 2018, Home is fresh-install

  • When I tried: WinKey+R-> dcomcnfg.exe to check permissions on, I've got warning: The CLSID {c82192ee-6cb5-4bc0-9ef0-fb818773790a}, item C:WindowsSystem32rundll32.exe and title JumpViewerExecuteHelper has named value AppID, but is not recorded under \HKEY_CLASSES_ROOTAppid. Do you wish to record it?

  • Adding it have not fixed the problem, fiddling with JumpViewerExecuteHelper permissions with dcomcnfg.exe didn't any good either.






share|improve this answer


























  • In my case, I have duplicate entries for the RuntimeBroker in component services. Thank you very much. You've been extremely helpful. I think this problem is still not resolved, as I still cannot fix it at the root. I can only circumvent it temporarily.

    – Igor Ševo
    Dec 31 '18 at 16:38














1












1








1







Another workaround worth trying:



Checking the possible cause of trouble:




  • Click random jump list item that does not work a few times.

  • Run Event Viewer (ie: WinKey+R-> eventvwr.msc)

  • Check section Windows Logs -> System

  • If you can see bunch of errors with DistributedCOM source and ID 10000 and error message that reads as: Unable to start a DCOM Server: {C82192EE-6CB5-4BC0-9EF0-FB818773790A}, please continue:


Running JumpViewerExecuteHelper manually





  • WinKey+R

  • run: %SystemRoot%System32rundll32.exe shell32.dll,SHCreateLocalServerRunDll {c82192ee-6cb5-4bc0-9ef0-fb818773790a}

  • If this is root cause of your trouble, UAC will ask you for elevated permissions for rundll32.exe process

  • After confirm, your jump lists should be working. (until restart or logging-off)


If this is the case, you can now create a shortcut:



Adding startup shortcut





  • desktopRight Click->New->Shortcut

  • target: %SystemRoot%System32rundll32.exe shell32.dll,SHCreateLocalServerRunDll {c82192ee-6cb5-4bc0-9ef0-fb818773790a}, named JumpListFix or anything of your liking

  • copy shortcut into %appdata%MicrosoftWindowsStart MenuProgramsStartup location, so you don't have to run it manually after each boot.


Notes




  • I have same problem on two different machines with Win 10 Home and Pro, both October 2018, Home is fresh-install

  • When I tried: WinKey+R-> dcomcnfg.exe to check permissions on, I've got warning: The CLSID {c82192ee-6cb5-4bc0-9ef0-fb818773790a}, item C:WindowsSystem32rundll32.exe and title JumpViewerExecuteHelper has named value AppID, but is not recorded under \HKEY_CLASSES_ROOTAppid. Do you wish to record it?

  • Adding it have not fixed the problem, fiddling with JumpViewerExecuteHelper permissions with dcomcnfg.exe didn't any good either.






share|improve this answer















Another workaround worth trying:



Checking the possible cause of trouble:




  • Click random jump list item that does not work a few times.

  • Run Event Viewer (ie: WinKey+R-> eventvwr.msc)

  • Check section Windows Logs -> System

  • If you can see bunch of errors with DistributedCOM source and ID 10000 and error message that reads as: Unable to start a DCOM Server: {C82192EE-6CB5-4BC0-9EF0-FB818773790A}, please continue:


Running JumpViewerExecuteHelper manually





  • WinKey+R

  • run: %SystemRoot%System32rundll32.exe shell32.dll,SHCreateLocalServerRunDll {c82192ee-6cb5-4bc0-9ef0-fb818773790a}

  • If this is root cause of your trouble, UAC will ask you for elevated permissions for rundll32.exe process

  • After confirm, your jump lists should be working. (until restart or logging-off)


If this is the case, you can now create a shortcut:



Adding startup shortcut





  • desktopRight Click->New->Shortcut

  • target: %SystemRoot%System32rundll32.exe shell32.dll,SHCreateLocalServerRunDll {c82192ee-6cb5-4bc0-9ef0-fb818773790a}, named JumpListFix or anything of your liking

  • copy shortcut into %appdata%MicrosoftWindowsStart MenuProgramsStartup location, so you don't have to run it manually after each boot.


Notes




  • I have same problem on two different machines with Win 10 Home and Pro, both October 2018, Home is fresh-install

  • When I tried: WinKey+R-> dcomcnfg.exe to check permissions on, I've got warning: The CLSID {c82192ee-6cb5-4bc0-9ef0-fb818773790a}, item C:WindowsSystem32rundll32.exe and title JumpViewerExecuteHelper has named value AppID, but is not recorded under \HKEY_CLASSES_ROOTAppid. Do you wish to record it?

  • Adding it have not fixed the problem, fiddling with JumpViewerExecuteHelper permissions with dcomcnfg.exe didn't any good either.







share|improve this answer














share|improve this answer



share|improve this answer








edited Dec 29 '18 at 3:41

























answered Dec 29 '18 at 3:34









ZenithiesZenithies

463




463













  • In my case, I have duplicate entries for the RuntimeBroker in component services. Thank you very much. You've been extremely helpful. I think this problem is still not resolved, as I still cannot fix it at the root. I can only circumvent it temporarily.

    – Igor Ševo
    Dec 31 '18 at 16:38



















  • In my case, I have duplicate entries for the RuntimeBroker in component services. Thank you very much. You've been extremely helpful. I think this problem is still not resolved, as I still cannot fix it at the root. I can only circumvent it temporarily.

    – Igor Ševo
    Dec 31 '18 at 16:38

















In my case, I have duplicate entries for the RuntimeBroker in component services. Thank you very much. You've been extremely helpful. I think this problem is still not resolved, as I still cannot fix it at the root. I can only circumvent it temporarily.

– Igor Ševo
Dec 31 '18 at 16:38





In my case, I have duplicate entries for the RuntimeBroker in component services. Thank you very much. You've been extremely helpful. I think this problem is still not resolved, as I still cannot fix it at the root. I can only circumvent it temporarily.

– Igor Ševo
Dec 31 '18 at 16:38











0














I used the Media Creation Tool to create a Windows 10 ISO file. I then ran an installation of April Update (even though I had April Update installed) to "upgrade" my computer. The installation finished and the problem is now resolved. However, this is not a real solution, considering that it is quite bothersome to have to reinstall Windows every time I update Visual Studio 2017.



I had submitted feedback through the Feedback Hub and a Microsoft engineer replied that the issue was fixed in build 17682. I have yet to confirm this.



Edit (October 2018)



I can confirm that the issue is not fixed in build 17763.1. I have submitted another report through Feedback Hub.



Edit (December 2018)



I have applied a fix from Zenithies's answer. However, this only circumvents the actual problem described in the last edit.






share|improve this answer


























  • I'm happy to know that my suggestion in the comment worked for you, but the normal practice is to invite the commenter to write the answer, and especially when a bounty is involved.

    – harrymc
    May 14 '18 at 11:17











  • I don't consider this an actual solution and don't really mean to accept my own answer. It did work, but it seems like an unnecessary effort for something seemingly simple. If by the day before the end of bounty period there is no other reasonable answer, you can write your suggestion as an answer and I will remove this one.

    – Igor Ševo
    May 14 '18 at 17:27











  • For a real "solution" one would need to know exactly what changes you have done to Windows that caused the problem, otherwise the only solution is the big hammer. In general, Windows has a very complex structure, too complex even for Microsoft to fully control. Even experts hesitate to make any changes, especially untested ones, since small changes may have unforeseen large effects. But I think that you have found that out by now ;)

    – harrymc
    May 14 '18 at 19:20











  • I'm fairly convinced that the installation of Visual Studio is what broke it, but I guess I'll have to wait for the next update. In any case, post your answer and if there isn't a better answer, the bounty points are yours.

    – Igor Ševo
    May 14 '18 at 19:47








  • 1





    I've got several versions of Visual Studio installed side-by-side and I update them regularly, with no problems with jump-lists, but my Windows setup is fairly standard with no added junctions. It's possible that the installation in your case was confused by these changes - Windows doesn't always handle junctions correctly.

    – harrymc
    May 14 '18 at 20:12


















0














I used the Media Creation Tool to create a Windows 10 ISO file. I then ran an installation of April Update (even though I had April Update installed) to "upgrade" my computer. The installation finished and the problem is now resolved. However, this is not a real solution, considering that it is quite bothersome to have to reinstall Windows every time I update Visual Studio 2017.



I had submitted feedback through the Feedback Hub and a Microsoft engineer replied that the issue was fixed in build 17682. I have yet to confirm this.



Edit (October 2018)



I can confirm that the issue is not fixed in build 17763.1. I have submitted another report through Feedback Hub.



Edit (December 2018)



I have applied a fix from Zenithies's answer. However, this only circumvents the actual problem described in the last edit.






share|improve this answer


























  • I'm happy to know that my suggestion in the comment worked for you, but the normal practice is to invite the commenter to write the answer, and especially when a bounty is involved.

    – harrymc
    May 14 '18 at 11:17











  • I don't consider this an actual solution and don't really mean to accept my own answer. It did work, but it seems like an unnecessary effort for something seemingly simple. If by the day before the end of bounty period there is no other reasonable answer, you can write your suggestion as an answer and I will remove this one.

    – Igor Ševo
    May 14 '18 at 17:27











  • For a real "solution" one would need to know exactly what changes you have done to Windows that caused the problem, otherwise the only solution is the big hammer. In general, Windows has a very complex structure, too complex even for Microsoft to fully control. Even experts hesitate to make any changes, especially untested ones, since small changes may have unforeseen large effects. But I think that you have found that out by now ;)

    – harrymc
    May 14 '18 at 19:20











  • I'm fairly convinced that the installation of Visual Studio is what broke it, but I guess I'll have to wait for the next update. In any case, post your answer and if there isn't a better answer, the bounty points are yours.

    – Igor Ševo
    May 14 '18 at 19:47








  • 1





    I've got several versions of Visual Studio installed side-by-side and I update them regularly, with no problems with jump-lists, but my Windows setup is fairly standard with no added junctions. It's possible that the installation in your case was confused by these changes - Windows doesn't always handle junctions correctly.

    – harrymc
    May 14 '18 at 20:12
















0












0








0







I used the Media Creation Tool to create a Windows 10 ISO file. I then ran an installation of April Update (even though I had April Update installed) to "upgrade" my computer. The installation finished and the problem is now resolved. However, this is not a real solution, considering that it is quite bothersome to have to reinstall Windows every time I update Visual Studio 2017.



I had submitted feedback through the Feedback Hub and a Microsoft engineer replied that the issue was fixed in build 17682. I have yet to confirm this.



Edit (October 2018)



I can confirm that the issue is not fixed in build 17763.1. I have submitted another report through Feedback Hub.



Edit (December 2018)



I have applied a fix from Zenithies's answer. However, this only circumvents the actual problem described in the last edit.






share|improve this answer















I used the Media Creation Tool to create a Windows 10 ISO file. I then ran an installation of April Update (even though I had April Update installed) to "upgrade" my computer. The installation finished and the problem is now resolved. However, this is not a real solution, considering that it is quite bothersome to have to reinstall Windows every time I update Visual Studio 2017.



I had submitted feedback through the Feedback Hub and a Microsoft engineer replied that the issue was fixed in build 17682. I have yet to confirm this.



Edit (October 2018)



I can confirm that the issue is not fixed in build 17763.1. I have submitted another report through Feedback Hub.



Edit (December 2018)



I have applied a fix from Zenithies's answer. However, this only circumvents the actual problem described in the last edit.







share|improve this answer














share|improve this answer



share|improve this answer








edited Dec 31 '18 at 16:47

























answered May 14 '18 at 11:01









Igor ŠevoIgor Ševo

1861516




1861516













  • I'm happy to know that my suggestion in the comment worked for you, but the normal practice is to invite the commenter to write the answer, and especially when a bounty is involved.

    – harrymc
    May 14 '18 at 11:17











  • I don't consider this an actual solution and don't really mean to accept my own answer. It did work, but it seems like an unnecessary effort for something seemingly simple. If by the day before the end of bounty period there is no other reasonable answer, you can write your suggestion as an answer and I will remove this one.

    – Igor Ševo
    May 14 '18 at 17:27











  • For a real "solution" one would need to know exactly what changes you have done to Windows that caused the problem, otherwise the only solution is the big hammer. In general, Windows has a very complex structure, too complex even for Microsoft to fully control. Even experts hesitate to make any changes, especially untested ones, since small changes may have unforeseen large effects. But I think that you have found that out by now ;)

    – harrymc
    May 14 '18 at 19:20











  • I'm fairly convinced that the installation of Visual Studio is what broke it, but I guess I'll have to wait for the next update. In any case, post your answer and if there isn't a better answer, the bounty points are yours.

    – Igor Ševo
    May 14 '18 at 19:47








  • 1





    I've got several versions of Visual Studio installed side-by-side and I update them regularly, with no problems with jump-lists, but my Windows setup is fairly standard with no added junctions. It's possible that the installation in your case was confused by these changes - Windows doesn't always handle junctions correctly.

    – harrymc
    May 14 '18 at 20:12





















  • I'm happy to know that my suggestion in the comment worked for you, but the normal practice is to invite the commenter to write the answer, and especially when a bounty is involved.

    – harrymc
    May 14 '18 at 11:17











  • I don't consider this an actual solution and don't really mean to accept my own answer. It did work, but it seems like an unnecessary effort for something seemingly simple. If by the day before the end of bounty period there is no other reasonable answer, you can write your suggestion as an answer and I will remove this one.

    – Igor Ševo
    May 14 '18 at 17:27











  • For a real "solution" one would need to know exactly what changes you have done to Windows that caused the problem, otherwise the only solution is the big hammer. In general, Windows has a very complex structure, too complex even for Microsoft to fully control. Even experts hesitate to make any changes, especially untested ones, since small changes may have unforeseen large effects. But I think that you have found that out by now ;)

    – harrymc
    May 14 '18 at 19:20











  • I'm fairly convinced that the installation of Visual Studio is what broke it, but I guess I'll have to wait for the next update. In any case, post your answer and if there isn't a better answer, the bounty points are yours.

    – Igor Ševo
    May 14 '18 at 19:47








  • 1





    I've got several versions of Visual Studio installed side-by-side and I update them regularly, with no problems with jump-lists, but my Windows setup is fairly standard with no added junctions. It's possible that the installation in your case was confused by these changes - Windows doesn't always handle junctions correctly.

    – harrymc
    May 14 '18 at 20:12



















I'm happy to know that my suggestion in the comment worked for you, but the normal practice is to invite the commenter to write the answer, and especially when a bounty is involved.

– harrymc
May 14 '18 at 11:17





I'm happy to know that my suggestion in the comment worked for you, but the normal practice is to invite the commenter to write the answer, and especially when a bounty is involved.

– harrymc
May 14 '18 at 11:17













I don't consider this an actual solution and don't really mean to accept my own answer. It did work, but it seems like an unnecessary effort for something seemingly simple. If by the day before the end of bounty period there is no other reasonable answer, you can write your suggestion as an answer and I will remove this one.

– Igor Ševo
May 14 '18 at 17:27





I don't consider this an actual solution and don't really mean to accept my own answer. It did work, but it seems like an unnecessary effort for something seemingly simple. If by the day before the end of bounty period there is no other reasonable answer, you can write your suggestion as an answer and I will remove this one.

– Igor Ševo
May 14 '18 at 17:27













For a real "solution" one would need to know exactly what changes you have done to Windows that caused the problem, otherwise the only solution is the big hammer. In general, Windows has a very complex structure, too complex even for Microsoft to fully control. Even experts hesitate to make any changes, especially untested ones, since small changes may have unforeseen large effects. But I think that you have found that out by now ;)

– harrymc
May 14 '18 at 19:20





For a real "solution" one would need to know exactly what changes you have done to Windows that caused the problem, otherwise the only solution is the big hammer. In general, Windows has a very complex structure, too complex even for Microsoft to fully control. Even experts hesitate to make any changes, especially untested ones, since small changes may have unforeseen large effects. But I think that you have found that out by now ;)

– harrymc
May 14 '18 at 19:20













I'm fairly convinced that the installation of Visual Studio is what broke it, but I guess I'll have to wait for the next update. In any case, post your answer and if there isn't a better answer, the bounty points are yours.

– Igor Ševo
May 14 '18 at 19:47







I'm fairly convinced that the installation of Visual Studio is what broke it, but I guess I'll have to wait for the next update. In any case, post your answer and if there isn't a better answer, the bounty points are yours.

– Igor Ševo
May 14 '18 at 19:47






1




1





I've got several versions of Visual Studio installed side-by-side and I update them regularly, with no problems with jump-lists, but my Windows setup is fairly standard with no added junctions. It's possible that the installation in your case was confused by these changes - Windows doesn't always handle junctions correctly.

– harrymc
May 14 '18 at 20:12







I've got several versions of Visual Studio installed side-by-side and I update them regularly, with no problems with jump-lists, but my Windows setup is fairly standard with no added junctions. It's possible that the installation in your case was confused by these changes - Windows doesn't always handle junctions correctly.

– harrymc
May 14 '18 at 20:12




















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1321248%2fbroken-jump-lists-on-windows-10%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

Plaza Victoria

Image
Plaza Victoria Plaza Victoria en 2017 Otros nombres Plaza de La Victoria Localización El Almendral, Valparaíso, Chile Vías adyacentes Chacabuco, Molina, Plaza Victoria y Edwards Creación 1841 Metro Bellavista Ubicación 33°02′46″S 71°37′11″O  /  -33.04624167, -71.61980833 Coordenadas: 33°02′46″S 71°37′11″O  /  -33.04624167, -71.61980833 [editar datos en Wikidata] La Plaza Victoria , también llamada Plaza de la Victoria , [ 1 ] ​ es una plaza ubicada en el sector El Almendral del plan de la ciudad de Valparaíso, Chile, de importancia patrimonial, que incluye valiosas estatuas y especies vegetales. [ 2 ] ​ La plaza se creó como tal en la primera mitad del siglo XIX, tomando previamente los nombres de Plaza Nueva y Plaza de Orrego . Si bien desde sus inicios tuvo relevancia histórica, no fue sino a partir de fines de los años 1860 cuando comenzó a cobrar mayor importancia y se convirtió en uno de los principales centros sociales de l
Read more

In PowerPoint, is there a keyboard shortcut for bulleted / numbered list?

Image
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box; } 2 OneNote has two useful keyboard shortcuts for bulleted and numbered lists, namely Ctrl + . and Ctrl + - . Is there something similar for PowerPoint where the work with lists is also very common? Haven't found anything here: Use keyboard shortcuts in PowerPoint. keyboard-shortcuts microsoft-powerpoint share | improve this question edited Aug 14 '14 at 14:49 Linger 2,826 10 28 40
Read more

How to put 3 figures in Latex with 2 figures side by side and 1 below these side by side images but in...

Image
1 0 I want to put 3 images in LateX such as 2 figures are side by side horizotally and 3rd figure below these 2 side by side figures but in middle. I have following code: begin{figure}[H] centering begin{minipage}{.5textwidth} centering includegraphics[width=.50linewidth]{Text/Images/Genelec_8010_AP.jpg} captionof{figure}{Genelec 8010 AP} label{fig:Genelec 8010} end{minipage}% begin{minipage}{.5textwidth} centering includegraphics[width=.69linewidth]{Text/Images/Genelec_8020_CPM.jpg} captionof{figure}{Genelec 8020 CPM} label{fig:Genelec 8020} end{minipage}% end{figure} %%Here is my 3rd picture code begin{figure} centering includegraphics[width=5cm]{Text/Images/Genelec_8030_BPM.jpg} caption{Genelec 8030 BPM} label{fig:Genelec 8030} end{figure} I want to ask ho
Read more