Fortunately, I found a way around problem #2:

I want to put picture when seeing windows shutting down as I fall sleep and the background is ugly.
Here is how it looks like

However, now shutting down picture is not logon picture anymore so I cannot not use logon screen tweaker.

Is there anyway to change the start/shutdown screen?

Thanks

I agree. In Win7, the shutdown screen is NOT opaque. Further, it doesn't appear for
a few seconds, and, in fact, I can delay it w/my own program, due to serialization of
SetConsoleCtrlHandler PIDs. This way, I am able to see my consoles' output briefly.
Now, I am forced to rely on log files exclusively! Basically, I lost a debugging aid...

I want to put picture when seeing windows shutting down as I fall sleep and the background is ugly.
Here is how it looks like

However, now shutting down picture is not logon picture anymore so I cannot not use logon screen tweaker.

Is there anyway to change the start/shutdown screen?

Thanks

I downloaded a program UI to change the locked login screen. The forum stated that unlike Windows 7 you couldn't just edit the registry and that the program supplied was needed to modify files. Actually it doesn't seem as complicated as stated, Windows 10 seems to have a series of executable configuration files called answer files (extension .xml). I'm still looking at the files assessing if i need to modify a file or create a new file and figure the command line to have this new file executed by Windows 10 unless its as simple as just writing the command and the file is automatically executed.
Custom shutdown screen




Windows provisioning answer file

What it is i think is that the registry has a lot of hidden root pathways the answer files overlay the registry like a custom rootkit that was placed in windows 10 by Microsoft.

This is the Lock screen changer. the sdk is available at the website.

No one has an answer to these yet?

1. How can I stop this IMMEDIATE(!) BLUE OPAQUE SHUTDOWN SCREEN
so I can watch how my programs react to shut down, as I can in Win7?
Perhaps RegQueryValue=FadePeriodConfiguration, length=144?

Perhaps this next one will fix both...???

2. How can I serialize shutting down processes, again, as Win7 does, where
the black shutdown screen ONLY appears AFTER all processes have been dealt
with? This kinda defeats the SetProcessShutdownParameters/ShutdownLevel API.
Using my program running multiples in Win7, I can give myself time to shut
down PROCMON to avoid its' 'file corrupted' msg when I try to open it later.
Perhaps RegQueryValue=SerializeAppShutdown, length=16?

I can't find any doc on these 2 registry values on the Web...

Although I do not know what to use as a value for SerializeAppShutdown
(various attempts all failed), I did find that csrsrv.dll apparently is
the program that uses it. However, in my multiples, if I "randomly" assign
the SHUTDOWNLEVEL so that each is unique, starting with 201h, then they no
longer shut down at the same time, and so I can once again extend my
shutdown time. That is, for each one, at startup, I add the current # of
seconds in the TOD clock to it. This then "serializes" them, similar to Win7
(assuming the # of seconds aren't the same, controlled by when I start them).