If cpu fast then it's roughly 5 mins or quicker for all safe apps removal, plus i think extra ram and a fast ssd helps too, so it all subjective to other factors.
I'm used to the pause, always had it. One at 94% and sometimes another one at 98%. It will eventually continue. I also might have identified the setting responsible for blocking the Autorun programs on the first two boots (when MRP windows run). Still testing, but I think it's the setting for restoring the old SynchronizedRunOnce script execution. Code: :OriginalRunOnceSync=Yes It holds Explorer from executing, and that seems to f*ck up processing of Autorun entries.
Yesterday the "pause" really was more a halt, it didn't go thru, even after an hour wait. EDIT: my current test was with Enterprise 2024 LTSC, the halt was with 27723.1000 Canary
Originalrunonce option is a strange one as it can fix some issues with timing during setupcomplete etc but it can have weird side effects. Will have to add more info in the creator on that option as it can help or hinder if used. It basically runs things like setupcomplete etc as not all at once which can screw up timings when one script finishes before another completes and if it set to wipe the 'scripts' folder it then causes issues with missing other stuff. Win 7 and before it used to run things one by one, win8+ ms changed it to all at once to get to desktop fastest. Which isn't always what is best for some.
Ip or insider builds don't seem to play nice with mrp as I'm guessing ms have changed things in the insider builds during its testing phases which it not like mrp or maybe other scripts that adjust stuff etc might not work as expected either.
Used the setting with Yes for a long time, but it blocks Autorun programs (like OpenShell) only recently. Will now try without.
Openshell 191 or is there a new version out? Although I not auto install it myself unless the person I'm installing Windows for requests the old start menu of win7. Then I install it manually after setup completed if they want to get rid of the new w1x menu.
The last openshell I dloaded was 191 the one fixed for w11 use too. It may be 192 I can't remember but I know it was the one that worked on w11.
Yes, OpenShell 191. But it is installed already. Previously, following the OOBE phase of the upgrade, I got a popup "OpenShell must configure itself for the new OS" or similar, after which the OpenShell menu worked again. Now, it works only after the second reboot or logout as it is blocked from starting prior. Edit: Using this Start button:
When I get a chance I will preinstall openshell via my usertweaks. I have a registry file I install first that does all the settings I use in it, plus a picture file of the old win7 orbs it copy's to system32 for it so the menu looks very close to the win7 start menu. I guess we all have our methods but as long as the end goal looks and works as we wish then that is all that matters. The win7 orbs can sometimes upset win 11 start orbs if it set as left and you not remove that weather app thing that sits there before setting to left and not the default w11's center.
On my other pc that's on w11 I forgot the w7 orb file so it still has the original w11 orbs. Looks ok to me.
mxman2k, Look into that xml file. Tweaks applied by that method still work where other methods fail. Hit me up in private message for details. I added extra for oem partition and data partition for my own personal use on my laptop.
Have uploaded MRP 159 BT10 for beta testers The prevent telemetry option has been set to be far less aggressive when a LTSx edition is detected. Hopefully this will prevent other issues reported. Note that LTSx are more user controllable than 'normal' editions. This option may get adjusted as any new issues arrive or some extra telemetry stuff needs to be re-added for LTSx too. There are other small updates to other routines but i cannot remember and not have the energy to do a code compare between BT8 and BT9/10 at this time. Its been close to a month since my last update to MRP so thought i better get what is in the editor sent out and tweak the Telemetry part for LTSx as i was looking at the code in the editor. For the time being it is only for the LTSx editions, normal enterprise is as it was before with full aggressive approach to reduce telemetry, if the change of aggressiveness is also needed for enterprise please let me know and i will adjust the 'flag' used on the next MRP beta.