This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ZAPP - Pin to Start displays error message

Hi,
I have been testing the Pin to Taskbar, Start Menu, and Desktop settings.

Windows 10 allows the end user to pin to Start Menu, Desktop, and the Taskbar. While Windows 7 only allows the end user to pin to the Desktop and the Taskbar.

When trying to utilize the Pin to Start Menu on Windows 10, we receive the following error: "Pin_Failed_StartMenuTiles (Bundle Name)". After clicking OK to the error, the shortcut is still added to the start menu.

The ZENworks log file states: [MetroStartMenuFolderingHandler] [] [EXCEPTION in AddItemMetroStartMenuThread with message-pin/unpin failed with message Verb confirmation check failed.]

I verified that this happens on a fresh install of the Windows 10 Enterprise LTSB 2016 without group policies, applocker, etc.

I know these features are supposed to be experimental, but is everyone else getting these same results?

Thanks,
Brandon Wise

Tags:

Parents
  • 0
    I tried to replicate this on my Windows 10 Pro (10.0.15063 Build) and it worked okay.

    Which log file did you see that message in? Are you on 17.1?
  • 0 in reply to 
    I found the message in the C:\Program Files (x86)\Novell\ZENworks\logs\LocalStore\zmd-messages.log file. We are utilizing the 17.1 agent.

    Windows Enterprise LTSB 2016 (10.0.14393)
  • 0   in reply to 
    I would recommend a Service-Request.
    This is not a known issue.

    For Troubleshooting, I would recommend testing with a User Profile that has never had a GPO applied and does not involve any type of Folder Redirection.
    These are not specifically prohibited.....but a possible source of generating unexpected conditions that may need to be handled.

    Also test removing any AV Software.
    AV Software can often block attempts to alter the Windows UI, since it could be viewed as trojan-like behavior.
    Very uncommon, but I've seen such things before.

    --

    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks

  • 0 in reply to   
    CRAIGDWILSON;2467496 wrote:
    I would recommend a Service-Request.
    This is not a known issue.

    For Troubleshooting, I would recommend testing with a User Profile that has never had a GPO applied and does not involve any type of Folder Redirection.
    These are not specifically prohibited.....but a possible source of generating unexpected conditions that may need to be handled.

    Also test removing any AV Software.
    AV Software can often block attempts to alter the Windows UI, since it could be viewed as trojan-like behavior.
    Very uncommon, but I've seen such things before.


    Hey Craig,
    I was concerned that it had to do with group policies. So I installed a fresh copy of Windows Enterprise LTSB 2016 (10.0.14393) without group policies. I also verified that the anti-virus was disabled. Unfortunately, it produced the same results, so I am trying to get my hands on the latest versions of Windows 10 (Creator's update) to see if that acts differently.

    If all else fails, I will attempt to open up a ticket with support.

    -Brandon
Reply
  • 0 in reply to   
    CRAIGDWILSON;2467496 wrote:
    I would recommend a Service-Request.
    This is not a known issue.

    For Troubleshooting, I would recommend testing with a User Profile that has never had a GPO applied and does not involve any type of Folder Redirection.
    These are not specifically prohibited.....but a possible source of generating unexpected conditions that may need to be handled.

    Also test removing any AV Software.
    AV Software can often block attempts to alter the Windows UI, since it could be viewed as trojan-like behavior.
    Very uncommon, but I've seen such things before.


    Hey Craig,
    I was concerned that it had to do with group policies. So I installed a fresh copy of Windows Enterprise LTSB 2016 (10.0.14393) without group policies. I also verified that the anti-virus was disabled. Unfortunately, it produced the same results, so I am trying to get my hands on the latest versions of Windows 10 (Creator's update) to see if that acts differently.

    If all else fails, I will attempt to open up a ticket with support.

    -Brandon
Children
  • 0   in reply to 
    Perhaps something about the bundles or the user name....Especially if there are non-English characters.

    Maybe logon as a simple user "bob".
    Make user only one bundle is assigned - "Notepad".

    This way no odd characters anywhere....no "too long" bundle name causing an issue.
    Again....those are not known issues either...but I could imagine those........

    The feature normally works..........So it's kind of trying to guess what is going on here.....
    All I can say is this is not a common problem. Fairly confident no open bugs around this feature.....



    wmed_bawise;2467546 wrote:
    Hey Craig,
    I was concerned that it had to do with group policies. So I installed a fresh copy of Windows Enterprise LTSB 2016 (10.0.14393) without group policies. I also verified that the anti-virus was disabled. Unfortunately, it produced the same results, so I am trying to get my hands on the latest versions of Windows 10 (Creator's update) to see if that acts differently.

    If all else fails, I will attempt to open up a ticket with support.

    -Brandon

    --

    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

    Be sure to "Like" My (and a few others) Cool Solutions below! 

    https://community.microfocus.com/members/craigdwilson/bookmarks