Um, that's by design. And it's been like that since the days of DOS. The command prompt remembers the current directory for each drive separately. So C: has a current directory, D: has a current directory, etc. CD only changes the current directory for that drive--it does not actually switch you to that drive. You need to issue a separate command to change to that drive.
Why maintain separate current directories for each drive? Because it can be useful: Code: :: assume you are somewhere in C: :: creates an empty file named foobar in the root of D: copy nul D:\foobar :: creates an empty file named foobar in the root of D: chdir D:\ copy nul D:foobar :: creates an empty file named foobar in D:\test chdir D:\test copy nul D:foobar :: if you have a lot of file operations, you can save a lot of typing this way :: old method: copy file1 D:\long\and\annoying\path move file2 D:\long\and\annoying\path del D:\long\and\annoying\path\file3 rename D:\long\and\annoying\path\file4 D:\long\and\annoying\path\file5 :: new method: cd D:\long\and\annoying\path copy file1 D: move file2 D: del D:file3 rename D:file4 D:file5
Well if someone finds an unexpected, never before used thing that somhow gets the Windows 8 h8er confused, Windows 8 gets blamed for it. In all seriousness this case of Windows 8 bashing prooves that ian82 never used a Commandline in Windows (or DOS) even before. This means he only USED the OS and never had any contact to the inner workings or deeper settings (cmd) of a Windows or DOS. An expert in h8ing Windows 8 but not in knowing! An Expert in h8ing Windows 8 but not knowing anything of realy using and do advanced things with computers in any way! The mainstream thinking of Windows 8 is driven by such people. Learn at least the realy low concepts of the commandline (Powershell would be very far away from your horizon of knowlage that I only mention it here in this bracets) before you say any bad things about Windows 8!
Thanks a lot man! that worked like a charm! I could've sworn I never had to do this in Windows 7 command prompt
The problem with our dear friend is that he doesn't know anything, yet he struts around like he's some kind of expert. Observe, for example, how he goes around telling everyone to install Intel's INF files (which aren't even drivers) to fix problems that aren't even related to drivers to begin with. He characterizes the Pro features in 8.1 as "bloat" without realizing that the system files for that "bloat" are always present regardless of whether one uses Pro or Core. And here, he comes across a long-standing feature of the Microsoft command line that he is unfamiliar with, but instead of spending a little time to research it, he gets out his megaphone and blames it on the new OS. And then when someone calls him out on this, he indignantly pulls out his favorite Castle gif as if it's such a scandal to suggest that he may be in the wrong. It's okay for someone to be ignorant--I have absolutely no problems with newbies asking for help or clarification. But it's bloody annoying when someone is ignorant but doesn't realize it, and subsequently goes around loudly spreading misconceptions and misinformation.