ng new <appname> ... fails when not performed on c:\ drive

[Coderrob]

Bug Report or Feature Request

- [x] bug report

Command

- [x] new

Versions

node v10.7.0
npm v6.1.0
ng v7.0.4
Windows 10

Repro steps

1. Open command prompt
2. Change the disk to a drive other than c:\
   • e: for example
3. Enter ng new some-app
4. Enter Y to add Angular routing
5. Scroll down to SCSS and hit Enter

Output:

Mention any other details that might be useful

I have run through and uninstalled global angular/cli also verified cache afterwards. I installed it again even using @latest. I've installed 10.x and 8.x Node/NPM versions switching back and forth with nvm to no avail.

It seems that the Angular app will be created just fine on a C:\ but not any other disk. I verified permissions were correct, ran everything as administrator, and could not come up with any reasons why it would fail.

One interesting thing to note is when I ran the ng new <appname> on a non-c drive an empty folder named as the drive letter was created at the same directory level. I've reproduced it several times. Otherwise I've only been able to get the ng new to work on the C:\.

Drive letter folder created:

Working on C:\:

[alan-agius4]

Duplicate of #12670

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}