New
#1
Have you run a checkdisk to look for errors on the drive?
No need for the second window, it is reported to be 523GB at the top of the disk managment console.
Try shrinking and extending the partition again. You should get the right values back. (just use windows default settings when shrinking and extending)
When you tried making a partition, did you actually make a Virtual Hard Disk instead?
Also when you tried resizing, did you use 1. the wrongly reported C: in the top pane, or 2. the Partition listed in Disk 0 in the bottom pane. I would recommend trying it from 2.
Also please let us know how running "chkdsk /f" from and elevated command promp went, were there any errors?
didnt get any errors on check up and it dont matter which one i click one it wont let me shrink it or extended it , says same thing and extend is grayed out.
Hmmmm........mysterious.
I can only stab in the dark.
Try an sfc /scannow from an elevated prompt to see if you have any bad system files. If it corrects errors, run it again till it finds no errors.
Download the hard disk utilities available from your drive manufacturer and see if it passes those tests.
There is definitely something wrong with the control info on this drive - possibly in the MFT. You do not just loose nearly half a terabyte like this.
The problem is, that working on this C partition can result in total loss. It would therefore be imparitive to make an image of the partition before we get started. Do you have an external drive large enough to place all that data - seems to be like around 400GBs worth. If we can do that, then we could proceed.
ok that method did find errors but says its unable to fix them so im going to post the log here ,did it 3 times still same message so ye like i said heres log but will continue to give it a go to see if it finds more ''
click to see logs>>>>> logs sfc - 032e9d3b
There might be someone around here who can properly analyze that CBS log, but you should take WHS's advise and make an image of the drive or otherwise preserve its current state because it is obviously rocky for some reason.
At a minimum, I would copy any personal data files on it to another drive if you have not already done so.