Quote Originally Posted by Megan2682 View Post
My question would then be, why does the CMD Prompt not like the work "my", which seems very strange considering the folders name is "my documents", and especially when the second folder was created by myself?
Starting with Windows Vista, the name "My Documents" was changed to "Documents". However, for backwards compatibility, the "My" prefix had to remain somehow. This would allow older programs that depended on this folder to find it.

If you type the following on a console you'll get a file not found message:
Code:
dir C:\Users\Megan\My Documents\
Whereas without the "My" prefix you do see your Documents folder contents. If you the go to Windows Explorer and navigate to that location, it shows the folder named as "My Documents". This I agree is confusing as hell. What is going on is that "My Documents" is in fact a Junction Point. An alias to the name Documents. Starting with Windows Vista, "My Documents" doesn't actually exist. It simply points to the actual folder named "Documents". Older applications can thus still function. So, from Windows Vista onwards, you should always use "Documents" instead of "My Documents".

So, what about the second folder, the "My Documents" you created yourself? Here's where you need to provide more information on how you actually created that folder. For all purposes, the name "My Documents" is a valid name. Both the windows console and explorer allow me to create "My Documents" inside the "Documents" folder. So what you are saying about the second folder doesn't make sense unless something else happened.