This message was deleted.

got back some advice from engineering Seems strange but the procmon could be a clue. Procmon has a mini-filter as well, and that could be forcing whoever is in the middle causing the bad behavior to step aside. One thing to try would be to try to execute the same thing from a administrator command window. Namely it is easy for things to jump into explorer.exe add ons that behave funny. And just to be clear, it is highly unlikely that this is being caused by our drivers. They just don't have that level of complexity to decide to not start something. If we see the open, we issue the open.