Shut down does not sign user out first

Windows 10 ‘Keeps you signed-in’ test: -
(Windows 10 Home 64-bit v1803, Build 17134.523 - Set up as Local Account)

Test 1 - Not signed-out:
1. Sign-in as ‘Visitor’ and then ‘Shut down’ without signing out.
2. Switch back on and sign-in as ‘Another User’ then shut down again. In this case an alert as follows appears: - “Someone else is still using this machine. If you shut down now they could lose unsaved work”. This proves that W10 did not sign 'Visitor' out before shutting down.

Test 2 - Signed-out:
3. Sign-in as ‘Visitor’ and sign-out first then ‘Shut down’ from sign-in screen.
4. Switch back on and sign-in as ‘Another User’ then shut down again. In this case no alerts appear but it is now ‘Another User’ who remains signed-in because they did not sign out before shutting down.

The above does not happen in Windows 8.1 which signs you out when you shut down the PC. It is clear that Windows 10 keeps you signed-in until you sign out manually. Is this a bug or setting on my Windows 10 Home machine or is it how W10 works?

I have looked for settings such as “Sign user out when user shuts down computer” but cannot find any.

I have tried switching ‘Fast start’ off but this does not fix the problem. All it does is increase the boot time.

I have seen a couple of sources that state that clicking ‘Start’ then ‘Shut-down’ is really hibernating and that W10 logs the user off before creating the hibernate file but in my case it is not signing a user out first so it may be a bug.

In order to bypass this Windows 10 problem/bug can anyone tell me if the following batch file script would sign-out the current user first then continue (after sign out is complete) to the ‘Shut down’ phase and shut down the laptop?
The batch file would be named “LO & SD.bat” (Log Off & Shut Down) and I would put it on each user’s desktop. Proposed script as follows: -

@ echo OFF
Shutdown /l (That is a letter l at the end, not a number 1)
Shutdown

I know I could try it and see how I get on but running batch files can have unwanted consequences and I did not want to confuse my OS and put it into a loop I can't get out of.

Any ideas welcome. Thanks.

Solved by forcing W10 to use "Shutdown.exe" command with switches as follows: -

Created a shortcut on desktop with "%windir%\system32\shutdown.exe -s -f -t 00" (without quotes) instruction and called it 'Shutdown'.

Double clicking on this shortcut signs user out before shutting down. Sorted.

This works differently to the Start/Shutdown command. Credit to "CountMike" on this forum: - Shutdown shortcut can't use F4 - Windows 10 Forums .

Thank you CountMike.

Update FYI - I have deleted the -f switch for safety and the shortcut still works fine. I notice that booting up takes a little longer so I take it that the shortcut performs a complete shutdown rather than hibernating. No problem.