Expanding Disk Issue

Ok-

I realize there are a lot of threads about folks having various issues with their expanding disk, but I haven't had luck finding a topic that addresses my particular issue.

I have a Win10 installation that started at 64gb. I bumped the size to 96gb as my usage got close to 50gb and I suffered the "typical" expanding disk issue where the added space was unallocated. I merged the unallocated space into C:\ & Windows successfully reported that it had 96gb total. However, as I got closer to 64gb, my disk usage claimed nearly 100% utilization (even though I now had 96gb total). I just re-expanded my disk to 112gb. Windows now believes I have 112gb total, but only shows 16% free (17.54gb). If I view the properties of all files & folders on C:\, they total 62.6gb (55.5gb on disk). Looking at the PVM, it is only 67.54gb.

My question: how do I get Parallels to properly expand to the full 112gb on my Mac and/or convince Windows that it has more space than it realizes. I've run chkdsk & everything appears fine. The issue that I currently have is that I'm using 64g on a 112g allocation but my Windows thinks I only have 17gb free.

Help!
Thanks.

 

Hi @DavidW5.

Please reproduce the issue seen in the screenshot, generate a Problem Report ID while the issue occurs (very important) and reply with the same.

 

Yeesh. I continued doing some disk management stuff & just expanded my disk to be large enough to handle the files I needed to work with despite the phantom disk usage. While trying to restore a database, the process failed (due to the supposed artificially low disk overhead), and so I bumped the disk again & then attempted to find the half-baked db file to delete it & restart the process. I ran windirstat (which is useful for quickly locating massive files buried deep in the Windows directory structure), yet none of the *.mdfs displayed. I went into SQL Server to find the path of another db & when browsing to the directory, I got an "elevated prompt required" message. *D'OH*. I re-ran windirstat in admin mode & voila: my missing storage showed up in the form of a number of "hidden" directories that got skipped in my space calculations because they required admin privileges to view.

tl;dr: there was no problem after all, I just miscalculated my usage by overlooking admin directories. That mistake was further compounded by the bad luck of the hidden files being roughly the same size as the original 64g->96g expansion.

Thanks for your quick turnaround, Hemnath!

 

You're welcome and I appreciate you for taking the time to share the above useful, insightful information. Please post again if you have any further queries on this subject.