I was thinking if it was kaspersky av nabbing the chkvalid.exe which checks for any invalid characters such as ( ) etc. But have still added the new code to check and if ok the motherboards maker name as a last resort for the next qt , have put it in mrp 144 bc2 already.
There again defender on w11 is very aggressive these days. Kaspersky's method to set files etc to ignore is not as easy. It tends to reset your exclusions list when it updates.
Finally the wait is over for many.... MRP v144.0 has been uploaded, 2nd post's download link, password and hashes have been updated. Spoiler: MRP144 Summary This is a major bug fix version, no new options added but some may of been updated. + Added an extra DMI check for the Mother Board's maker, this will be used as a very last resort when no other DMI, SLIC or MSDM branding can be used. This will be overridden when the user selects another brand from the Custom Theme list within the MRPCreator. + Added a variable that can be set in the oobe.cmd file which will tell MRP to NOT delete the Scripts folder when it completes. This overrides the option to do the same within the MRPCreator, this was added so that those who just use MRP to do the branding and not use any of the tweaks/options so that you can use your own set of programs/tweaks to install and not have them vanish/not work because MRP had deleted the Scripts folder. + When Windows 11, (dev and later), or any Server OS is being installed if the option to 'disable network connections during oobe' is used then it will be auto disabled as it can cause some issues with Windows Setup program. + When windows 11 is detected being installed the InSpectre program to check for Meltdown/Spectre is auto disabled because it appears not to be fully compatible with the newer OS and gives either false results or can cause Setup to 'halt/hang' so to prevent that it will be ignored/disabled. + Added TPM Vendor/Maker name to the TPM detection line, if it is available, if not and a numeric version is found not to be in the MRP's database then the number will be shown instead. The majority of the main makers is added such as Intel, AMD etc. + Fixed the rare issue on later w11 builds including dev, in that MRP can hang or abort during the section that disables the Defender's main service during OOBE and SmartScreen. It will be now be disabled at a later stage when the option to disable Defender is used. + Added more debug lines into the log(s) more to the early log to hopefully find where a glitch has happened if it does. + Fixed the issue when using MRP 142/3 in that the TaskManager's screen would default to details, this has now been sorted and no longer changes the order in which it is displayed. Hopefully that is the majority of any bugs that have been reported or i have found during the past month are now sorted.
Add this too. For Windows 11 Install. It will Force to use local Acc. Code: :: OOBE\BYPASSNRO by avayo reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE /v BypassNRO /t reg_dword /d 1 /f You can add this too. Code: :: hide unsupported nag on update settings by avayo reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate /v TargetReleaseVersion /d 1 /t reg_dword /f reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate /v TargetReleaseVersionInfo /d 25H1 /f
A registry key that causes oobe to not require a network, and then subsequently allow you to create a local account on a clean install. Will add it for next mrp
I knew that HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE had many bits to it but could never find a full list, mrp uses a few well known ones via several options.
I have another ideas, Since it download & Install updates in OOBE stage Can use this, to disable & Enable all Network adapters Code: powershell -noprofile -executionpolicy bypass -command "Get-NetAdapter | foreach { Disable-NetAdapter -Name $_.Name -Confirm:$false }" CMD /c reg add "HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce" /f /v "RunOnce" /t Reg_SZ /d "powershell -noprofile -executionpolicy bypass -command \"Get-NetAdapter ^| foreach { Enable-NetAdapter -Name $_.Name -Confirm:$false }\""
That was used already , plus the WMIC version but it caused w11 oobe to loop or just fail to go further so that option is auto disabled to prevent that. On w10 and below it works ok.
you forgot something the oob.cmd and the setupcomplete.cmd are actually executed at the same time, i told you then i have an idea Setucomplete.cmd Code: IF EXIST "%Windir%\Setup\Scripts\DeCompile.exe" ( CALL "%Windir%\Setup\Scripts\DeCompile.exe" DEL /F /Q "%Windir%\Setup\Scripts\DeCompile.exe" >nul ) REM Added a early log that is created during the silent oobe part. Will be auto deleted when MRP completes. REM This is for debugging when something causes MRP to abort in the early stages. Please do not rename. IF EXIST "%Windir%\Setup\Scripts\Install.cmd" CALL "%Windir%\Setup\Scripts\Install.cmd" >"%SystemDrive%\EarlyRun.log" IF EXIST "%Windir%\Setup\Scripts\MRPInstall.cmd" CALL "%Windir%\Setup\Scripts\MRPInstall.cmd" >"%SystemDrive%\EarlyRun.log" cd /d "%~dp0" :: REM Microsoft Office LTSC Professional Plus 2021 v2202 Build 16.0.14931.20120 (Price 832.52 USD) :: call %~dp0Office_Installer.cmd" :: REM Office 2021 Offline KMS Aktivator (KMS_VL_ALL_AIO-45) :: call %~dp0KMS_VL_ALL_AIO.cmd /s /a :: No yet: : REM Windows 10/11 Digital Lizenz Aktivierung (MAS 1.5) ::: reg query HKU\S-1-5-19 1>nul 2>nul || exit /b :: start /b /wait cmd /c "%~dp0HWID_Activation_AIO.cmd" /a reg add HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce /v firstlogon /t REG_SZ /d %windir%\Setup\Scripts\firstlogon.cmd /f I still have to finish something, I could also have shown him how the whole thing works without circumstances
Setupcomplete.cmd is ran after oobe and just before the desktop appears when using windows setup. Oobe.cmd is run after the the screen about copying of files/expanding files part is shown via setup and the bit when it says it will reboot in x seconds... MRP uses the standard rules of windows installation. If the user has a different method to install the os then it is outside the scope of this project. I cannot cover every way users install the os as each has their own ways and would not be viable for me to spend time trying to make the project work in each case. I try to make mrp work with other methods but i do have to draw a line when it could cause the project to malfunction for others.
There is a post that @abbodi1406 shows the way in which windows setup runs and the sequence it uses. Found the post about the sequence: https://forums.mydigitallife.net/th...l-project-mrp-mk3.71555/page-398#post-1724745
Remember also that MRP is designed to be run ONLY during early oobe (via oobe.cmd), it will NOT run at any other stage. This has always been like that because certain aspects of the theme/branding needs to be done via the early stage so that it bypasses some permissions which are set later on during setup. Plus as some options that are in MRP now also need to be run early on, such as the Defender disable part to get around the OS blocking such actions. Therefore you cannot run MRP at SetupComplete or FirstLogon stage.