Browser processes killed on WM_QUERYENDSESSION

My application is listening for the WM_QUERYENDSESSION message. If the user has not saved his work then a shutdown reason block is set (ShutdownBlockReasonCreate) and FALSE is returned.
When the user logoff, Windows display a screen showing applications that hang with the message defined with ShutdownBlockReasonCreate. If the user cancel the end of the Windows session because he realize that he haven't saved something, then the application is reshown but the browser processes have been killed and the application show balck screen insteed of the web page.

This is reproductible with the WebView2APISample, is you modify the WM_QUERYENDSESSION with:

case WM_QUERYENDSESSION:
{
    // yes, we can shut down
    // Register how we might be restarted
    /*RegisterApplicationRestart(L"--restore", RESTART_NO_CRASH | RESTART_NO_HANG);
    *result = TRUE;
    */
    ShutdownBlockReasonCreate(m_mainWindow, L"Block");
    *result = FALSE;
    return true;
}

Before the user query the end of session:

After the user canceled the end of session:

I think that the browser process should not be terminated before the application is realy being terminated.

If I use SetProcessShutdownParameters(0x3FF, 0); in the main application to set the shutdown priority the "highest" then the problem disappear. Is this because the application receive early the WM_QUERYENDSESSION and respond FALSE and then others processes do not receive the WM_QUERYENDSESSION ?
Is this workaround will always works ?

AB#46194890