C drive seems abnormally large for the deployment (.WIM taking up all the space)

Question

I just started using SCCM 2012 R2.  I've gotten everything setup to do my deployment but it turns out I clicked deploy on a .wim file I had and it filled up the C drive.  This is a virtual machine and I never intended to store the data on the C:\
drive.  But by following a install online it seems that the default DP puts it there.  My SCCMContentLib seems to grow uncontrollably and I can't figure out why.  At first I started with a 40GB vm.  Then moved it up to 60 to give me 20GB
of free space.  Next I noticed that my image wasn't getting sent via the client pc because of a error which tracked back to the operating system status being red.  This tracked to not enough space on the C:\ when I clicked the error.  I noticed
somehow this WIM file took up the 20GB I had given it extra.
My image is for a Dell Optiplex 3020.  The .wim file is 9GB in size on the file share.  Yet when I right click and check the properties under Operating System Images it shows as 22,083.82MB.  Which doesn't seem all that confusing understanding
that this is probably the extracted size?
So no problem I increased the drive size by 40GB again.  I then went to the operating system and right clicked and said distribute content.  But it didn't seem to turn yellow.  So I went to Task Sequences, Distribute content on the task sequence
that is set to push out that image, then went back to the OS and clicked distribute again.  This time it went Yellow.  I waited and waited then it failed out again.
Now when I check the C:\ drive it has 4GB or so free, and the status is red again with the error not enough space on the C:\ NTFS drive.  I have no idea how a 9GB .wim file can turn into 60GB of space eaten up?  What am I not understanding about
SCCM.  Just using WDS seemed like a much better solution as it didn't require a insane amount of space to push a single image.  I understand that SCCM has many other capabilities which is why I moved to it.  Yet this is not a acceptable solution
using up 60+GB for a single 10GB wim file to image a few machines.
There must be something wrong here and I am not doing correctly.

Answer 1

To answer the questions thus far.  I originally used WDS and the other program which escapes me MDT? I think to create the wim files on the old server.  In the file share there is the .wim and a language.ini file which WDS and MDT created when
making those images.  I just moved them to the new file share which has plenty of space.  This .wim file is a little over 9GB in size on the file share.
I right clicked the OS file and clicked Distribute, I didn't click deploy.  I then boot PXE on the computer and it runs the task sequence.  I had several images which failed to distribute due to file space.  I removed the content by going
to the DP and in the Content tab and clicked on each image and clicked remove.  It stated that it would remove the data for those but would not remove any data linked to other deployments I believe.
I deleted the OS as you said and it cleared up 60GB of space.  The next issue is I had to delete the task sequence as I could not longer find a place to edit which WIM it used.  Not sure if this is standard or if there is a place to edit this after
the fact when we have a issue such as this?
I wanted to next look into moving the software library to my file share if possible.  I see I can create a mapped drive and for example make it E:\.  I have read that you can use the Config Manager 2012 R2 Tools to move this.  However it looks
like it moves MUCH more than just the SCCMSoftwarelib folder.  I have read it required or maybe recommended that you keep the software lib and other folders on the base drive with NTFS.  Curious if mapping a share and moving all the files to the
file server I created to store the .wim files is recommended here and possible?