Multi-OEM/Retail Project {MRP} - Mk3

Thanks for confirming...

I think it could be a new win 11 issue for Pro and above , it used to just be home editions that didn't like that option to disable network adaptors.

Not much i can do as it is a standard wmic , vbscript and powershell command line in that order that turns the adaptor(s) off and back on later. If one fails the next in line is tried until pshell one is last in line to try, then it mentions in the log either that the adaptor(s) failed to disable or enable.

 

The re-enable network adaptor(s) code is as follows for those interested...

Powershell (via admin cmd) enable:

Code:

Powershell -Command "Get-NetAdapter | ? status -ne up | Enable-NetAdapter -Confirm:$false"

Wmic enable (same as vbscript way):

Code:

wmic path win32_networkadapter where "physicaladapter=true" call enable

VBscript:

Code:

strComputer = "."
Set objWMIService = GetObject("winmgmts:[locale=ms_409]!\\" & strComputer & "\root\CIMV2")
Set colItems = objWMIService.ExecQuery("SELECT * FROM Win32_NetworkAdapter Where NetEnabled = 'False'")

For Each objItem in colItems
objItem.Enable
Next

Pretty much standard codes..

 

At times I'm sure they are !!, joking aside, as they really not like MRP or its internal parts at least , may be because it tweaks their darling defender, or turns off co-pilot etc

May be I'm paranoid but ever since i added the tweaks part to MRP defender has been quite aggressive towards the project and other AV's too.

 

I know hp and compaq computers are problematic at times.

Never had Gigabyte not play by the rules.

Any logs would help.

 

Autounattend is possible to upset mrp it depends if it calling any scripts that delete the scripts or setup folders usually by a RD xxxxxx type line of code.

Think the loader cmd does that.

 

I am at a loss trying to work out why it works on a vm yet not on the actual pc.

 

By default mrp will delete the scripts folder once it has completed and the desktop is shown unless you select the option not to auto delete scripts folder then mrp won't delete that folder.

It's all about tidying up. Oh and users choice.

 

Using the loader script if the slic is correct and not corrupted in some way then the loader will just use its certificate and slp key. If slic corrupted in any way it will ignore it and use its own method to insert a slic into the drives mbr area to fool windows.

 

let me check the logs first

 

It seems to have crashed out checking the system's RAM/Memory..

You may have a faulty ram stick?

 

Im guessing it is a socket 775 cpu , the chipset could have issues with memory modules , i remember having a gigabyte board years ago that didnt like either single sided or double sided ram modules it had to be one type only and not mixed and if you tried to exceed its maximum capacity it did some strange things.