Windows 10 single disk resizable, stuck on BIOS screen after process

[banana123]

@george1421 I am not sure how to fix this partition layout in its current state, since If I delete the recovery partition it won’t be adjacent to extend with my data partition. I looked into some freeware partition tools but it didn’t seem to cover what I need to do.

I am a bit confused though, since I am seeing other w10 GPT disks with Recovery being on partition 1

Is my best course of action here just starting a new w10 image?

[banana123]

@banana123

I installed a fresh W10 and compared the log files and how it handled this partition. I changed the flags on the recovery partition so it matched. I ran these on the Recovery partition from diskpart to get it back to normal. Went to do a resize capture, saw it not resize in log file, but still got stuck on Dell Logo http://prntscr.com/qu632u

set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001

label: gpt
label-id: E3756D2D-6EEC-459F-BFA3-B0DCB3D4891D
device: /dev/nvme0n1
unit: sectors
first-lba: 34
last-lba: 500118158

/dev/nvme0n1p1 : start=        2048, size=     1083392, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=C0E109E0-E41D-47CB-8798-38C184966E0C, name="Basic data partition", attrs="RequiredPartition GUID:63"
/dev/nvme0n1p2 : start=     1085440, size=      204800, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=D8942D98-D71D-4348-8909-A6BC265A8BBB, name="EFI system partition", attrs="GUID:63"
/dev/nvme0n1p3 : start=     1290240, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=E9F36812-1E24-4028-873E-83C84B42E9DE, name="Microsoft reserved partition", attrs="GUID:63"
/dev/nvme0n1p4 : start=     1323008, size=   498794496, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=C0AECA45-A5CD-4B3C-AB8A-F3102F545114, name="Basic data partition"

label: gpt
label-id: E3756D2D-6EEC-459F-BFA3-B0DCB3D4891D
device: /dev/nvme0n1
unit: sectors
first-lba: 34
last-lba: 500118158

/dev/nvme0n1p1 : start=        2048, size=     1083392, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=B4F54B55-07DE-41E0-932A-9FEC86A30A65, name="Basic data partition", attrs="RequiredPartition GUID:63"
/dev/nvme0n1p2 : start=     1085440, size=      202752, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=B7155540-CEA7-4F35-BDDB-E3CEF4D40130, name="EFI system partition"
/dev/nvme0n1p3 : start=     1288192, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=FA93F7E5-982E-476F-93D1-8DBC9E9E6ABC, name="Microsoft reserved partition"
/dev/nvme0n1p4 : start=     1320960, size=    59195110, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=AD6ABD0C-959A-491C-A9A5-FDDD31822B65, name="Basic data partition"

[Sebastian Roth]

@banana123 said in Windows 10 single disk resizable, stuck on BIOS screen after process:

Went to do a resize capture, saw it not resize in log file, but still got stuck on Dell Logo

We might need to look into that state a bit more. Any chance you can get some more information on what happens at this point? Does is wait or freeze? Caps lock, Num lock still working? Maybe disable fast boot in the UEFI setup to hopefully get some more hints on what the issue is?!

While this partition layout might now be standard (George you are absolutely right) I still don’t have a clue why you can capture and deploy as non-resizable but it seems to be doomed when capturing as resizable.

[banana123]

@Sebastian-Roth just stuck at Dell logo. I can press caps lock to toggle, I can alt + ctrl + del. If I try to quickly boot into an F Key, it will show a bar but get stuck at 30%. Fast boot set at minimal… .

[george1421]

@banana123 As a point of data collection, how did this disk get created in this state? This is not how the M$ installer creates the disk layout.

Through MDT its efi, c drive 99% of free, recovery partition 100% of free space.

Someone/thing had to create this format structure intentionally.

[Quazz]

@banana123 I agree with George.

The type matches a normal Windows first partition, but it appears to have been heavily modified afterwards to be “recovery”.

And it seems your second partition is now getting resized for whatever reason…

If you don’t need the recovery partition it seems best to just start over.

[banana123]

Not sure what happened, I originally created the image on another physical machine.
I am going to restart with a new image.

Thanks all

[dclark]

@banana123 Did the new image fix the issue for you? I am having the same issue with the Latitude 3400 model. If it did what changes did you make? Ours was working and then I updated the image with the latest Windows updates and a couple of testing apps needed by the users and now the 3400 exhibits the same behavior as you describe. All other models here are working fine with the latest image. (Windows 10)

[Sebastian Roth]

@dclark I kind of doubt you are having the exact same issue. While it might look the same at first I am fairly sure your partition layout is differnt and that is playing a big role in this case. Please open a new topic and post all your details so we can help properly: FOG version, Linux OS version, image type (resize or not), contents of d1.partitions, d1.minimum.partitions and d1.fixed_size_partitions…

[banana123]

@dclark I ended up just redoing my image for my Latitude 3500s with a clean install of latest W10 from USB. I gave up trying to fix the partitions/issue.

No issue with new image and deployed a bunch so far (single disk resizable)