Solved CMD format ssd for install

cereberus said:

This is exactly how I set up my drive 0. Like you, I only image backup 1st four partitions (3 hidden and C drive). The data partition is backed up separately.

IMO, this is the optimum layout unless you have a second data drive in which case, it is rather optional to have a data drive on drive 0.

I note the OPs layout is an mbr drive which is just asking for update troubled as Windows 11 is nominally designed for UEFI/GPT.

Click to expand...

Hi,
The system this question is about is not mbr dude read the screen shot again it clearly shows 1-260mb efi partition although the second 16mb is hidden by disk management actually on both m.2's lol

My z490 and x299 and x99 systems are the same partition setup except they are mbr and were a crapload easier than this gpt system was to setup this way.

ThrashZone said:

Hi,
The system this question is about is not mbr dude read the screen shot again it clearly shows 1-260mb efi partition although the second 16mb is hidden by disk management actually on both m.2's lol

My z490 and x299 and x99 systems are the same partition setup except they are mbr and were a crapload easier than this gpt system was to setup this way.

Click to expand...

Yeah misread it.
Either way OPs setup is sub optimal, and higher risk of updates failing to work as required.

cereberus said:

Yeah misread it.
Either way OPs setup is sub optimal, and higher risk of updates failing to work as required.

Click to expand...

All are setup exactly the way I want them now lol
As far as this system one goes I could say I deleted a oem recovery partition and that's why it's that large

To sum up the easiest way to install with system recovery in front of C
Create one partition 1-2-3gb first then install windows as you normally would
Installer will create the efi and gpt partitions in front of C by default although the installer did under size the efi partition to 100mb not 260mb so this will also need to be resized later.
Then just redirect the recovery partition the installer creates at the end of the disk into the partition you created at the beginning of C.

Thanks again for all the help to bad disk genus didn't create a recovery partition windows would use it is an interesting app.

cereberus said:

This is exactly how I set up my drive 0. Like you, I only image backup 1st four partitions (3 hidden and C drive). The data partition is backed up separately.

IMO, this is the optimum layout unless you have a second data drive in which case, it is rather optional to have a data drive on drive 0.

I note the OPs layout is an mbr drive which is just asking for update troubled as Windows 11 is nominally designed for UEFI/GPT.

Click to expand...

Funny you should mention the data drive. On systems that have only a single physical drive, such as on many laptops, I used to sometimes create a Windows partition and a separate data partition. The reason was that when disk imaging I wanted to capture the OS drive but I have a huge data folder that does not need to get imaged (I have other backup methods for it), and I also don't need to backup my temporary VMs. The problem was that I always struggled with finding the optimal ratio of the Windows drive size vs the data drive size.

Then I discovered that there is a registry entry that you can use to tell VSS not to snapshot certain folders. As a result, I now just have one big C: drive but my images skip the data folder and my VMs. Life is good!

Open the registry editor and navigate to this location:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToSnapshot\

Add a new "Multi-String Value":

Value Name: Volume Shadow Copy Data
Value Data: C:\Virtual Machines\*.* /S

NOTE: In the above example I am excluding C:\Virtual Machines including all files and subfolders. Note too that you can add multiple entries, one entry per line. Also, do not enclose the path in quotes even if it has spaces in the name.

More details about this registry can be found in Microsoft's article : Excluding Files from Shadow Copies:

https://docs.microsoft.com/en-us/windows/win32/vss/excluding-files-from-shadow-copies

Hi,
It's official bitlocker update reused the new RE partition shows hair less than 750mb now instead of 16mb before the update lol
Now just to disable it reagentc /disableso I can use the boot menu instead of bios boot order to boot to winPE recovery media

Hi,
Think I should actually post the real process strings
Taking into account I already had a partition in front of C already way to big lol

I had to remove the Z letter again with free minitool diskpart did but it showed back up.

Hi,
Even better
I clean installed with a 2gb partition installed first then installed on the rest of the disk

After that use macrium reflect system image and it's winpe recovery media and it has a neat feature where you use that system image of a install and drag that C partition on top of the new installs C partition

Only thing to do after that is wait a little for the magic to happen and then lastly use startup repair using thew same winpe.
Keeping in mind this happened on a old mbr system and image onto a clean install gpt/ uefi install lol

Because of an error on my part resizing C to early and that broke the clean installs RE partition I had to use refresh install with new 23h2 iso

Only scripts I had to use in diskpart were these.
Results were just what I was loking for in the end though plus I got a fresh plate to mess windows up in my own special way
@Bree :cheers: for the help !

Just out of pure curiosity, why are you creating the RE partition before the Windows partition? There must be some reason I'm simply missing.

hsehestedt said:

Just out of pure curiosity, why are you creating the RE partition before the Windows partition? There must be some reason I'm simply missing.

Click to expand...

Hi,
Well I think I just said and showed why
This clean install was on a 2tb m.2 my other was 500gb so not so bad doing this stuff on 22h2 win-11 on my laptop was oddly easier than 23h2 on my z490 rig

MS throwing the RE at the end of it/1-2-4tb drives, I tried to install on a 400gb partition silly 23h2 installer threw all three partitions RE/ and both efi partitions at the end of C lol
Now I broke the RE just by resizing C down to 250gb to early this was my second attempt
I should of done the scripts you posted earlier but didn't know the RE would get broken resizing C

Now with that in mind
RE in front of C along with both efi's is very unlikely to be broken I mean ms has been installing the RE in front of C for decades
Only issue is they are way to small by today's standards by ms.
Now my RE's aren't to small and all is good I can do what ever I want with C and the rest of my disk without effecting RE at all.

Hope that is clear enough I also appreciate your help to

Hi,
Gone through all my rigs and they are all setup the same way now hehe
Sure guys and gals let MS tell you what's best for your disks

Wish I knew about using prior made system images "all MBR for myself" and drag and dropping the older C partition onto the new efi/ gpt clean installs C partition thus keeping all your ms and third party activated software in tact and replacing the MS sludge filled install quick and easily with macirum reflect winpe recovery media

Only preparation before the clean install is making sure the disk is GPT of course and creating a new 2gb primary partition to use after the clean install to be turned into the new larger RE partition.
Frankly the RE partition tools are pretty lame and I've never had any luck using them for any issues that came up besides making it go to safe mode.
Startup repair has never done anything but fail lol where as reflect winpe has never failed at any needed task
Setting it up this way insures I claim all my disk space without all being on C partition.

Plus ms will never have to create another RE in the future because frankly they are very easy to break by the user by simply adding another storage partition. between C and the RE which is the most lame disk design ever thought up by MS besides making the prior design RE way to small.
Last was my x99 system did this on win-10 and mounted 11 23h2 after
.