Window: After installation
- Thread starter BKPB
- Start date
- Messages
- 3,945
- Reaction score
- 1,651
This on the screenshot is the After Logon mode in Post-setup.
You can switch most of these to Before Logon, then it's invisible. Do it after loading the preset on a fresh ISO.
Let me know if anything changed in the last versions, not sure about your report how to look at it.
You can switch most of these to Before Logon, then it's invisible. Do it after loading the preset on a fresh ISO.
Let me know if anything changed in the last versions, not sure about your report how to look at it.
BKPB
Member
- Messages
- 91
- Reaction score
- 10
Previously, when executing, for example, Setup_Complete.cmd, only the command prompt window was displayed and the installation window was never launched. Or did I misunderstand your question ?
Post-Setup (Before logon) creates a single SetupComplete.cmd script from your commands.
When this script runs, it is hidden by the Windows setup screen.
Post-Setup (After Logon) creates a set of RunOnceEx tasks from your commands.
When the tasks the run, you are already logged on the desktop for the first time. All output is visible.
The difference is when each of them is executed. At the time when SetupComplete is running, Windows hides visible processes and no other windows can be displayed. After logon runs when you have a full desktop, and all windows are visible.
When this script runs, it is hidden by the Windows setup screen.
Post-Setup (After Logon) creates a set of RunOnceEx tasks from your commands.
When the tasks the run, you are already logged on the desktop for the first time. All output is visible.
The difference is when each of them is executed. At the time when SetupComplete is running, Windows hides visible processes and no other windows can be displayed. After logon runs when you have a full desktop, and all windows are visible.
BKPB
Member
- Messages
- 91
- Reaction score
- 10
After installation (before logging in), a single SetupComplete.cmd script is created, yes, it is,
but, firstly, the script execution is still displayed on the desktop.,
secondly, my commands can only be executed after logging in.
I have not received an answer to the main question that interests me.
1. When executing scripts or files, a window is displayed in addition to the command prompt window RUNDLL32.EXE .
Tell me, is this a new feature of NTLite or Windows?
Why is this happening, this process has never been started before, there was only a Command line display)
P.S. I'm trying to make the script execution process hidden, but even if I use .vbs, window RUNDLL32.EXE Anyway отображается.
but, firstly, the script execution is still displayed on the desktop.,
secondly, my commands can only be executed after logging in.
I have not received an answer to the main question that interests me.
1. When executing scripts or files, a window is displayed in addition to the command prompt window RUNDLL32.EXE .
Tell me, is this a new feature of NTLite or Windows?
Why is this happening, this process has never been started before, there was only a Command line display)
P.S. I'm trying to make the script execution process hidden, but even if I use .vbs, window RUNDLL32.EXE Anyway отображается.
Last edited:
The RunOnce dialog box cannot be hidden. RunOnce is used because all of your commands are executed with Admin rights, if you are a member of the Administrators group. If you want to run the commands a different way, create a Logon scheduled task which deletes itself after running. NTLite doesn't support this method.
You can create the Logon task from a script run during (Before logon), since it completes before you reach the Desktop. It should require the user be logged on, and use the Highest privilege if you want Admin rights.
You can create the Logon task from a script run during (Before logon), since it completes before you reach the Desktop. It should require the user be logged on, and use the Highest privilege if you want Admin rights.
BKPB
Member
- Messages
- 91
- Reaction score
- 10
Dear Garlin. I won't bother you with my questions anymore, but if you know, tell me why and when did the RunOnce execution engine start being used? I use NTLite every month when the next Windows build is released. And this window has never been there.
P.S. I use an online translator.
P.S. I use an online translator.
It's always been done this way with RunOnce. Most of the time, scripts will finish quickly and you don't notice the window flashing onscreen. But you're using an interactive batch file which keeps the RunOnce window open until the CMD window exits.
Why don't you rewrite the batch file so you don't need to pick the options?
Why don't you rewrite the batch file so you don't need to pick the options?