MSMG ToolKit

But when you have an SSD in GPT, unpartitioned. Only EFI, MS Reserved Partition and NTFS system partition that will fill the disk, will be created, no?

I dont remember this. I usually use Disk Genius - Partition Guru.

 

Yes, but it also creates 700mb recovery partition during or after installation (not sure when exactly).
So after succesfully installation theres: EFI (100mb), MSR (16mb), Primary, Recovery (700mb) partitions.

 

How intriguing... You can't manually create EFI and MSR and already create the system's NTFS? In this way the recovery will be in your C:\Recovery hidden folder.

 

Yes, you are right. It seems like manually creating a partition during setup using "diskpart" is the best option since Windows won't create a recovery partition automatically. That's ridiculous but it is as it is.
I guess there's no other way to block it.

 

If you use UUP dump to create/download base ISO(say 19041.1)
skipWinRE = 1 option in ConvertConfig.ini
And integrate updates via W10UI.cmd
By this way it won't automatically create WinRE partition during installation.

PS: In-place upgrade is not possible after this(YOU HAVE BEEN WARNED)

 

Not only that.
This function will also create an install.wim without the winre.wim image. And this will make it impossible to do in-place update. It will only be possible to perform a clean installation.
Be aware of this.

 

Indeed, that's the downside of creating an ISO without WinRE partition.

 

I never used winre in my life and I always done in place upgrades w/o any problem.

Where you got that idea?

Edit:

You're talking of the winre file inside the istall media, I thought you were talking about the partition layout of the installed OS.

 

Yes, downsize removing winre.wim image.

Yes, it break Manual Setup. So, if you remove winre.wim you will have no need for ManualSetup component.
But if you want to remove ManualSetup it is unnecessary (unless you want) to remove the winre.wim image.
Just to be clear.

 

Yepp.

My idea is (as I wrote many times) that creating an ISO in 2023 makes sense just for in place upgrades, so manual setup and winre should be left there.

For fresh installs, install.wim/esd is all you need. Creating ISOs w/o the ability to do in place upgrades is good just to waste some space when you archive them, then to waste some time each time the OS is going to be deployed.

 

While using TIMEOUT /T -1 fixes arrow keys causing next (2nd) pause to auto-pass,
BUT it has a similar problem with mouse handling:
- clicking on cmd title bar buttons (min/max) with left mouse = pass
- clicking on cmd title bar with right mouse = pass (+ left click anywhere = another pass)
- clicking any key on icon menu = pass

For this reason might be better to use another method:
pause>nul|set/p =Maybe press any key to continue . . .&echo.
As this solves the issue + no pass by mouse actions..

 

any info on when the toolkit will be updated? at least for supporting 19045.3208 22H2 Win 10?

 

It will probably be updated to support next monthly update or later. Not really a relevant question as msmg can't actually give people a realistic timetable.

 

seems like changing in 'toolkit.cmd' one thing, tricked the gears into enabling editing the 3208 version. just changed '3086' to '3208;.

Even though it had no errors or anything, some things like for ex. 'assigned access' could not be found for removal . Despite this, am gonna wait for the new update then edit again. Kind of have mixed feelings, there could be errors

 

It seems that Windows Restore function came back with this or last months update. But you can't actually use it as you normally (if you removed it) would, but files will start to clog up your drive as can be seen with apps like dism++

 

@MSMG,

@bala1 helped too.

Thnx, man!