Partitioning, strange bug need help

[Kurt101]

Hi guys, i need help with this strange bug. It is involved around the GUID (gpt) disk style. When i delete partitions, they are not partitioning correctly, for example:

I delete my games partition, primary ntfs, 50gb. The partition does not become a logical partition (unallocated space) instead the partition is formatted and renamed unallocated, when in fact it has not become unallocated storage, and the partitioning space (50gb) is rendered useless and can never be used again (cannot create a new volume, cannot merge, can literally do nothing unless i use diskpart and clean the disk) I know these sentences are not too clear, however it is really hard to explain. Put simply. When you delete a partition, it is supposed to become a logical partition in which it can be reused to create volumes again, in my case, the partitions are not becoming logical, they are still physically on the disk, and with the now new blank partition, nothing can be done (resize, merge, create new etc.) This is strange as i am now using the mbr disk style in which this error does not occur. But i have tried gpt numerous times, and I KNOW FOR certain, that it always happens, that it is not just a one time thing. If you understand what i am saying (which your most likely do not, i cannot blame you) then please help me. Also another strange instance, is that the sleep on my computer does not work, i have tried countless times to get it too work and it never does, what happens is i try to turn the computer on and nothing happens, I have to press the reset button and then the computer goes back to the last session, for some reason the first time i load the computer after it is in sleep mode, the Ram is not loading, it only loads when i have to restart it for the second time. 

With kind regards- Kurt     Windows 10 pro   

[zMeul]

can you post a screenshot?

it sounds to me that you're dealing with extended partition, for some odd reason

[Kurt101]

5 minutes ago, zMeul said:

can you post a screenshot?

it sounds to me that you're dealing with extended partition, for some odd reason

one second, sorry just broke glass at the worst time, just cleaning it up

 

[Kurt101]

9 minutes ago, zMeul said:

can you post a screenshot?

it sounds to me that you're dealing with extended partition, for some odd reason

I cannot provide a screenshot as of now, sorry. Just imagine an ordinary partition, you delete it, it is still their exactly as before, just wiped and renamed unallocated. When i use minitool it saids that it is "gpt" where unallocated space should say "logical"

 

[zMeul]

2 minutes ago, Kurt101 said:

I cannot provide a screenshot as of now, sorry. Just imagine an ordinary partition, you delete it, it is still their exactly as before, just wiped and renamed unallocated. When i use minitool it saids that it is "gpt" where unallocated space should say "logical"

aren't you supposed to click apply for changes to take effect?

haven't worked with minitool, but other partition managers work this way

[theanimun]

have you tried using Windows Disk Manager yet?

[Kurt101]

Just now, zMeul said:

aren't you supposed to click apply for changes to take effect?

haven't worked with minitool

I use windows ms dos, i simply use minitool as it provides me with more information to which i can diagnose issues.

 

[theanimun]

Just now, Kurt101 said:

I use windows ms dos, i simply use minitool as it provides me with more information to which i can diagnose issues.

 

So your using MS DOS on an Operating System that doesnt have MS DOS in it at all?

 

23 minutes ago, Kurt101 said:

Windows 10 pro

 

[Kurt101]

Just now, theanimun said:

So your using MS DOS on an Operating System that doesnt have MS DOS in it at all?

 

 

I mean cmd (which is based on ms dos)

[theanimun]

Just now, Kurt101 said:

I mean cmd (which is based on ms dos)

if minitool partition wizard doesnt work, then use Windows Disk Manager to delete said partition, and that doesnt fix it, then your issue falls under a hardware issue

[Kurt101]

I have used cmd (diskpart) windows disk manager, linux grub everything, i have a ssd and a hdd, this issue occurs on both. If my knowledge is correct, then my motherboard is to blame? It cannot be my cpu, it cannot be the drives, i have 4x4 ram the chances of it being that are slim, the only thing that would cause it is a faulty motherboard? Please confirm

[theanimun]

if it were indeed the motherboard, the drives wouldn't be able to send or receive data. (i had a mobo die recently from exposed circuitry) and if it is the motherboard you will need to do a once over visually on the mother board to check if any of the circuits are visible, and you would notice a copper or gold

[Kurt101]

Just now, theanimun said:

if it were indeed the motherboard, the drives wouldn't be able to send or receive data. (i had a mobo die recently from exposed circuitry) and if it is the motherboard you will need to do a once over visually on the mother board to check if any of the circuits are visible, and you would notice a copper or gold

what else could it be? When my computer was shipped my computer supplier shipped me a faulty hard drive, anything could also be wrong, if im going to contact them i need to know what needs replacement. Please help with kind regards-Kurt

 

[theanimun]

you said it happens on both your SSD and Hard Drive right? you might need to do a refresh on windows 10 (minitool partition wizard uses windows diskpart command to do the basic functions, but the on top of that, adds additional functionality to it) and if its giving the error on windows disk manager, you could try a refresh to hope that fixes it