you had a terry moment then. again job well done gerry.
yes looks good, must admit though the first 15GB partition and the 36MB partition confuse me. both say 100% free. usually i'd expect a 15GB recovery partition to have at least 10GB of data on it and i'd expect the uefi partition to be 100MB even though i don't think it's used with windows 7 so is usually 100% free. not that it matters everything works fine and you now have plenty of free space for your os, and data partitions so well done. curios nigsy why you suggest he wants to consider moving whats on d to the external? surely the external would only be used for backups and it's looking pretty full anyway with only 17% remaining free out of 2TB.
my biggest worry when anyone makes changes to their partitions is the boot loader gets broken so the pc won't boot into recovery options or the operating system. what did you use in the end? can you post a screenshot of your partitions now too? i'm just curious if you still have any unused space on the drive.
did you read my post? if not see my post above and then tell us (screenshot would be best) what your pc shows. i'm beginning to think you have 1x2TB drive with c and d partitions on it. and 1x2TB external drive from what you posted above.
sorry gerry, tomk's post lists the options and advice we'd recommend and only thing we'd need to know first is if you have 2 separate hard drives in your pc, or if it's 1 that's been partitioned so it shows as 2 drives in windows, don't see where you've said in topic.
it's a permission problem then, windows knows it's a needed folder so probably has it tied down so only the hidden admin account can delete/make changes to it. don't have a windows pc and haven't set up virtualbox on this new install yet so i could install a windows os to test with yet or i would have done so already, also i've never used win10 and won't let it anywhere near my pc's even in virtualbox so it would be win 7 i tested with anyway. anyway back to original topic and poster, like nigsy my recommendation would be to clone the complete os drive to the larger drive and make that the boot drive as long as there is no files on there that haven't been backed up first.
coward. what you want to do is move the complete windows programs folder (and not 1 or 2 program folders inside it.) and see if things work, especially installing something new to see if it does follow the sym link and installs on the d drive when it thinks it's installed on the c drive. as everyone can see, me and y figured out why i was having smillie problems and now they work.
&amp;nbsp; &amp;nbsp; tomk's link explains it perfectly, "symbolic links" are needed and not short cuts but yes essentially that is the process. in linux you get the option to "copy, move or link" things instead of creating short cuts like in windows so the process of linking folders is straight forward, just move the folder and then link it back to where it was. now who's going to be brave enough to test if moving the windows programs folder and then sym linking it back again works? lol personally i use sym links all the time to save space on my os/home drive.
if you link the original folder after it's moved to it's original location then (if things work like in linux.) then you should have no problems because everything will follow the links to the actual programs/data needed to work. no idea why but i don't get any smilie icon or quote options when i make a post so no beers at the moment.
"The standard recommendation is that you should keep at least 50% of your hdd free to ensure that the drive operates smoothly" think you'll find that's 10 to 15% and not 50% caintry.
well done everyone. still a ways to go though before you equal the highest spot i remember our team getting to and that was 55th, so keep up the good work.
see if these links better help you trace and find out where the problem is when you lose your connection. eg.netsh command. https://technet.microsoft.com/en-us/magazine/ff625276.aspx http://www.windowsnetworking.com/articles-tutorials/windows-7/Network-Diagnostics-Tracing-Windows-7.html if you can't then find and fix the problem on your own, post any trace logs and errors in your next post so someone here may be better able to help you pinpoint where the problem is. .