Firstlogon is ran along side setupcomplete it may be run before setupcomplete.cmd as i cant remember the order in which they are run in, but both are run AFTER the user is created.
i do not use ini from them with this is set via regtweaks or via RunAsTI. I can gladly provide you with my complete $OEM$ folder in private
I am unable to test for a few days as got a busy week Using the creator to create the ini with just the option to not delete scripts folder would not affect anything else as MRP will just use defaults for all other options basically like not using the ini file.
Has it worked on a older MRP before 142? I have not changed much in MRP only the options and log text entries , so i don't think it is MRP as you are not using any options. Sadly i am unable to give a definitive answer as it is outside the scope of the project, it could be the change of rights (RunTI) - i honestly do not know.
I wonder if Defender is interfering, because on win 11 it is quite aggressive... Just trying to think what is causing bits to fail...
have built new build with Enterprise version Microsoft Windows Defender Updates 28.02.2022 Version: 1.359.1073.0 Engine Version: 1.1.18900.3 Platform Version: 4.18.2201.10 I do not toogle anything I will gladly give you the image Image Complete Original, set RegTweaks in Ordener you can dselbel ride setupcomplete.cmd All Information There
As i have said many times there is nothing in mrp that is sinister in any way. It is only compiled for ease of use, plus if it was in individual parts some bits could go missing or get corrupted and cause failure. If you or any one wants to take over the projects just ask as it would give me a break. But it not be as easy to work on as it can get very sensitive to changes.
I'm not good at it and certainly no professional I make many mistakes , not as many as i did when i took mrp over in 2016, it took me a few test runs before my first release. Have had much help from other developers on mdl which has kept the project alive.
Many years ago i had wrote a script that was like this project but just did the branding, very simple and just covered 4 brands used in Britain. Hp and compaq was a fussy brand and it can still throw a spanner in the works now and then. I found my old project the other day on a old back up image. Made me cringe how s**te my coding was back then Have learnt a lot since then and expanded mrp to what it is today. Due to other commitments and the brain injury i suffered in 2019, the time i can spend on coding is a lot less. Im still amazed how many still look forward to the next mrp release , think over 2300 downloads for version 142!!
There is saying in Jew Talmus Code: המתחיל במצווה אומרים לו גמור It's say if you start something good Keep doing it until it end It's still not the end So you have a work to do
Very true.... No matter how tough things have got, I'm still at the keyboard fixing, updating it. I am sure working on this project helped with my recovery.
The order according to Windows\system32\oobe\windeploy.exe Code: - RtlGetVersion: Client OS detected - IsUserProvidedScriptAllowed: IsOEMLicense, Enterprise-type edition detected, Client non-Enterprise OS edition detected with OEM license - FbeExtension: running PreOOBE commands - IsAuditBoot: running %windir%\Setup\Scripts\winbom.cmd - IsUserProvidedScriptAllowed: running %windir%\Setup\Scripts\oobe.cmd - Launching [C:\Windows\system32\oobe\oobeldr.exe /system] - Launching [C:\Windows\system32\oobe\msoobe.exe] - FbeExtension: running PostOOBE commands - IsUserProvidedScriptAllowed: running %windir%\Setup\Scripts\SetupComplete.cmd Fbe = First Boot Experience = undocumented registry keys, supported since Windows 8.1 (or 8): HKEY_LOCAL_MACHINE\Setup\FirstBoot no mention of Firstlogon.cmd, but it probably run (by other exe) afterwards is there an official documentation for it? is it affected by UAC and if AutoLogin is set?
If i remember the first time i heard of firstlogon.cmd was by seeing it mentioned in a autounattend.xml file to call the script. It may be listed on some m$ internal memo. But as we know they not always publicly release all data regarding windows.