What's the difference of launching native executable from Visual Studio with launching the exe by myself?

Details:

1. A function does not work if I launch it directly

2. From VS2015, even if I choose "Start without debugging", it will work

3. The function is RtlQueryProcessDebugInformation, it always return 0xc0000022 unless I launch it from VS

4. the file is a WMI provider DLL, #2 is launching it with decoupled model with a .exe. Use shared host model wmiprovse.exe always does not work.

Visual Studio will attach a debugger to your process, even if it technically is a release build. That's why you can hit the stop button of the debugger. This does not apply when you start your EXE from say Explorer.

As for calling undocumented Windows functions, well, those give undocumented return values. What else did you expect? And what do you even mean with "it doesn't work"? A function works, when it behaves as documented.