Remove Wireless Projection Banner from Desktop screen

I agree completely with this:

i don't think MS thought this through completely to realize that, unlike the remote desktop connection banner it emulates, wireless displays are used a LOT by regular users, home users, not just IT techs, sys-admins, etc.

I use it for work and at home and it drives me crazy - I have to end up rebooting a few times some days.  I'm glad to know if I disconnect with it it doesn't stay and cover the top tabs of the browser even though I may not be in range of the display I was connected to.  

The old way was just fine - using the pop-up to connect and disconnect.  I hate the way it pops down and covers my tabs when I am trying to project.  I'm doing training on a web-based system requires many tabs open and sometimes it's very hard to get to the tab I need to because the bar pops down when I get near it.  Please fix this.

This works and until a fix is released will do for now.

The process automatically restarts itself so no impact should be seen other than the banner being killed.

From a reply above -

Open Task Manager and, after making sure the "More details" button was selected, selecting the "Windows Shell Experience Host" process and clicking "End Task".

This will close the banner and then the "Windows Shell Experience Host" process restarts automatically all is good.

Need a few more instructions on that dll extension change, can't figure how to change owners name?

Does any body know what process is responsible for this banner so we can end it? I looked in the task manager window and it is not clear to me which one I should end.

It's not ideal but if you restart Windows File Explorer that will kill the bar. 

I had a teacher this morning with the same issue, infact all our teachers use miracast to connect to projectors/TVs all over our school and this new *feature* is highly agitating them, particularly when the bar stays there after having disconnected from a projector or TV.

I hope this is something that can be disabled via Group Policy or the registry, this decision has increased the number of support calls/tickets to our small helpdesk.