Extended C: drive in ESXi not extending

I just extended a C: drive from 40GB to 160GB with the VMware vCenter Converter Standalone and the disk keeps showing as 40GB.  However, in Windows Disk Management shows as 160GB (see pic). I already tried rescan, etc. Any ideas?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

In diskmanagement shring the disk by about 10MB. Windows usually wants a little free, unpartitioned space to properly reflect the partition's size.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
andyalderSaggar maker's framemakerCommented:
Use the extend filesystem command in diskpart, instructions are in the "more information" section of http://support.microsoft.com/kb/832316

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

IDMAAuthor Commented:
The shrink won't allow me to do it.  The Shrink button stays grayed out.

The virtual machine version I choose was 10.  Would that make a difference?
Maybe run a defrag as the image you posted suggests you to do.
andyalderSaggar maker's framemakerCommented:
You'd think MS would have built a re-check into the extend volume option of diskpart and the GUI so that if it failed like it has for you it would automatically re-do the extend filesystem for you. I wouldn't run a defrag until you extend the filesystem with diskpart.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Virtual Machine selection should not cause this issue, but I would recommend version 8.0, unless you need the features of v10.

To be honest, I would try again...
IDMAAuthor Commented:

This is my third try....

I did one a couple of months ago and it worked just fine. Hmmmm
andyalderSaggar maker's framemakerCommented:
You can always try allocating a bit more space with VMware then extending the partition again but the extend filesystem option normally fixes this problem. (you don't mention if you have tried it or not even though I have mentioned it twice).
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
You've done this three times, this conversion ?

and three times it's failed ?
IDMAAuthor Commented:

Third time's a charm, sir.
I followed the steps on the More Information section and now I have the extra space.

I must admit, I'm a bit disappointed on the Converter.
andyalderSaggar maker's framemakerCommented:
It's not a VMware problem, NTFS.SYS is to blame. It happens on physical Windows servers as well.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.