Multi-OEM/Retail Project {MRP} - Mk3

I thought there may be a way via the Store or via PowerShell etc but didn't want to say in case i had wrong info.

 

If i understand how the msmg toolkit removes those 'features' is by either powershell or dism or a combination of both.

Not used the toolkit personally so im not familiar with how it works.

Mrp can disable/hide certain bits but any chosen app is only removed by powershell commands and not dism. The list of apps removed is shown on the mrp ini creator's apps tab. Most can be reinstalled if required by the store or by obtaining the required appx files.

Note that Defender when disabled by mrp does not remove it but makes it very difficult to make it active again, so it is wise to think if that is what is needed, as to revert the option is almost impossible!

 

The photo viewer as the default image viewer is set for win11 is working too.

If the important photo viewer dll file it uses is removed by ms at any future time, then the option will auto disable.

 

MRP 143 is progressing a bit slower than usual due to not having as much time to work on it, no new options added at the moment, but one or two old ones have been updated and other code updates done.

PhotoViewer option is the main one that been updated and is for Windows 10 and 11 only as previous OS's i think Photoviewer was default or could be set as default far easier than W10+ can be.

At T10 stage at moment as quite a bit of code has been moved, deleted or re-written to be as efficient as possible. All boring 'housekeeping' duties really.

Decompile.exe has had a makeover too, first time since 2016 - quite a lot of code was redundant, or was left in for testing, that never got taken out, it shaved off a few KiB's -- but those got added back with the code updates in the main project!

Query Tool has not been updated as such - only one part about the CPU Family which the database was not complete and so only the numeric value is shown now until i can get the D/Base filled.

 

Defender is mrp's nemesis

Chkvalid basically checks a string passed to it for invalid characters and either removes them or substitutes to one that not cause a crash.

Invalid Chars include ( l )^&£@? And a few others.

Plus as it is in autoit Defender and some av's throw its dummy out.

Not started on the qt yet as time is a bit tight at present.

 

Working on a method to filter invalid chars that not use AutoIT or PowerShell so it is compatible with all supported OS's...

That should prevent any AV from screwing up the projects.

So far it will allow a-Z and 0-9, _ , -, { }, [ ], any ( ) brackets are replaced with { } the '&' and '!' chars are removed.

Language's with umlauts, or special chars etc i will have to filter those when i get time.

Spoiler: VBSCRIPT: Filtering Code - so far

Code:

' If nothing passed just return empty string, prevents errors.
if WScript.Arguments.Count = 0 then wscript.quit

PassVar = Wscript.Arguments(0)
wscript.echo CleanUp(Passvar)
wscript.Quit

Function CleanUp (input)
      Dim objRegExp, outputStr
      Set objRegExp = New Regexp

      objRegExp.IgnoreCase = True
      objRegExp.Global = True

      objRegExp.Pattern = "[^a-zA-Z0-9{}\[\]\-\(\) \_]"
      outputStr = objRegExp.Replace(input, "")

      objRegExp.Pattern = "\&\!+"
      outputStr = objRegExp.Replace(outputStr, "")

      objRegExp.Pattern = "\(+"
      outputStr = objRegExp.Replace(outputStr, "{")

      objRegExp.Pattern = "\)+"
      outputStr = objRegExp.Replace(outputStr, "}")

      CleanUp = outputStr
End Function

Save as filter.vbs or any filename.

Usage:

Cscript //nologo filter.vbs "your text or passed string variable to filter"

Returns:

The filtered string.

filter.vbs can be any filename.

Any help with this much appreciated.

Note: This is just a rough starting point so some parts may not be needed.

---------------
Have edited the QT/MRP code to hopefully prevent the detection of 'Multi-Languages' from having issues...

 

Did mrp run and just any tweaks you had set via the mrpconfig.ini did not work/set?

As long as mrp ran and oobe mode detected all should run as normal, mrp works best via a clean install, but does run if you do an in place install too.

Odd times when in place being done branding or some theme elements not get set, think that more to do with if the os being overwritten has any errors that could cause a few issues.

Also i have had the rare occasion where some tweaks would not set but that was down to testing a 'edited' os that someone mentioned mrp not work on.

At present the tweaks set by the config maker are not usable outside of mrp. I have thought about a version that they could be used/set as a standalone but that is still on the back-burner until i have more time.

 

What i mean about os being in place upgraded having errors or issues is things like broken services or some file/registry permission locks etc.

Those issues as above can cause a install to fail or certain elements of the install not work as expected and not just affect mrp.

 

Hmm im wondering if ms have done changes in the setup/oobe stage that prevents oobe.cmd/setupcomplete etc from running.

I know it used to up till 1909 w10 as that was last time i did a repair install for a pc.