Only a few apps are left alone, Store being one as for some odd reason it is required for some of the newer drivers or some will want to re-install it later anyway. Part of the XBox app is left behind to prevent problems later. Basically anything else is removed - if it can be done To totally remove apps etc there are other tools to do it on the WIM itself, but that is up to the individual in what they are comfortable with. MRP just does a simple removal using powershell , i not use DISM as it a bit clumsy for my liking and can cause weird results if not done properly especially via OOBE as you cant see anything onscreen.
Not sure if it is possible to clear all pinned apps on win 11 as there seems to be a minimum of x amount of apps that have to be on the start menu etc, if below that amount m$ will just dump random, err i mean place, items on it to make up the short fall.
I have addressed the issues raised by those that PM'd me, thanks for letting me know. Hopefully v141 will fix them. Nothing major or show stopping, one was spelling errors another a rewording to make better clarity. For now the Unicode part is still deactivated on Win7/Vista as no fully working method can be found. But that should not affect the majority of options that are auto-translated by the OS/Language, just a few odd options that have user entered text - such as Drive/Model name and some CT menu items. A few of the win 11 options have extra code added to cover the older and newer builds/updates. The 'expand explorer ribbon' option sometimes requires 2 logout/in or reboot cycles once the OS has installed to take effect, but have adjusted it to hopefully just need one like win 10 does. That option can be found under the [W1x {2}] tab about half way down the list in the ini creator. I did not add it to the win11 section as it covers both 10 and 11 and it is pointless to have it listed twice.
Due to WMIC being depreciated to the point that m$ have removed it from the latest DEV insider build (mistake or on purpose?), i have been trying p/shell methods to use the WMI system that PS still has access to, but gez is it slow! So for now I have done a check for WMIC.exe and if missing the next released QT and MRP will put a note in the log(s) and will run at reduced efficiency - a lot of queries will be skipped and so some systems may not be branded properly or lot of results may not be shown... As it only preview affected for now and not in the 'rtm/GA' ones MRP/QT will be ok, but if you attempt to use the projects on a later DEV build expect some strange results!! You could copy the c:\windows\system32\wbem folder from a older ISO/image but it could be language dependant and so issues could arise... However that will have to be up to the end user to copy that into the WIM, as even a compressed 'wbem' folder is still over 50mb..
Can you please add an option to restore wmic in new DEV builds and use it for the queries? It can be restored by replacing the folder \Windows\System32\wbem from build 22478. Thank you.
See my updated post, the folder even compressed is over 50mb as not sure what to remove around WMIC files, plus just overwriting the folder's contents could cause major issues, especially as some files within wbem are language dependant!
I have a 7z file of what i think are all the WMIC files from within wbem folder that are reduced to 7mb compressed but i not able to test if that will be enough as i not at home or have the latest DEV build. Plus time is limited for me at the moment.
That won't be enough, I already tried. The entire folder must be replaced. M$ likes to deprecate things without giving competent alternatives.
Exactly and if the OS you copied from is say English, and you copy it into say a Russian/Chinese or any other non english version it most likely screw the system up as there are folders and files are appear to be os/language dependant. I am very aware of other languages and try my best to have any option translate in some way. This is a bit more than MRP was intended for.. I will have to re-write both projects sooner rather than later it seems...
As i mentioned i am trying to find alternatives and may have to resort to AutoIT for a replacement WMIC command, once i can work out how it calls the api that PShell uses
I agree m$ like to remove things that have been in Windows for ages and work, i know WMIC can be a bit hit and miss due to some out put text is ANSI others something else, but the majority give the required results.. VRam on WMIC if over 4GB is incorrect, but even the posh p/shell doesn't get it right either, so it not that perfect for a replacement, plus the syntax can get way too complicated.
example wmic vs pshell to get same information via cmd prompt or batch script: Code: wmic idecontroller get name /value powershell -ExecutionPolicy Bypass -Command "Get-CimInstance -ClassName Win32_IDEController | Select-Object -Property Name | format-table -hidetableheaders" See the speed that WMIC gives results also how much more complex PS has to be to get same data!
Powershell is slower, but can be shortened Code: powershell -nop -ep bypass -c "(gcim Win32_IDEController).Name" Get-CimInstance is PS 3.0+, Win7 PS 2.0 need Get-WmiObject (gwmi)
I was going to use the CIM PS cmdlet just for the newer builfd(s) that not have WMIC present. For older still use wmic Means more work to have dual routines but i have already been re writing the BIOS and DMI parts using registry instead of WMIC so those will be universal OS sections. Just need to do CPU and memory ones..
Got a little time spare before i am off to invigilate a NHS exam... So downloading that 22483 build and see what i can work with and adjust in the projects over the next few days so that they have a half decent chance of working like they did... Because of this WMIC issue the releases of MRP 141 and QT 118 are on hold, sorry. if someone wants copy of the current RC of them to use on other OS's/Builds that do still have WMIC in please PM me and when i get time i will upload a copy of the current state they in , (before this WMIC fiasco), of the project(s). Remember they are test versions but so far everything works as intended. Typical m$ throw a curve ball - yet again!