Can you please supply more information, including what version of Chrome (see chrome://version) has the problem, and what version of Windows is in use? 

Is there any sort of error message?

The version is 58.0.3029.110 (64-bit). The test was performed on at least 6
devices presenting the same problem. There is no error message. Simply by
using the media / shortcut to open the "New Anonymous Window", right-click
(as pictured) it does not open anonymous mode as it should. That is the
problem.

2017-05-16 16:27 GMT-03:00 elawre… via monorail <
monorail+v2.271331812@chromium.org>:

Thank you for providing more feedback. Adding requester "elawrence@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Thanks. This is Windows 10? Is the Windows language set to Portuguese?

When you right-click the "New Anonymous Window" option, does an "Open" command appear? If you click that, does anything happen at all? Does this problem occur if you have one or more Chrome windows already open? Does it happen if NO Chrome windows are open? If you choose "New Anonymous Window" by clicking the menu item at the top-right inside Chrome itself (or by hitting CTRL+Shift+N) does an Incognito window open?

Yes, this is Windows 10!

Yes, it is set to Portuguese (Brazil).

The problem is this: When I right click on Chrome open on the desktop (as attached image at the beginning) in the "New Anonymous" option, Chrome does not open a new incognito window, Chrome opens a " New Window ".

The problem is that the command (using this means) does not work, does not display an error message, it simply opens a "New window".

So, the user thinks that he has opened an anonymous window, thinks that he is browsing anonymously, in fact opens a Normal Window.

Using the command (CTRL + Shift + N), Yes it opens an anonymous window, It works normally.

The problem is in the path described above (via toolbar, right click) that does not work as it should.

Thank you.

Hello,
I would like to give a return.
I performed several external tests, considering the same scenario of the corporate environment and I was successful.
I think the problem really is conflict with someone else's tool in the environment.
Thank you for your attention to the problem.

Sorry, can you elaborate on what you mean? I think you're saying: "It turns out that this problem was caused by other software we're running on our PC, so I wouldn't expect Chrome to be able to do anything to fix this. Please close this issue."

Is that correct?

Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot