Customized image of Windows10 1803 RS4, partition resize issue

[Rayco]

Hello mates.

I have worked correctly with windows images without recovery partition, but now, for production reasons I have to make a new image with recovery partition.

I am working with Express Deployment Tool and it automatically generates the partition for me.

The problem that I have, is that when configuring the template as a single disk rezisable does not expand all the gigabytes.

For example, when I deploy to 240Gb SSD, it gives me an unpartitioned 3.4Gb, with no partition at the end of the disk.

If I do it on a 1Tb HDD, it leaves me at the end of the disk without partitioning, almost 34Gb.

As I mention, in other versions without the recovery partition at the end it worked correctly. Before creating the image I have also changed the partitions of place, putting the partition of recovery ahead of the system and it has worked, but the function of restoring the computer fails.

Has anyone had any similar problem with the hard disk regain?

Running Version 1.3.5
SVN Revision: 6067

[Rayco]

For more details, I attached some SS.

Template image:

Source master image in ssd 30Gb:

Deployed to HDD 1Tb:

I tryed to swap system partition with recovery, with the same issue, deployed:

[Sebastian Roth]

@Rayco Can you please post the contents of d1.fixed_size_partitions, d1.minimum.partitions and d1.partitions which you find in the image directory on your FOG server (/images/Win10ProfeQi1803/...).

[Rayco]

@sebastian-roth Thanks for response.

d1.fixed_size_partitions

:1:2:4

d1.minimum.partitions

label: gpt
label-id: FAD8F34F-08FC-4068-8435-9AFFAAA13980
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 60460795

/dev/sda1 : start=        2048, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=CFDA3487-867C-48F9-8177-810EF4EB6F0C, name="EFI system partition", attrs="GUID:63"
/dev/sda2 : start=      206848, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=24E9E9B1-D1A8-4FED-818C-60FF804F64E7, name="Microsoft reserved partition", attrs="GUID:63"
/dev/sda3 : start=      239616, size=    27075584, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=7359A249-2F8A-42E8-AFDB-48FD43250DC5, name="Basic data partition"
/dev/sda4 : start=    58615808, size=     1843200, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=68BF7C08-141B-4607-BC65-A537B0ECDC5E, name="Basic data partition", attrs="RequiredPartition GUID:63"

d1.partitions

label: gpt
label-id: FAD8F34F-08FC-4068-8435-9AFFAAA13980
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 60460795

/dev/sda1 : start=        2048, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=CFDA3487-867C-48F9-8177-810EF4EB6F0C, name="EFI system partition", attrs="GUID:63"
/dev/sda2 : start=      206848, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=24E9E9B1-D1A8-4FED-818C-60FF804F64E7, name="Microsoft reserved partition", attrs="GUID:63"
/dev/sda3 : start=      239616, size=    58376192, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=7359A249-2F8A-42E8-AFDB-48FD43250DC5, name="Basic data partition"
/dev/sda4 : start=    58615808, size=     1843200, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=68BF7C08-141B-4607-BC65-A537B0ECDC5E, name="Basic data partition", attrs="RequiredPartition GUID:63"

[Quazz]

That’s strange, it claims there’s a 4th partition, but I don’t see it in your disk management screenshot.

[Rayco]

@quazz I deployed on a 500gb hard drive in search of patterns, with the same result.

[Quazz]

@rayco Yes, but FOG records the partitions from the source system, which only has 3 partitions, so I don’t know why it thinks there are 4?

Are you 100% sure this is the correct image? When was it last captured?

[Rayco]

@quazz The weekend I deleted all images I had created in 1803, and today to pass you the logs of the partitions I did the whole process of capture and deploy again.

Could it be because the recovery partition is hidden?

[Sebastian Roth]

@rayco Ok, let me try to interpret your partition table:

sda1 - type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B: EFI boot partition, size matches the 100 MB seen in disk management picture
sda2 - type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE: Microsoft Reserved Partition, only about 32 kilobytes in size. Not sure but partition flags might hide this one from disk management.
sda3 - type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7: That’s your windows system partition. This is the only partition FOG is able and willing to resize.
sda4 - type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC: Windows Recovery Environment partition. This partition is hindering FOG from expanding your main system partition as it cannot move the start of this one without breaking the recovery option.

[Rayco]

@sebastian-roth correctly, I’m sure the problem is recovery partition.

I’m traying diferents methods but with unlucky results.

[Sebastian Roth]

@rayco said in Customized image of Windows10 1803 RS4, partition resize issue:

I’m traying diferents methods but with unlucky results.

What exactly have you tried and which errors occurred? We can’t help without knowing more details from you.

[Rayco]

@sebastian-roth I have changed the partition part of recovery using partedmagic, placing the recovery before the partition of the system, with an identical result, but with great detail, once the deploy is done I can extend the partition of the system from within the windows itself, using the graphic environment in disk manager, extend partition. But the recovery stops working. I understand that this happens because the partition is not where the system points.

I am thinking that an easy solution would be to find in the bowels of Microsoft EDT the way in which it creates the partitions automatically and force it to place the partition originally before the one of the system.

[Rayco]

Finally, I had to reinstall FOG and everything was fixed.

Thanks guys for the answers.