good afternoon
i recently bought a used surface pro 5 used. reconditioned with a fresh install of windows 10 pro.
i wonted to shrink the c:/ portion, but didn't feel comfortable shrinking it with windows.
so i booted Debian 11 (cb++11) live usb opened gparted and resized c:/ saved it.
rebooted into window, i was surprised when windows didn't complain that something had changed and didn't run ckdis before going into windows. i then went in and looked at the the ssd nothing has changed ...

before i touched the ssd drive, from windows

after i used gparted on the same ssd from linux

back in windows after a reboot

booted straight from windows to live cd and gparted

so gparted wrote portion information some where, but windows is not using it?

i'v never seen this happen before, any help or direction would be greatly appreciated .

Attached Thumbnails

       

Since Windows is showing just 4 partitions on the disk, I suspect that the disk has both a valid MBR partition table and a GPT, and Windows is using the first of those. A disk with a GPT normally has a "protective" MBR with just a single partition of type 0xEE occupying the whole disk, or as much of the disk as an MBR partition can cover. If you didn't properly convert from MBR to GPT, you might end up with both partition tables appearing valid.

rknichols thanks for the reply.
i have never ran into this problem before.
gparted says it is a GPT portion table.
how can i tell exactly what is going on.

Dunno what's happening, but Win10 sees the EFI partition, so I'm guessing it thinks it's gpt.
In Win10 go to Computer management -> Device Management, then right-click Disc0 and pick properties. Then the volumes tab - post it.

I might add I have had Win10 trash gpt partition tables, but that was with the preview, before Win10 was officially released. Don't recall anything similar with more recent systems.

from my side it can be two different disks too. Or just two different partition tables.
I'm not really sure, but that "EFI system" is just the type of the partition, and probably can be seen using MBR too (but will not do anything useful in that case).

I do not know either so just throwing out some guesses. Windows by default hibernates when turned off so when restarted it may not of reread the modified partition table. Disable fast boot mode, shutdown, restart and see what happens. If you want to access the Windows drive from linux you need to disable fast boot mode anyway.

As a FYI as far as I know the Windows built in disk management utility is capable of resizing NTFS on the fly so no concerns but do not use it now.

i'm reading this morning.
thank you all for your suggestions.
after i read through and try to absorb this, i will post more info.
i think this link from thestarman might be more that i ever wonted to know about windows boot.


thestarman pcministry com asm mbr GPT

it would seem.....
that the 16mb partition is the problem!
and in less a complete reinstall i'm not going to be able to divide up c:/
https://www.diskpart.com/windows-10/...s-10-0825.html

i'm not giving up, but i don't see any way ahead with out a reinstall, these surface pro 5 do not use regular iso,
they have there own image.

I've never had any problems shrinking windows from within windows using diskmanagement.

Windows is probably shutting down in fastboot/hibernation mode, therefore gparted is not able to shrink the windows partition. Clicking on the yellow icons beside the windows paritions in gparted will provide additional informatiom.

I think doing a restart from within windows straight to the live usb will allow gparted to shrink the windows partition

or

Under windows advance power settings is where fastboot can be disable.

1 members found this post helpful.

out standing colorpurple21859
i went in and disable fast boot, rebooted and there were all the portions i set up with gparted.
i have spent many hours reading, more ms doc, web pages and nothing ever suggested disabling fast boot.