I also am getting this message after updating to the Fall Creators Update. Windows 10 Pro, Version 1709, OS Build 16299.19, 64 bit on an Asus laptop.
I have four local accounts: the original admin account that I created as part of the build, (Florence) plus three other local user accounts for the three of us (Terry, Lucy, Maisie) (names changed). None of us ever use account switching, and the machine
is only ever used by one account at a time.
Suppose Lucy signs in, then shuts the machine down. Just shutdown, not a restart. Then I power the machine up, and I am presented with Lucy's sign in screen and current spotlight picture. I tab to user Terry, that's me, press Return, get my current spotlight
picture, and sign in. Later, I press Start, power, shutdown, and get the message "someone else is still... etc."
If I back off from that, Task Manager/Users shows me that Terry is signed in, with (38) after my name (whatever that means, running processes?), using about 1% cpu and about 600Mb memory, and it also shows me that Lucy is there too but with no number in
brackets after her name, a Status of Disconnected, 0% cpu and 44.5Mb memory. But I know for certain that Lucy has not been using the machine since I last switched it on. She did use it the time before though, which is why her signon screen was initially presented
this time round.
If I then use Task Manager/Users and press Delete on Lucy, her account gets signed out (I suppose) and then the shutdown "someone else..." message doesn't occur.
This message doesn't always occur but sometimes I sign in and out again more than once in succession. And sometimes I remember to choose restart instead of shutdown, and then remove the power at the appropriate point (the laptop battery has been removed)
to switch the thing off, because I read somewhere a while ago that doing that gives Windows a more complete restart, next time round.
It's no big deal for us, now that I've told Lucy and Maisie to ignore the warning and shut down anyway, hoping that you nice folk at Microsoft will soon fix whatever it is and an update will eventually sort it out. But since you did say to Mon.k11 that you'd
like to get it fixed, that would be nice. If you need any more information and ask, I can try a bit more with the limited resource that I have.