Nothing created on Windows with `eos start`

[k-grube]

D:\>npm ls eos -g
C:\Users\kgrube\AppData\Roaming\npm
`-- eos@0.4.1

D:\>npm --version
3.10.5

D:\>node --version
v6.3.0

D:\>eos start test_eos
created test_eos/
created test_eos/frontend/
created test_eos/frontendindex/index.html
created test_eos/frontend/actions/
created test_eos/frontend/components/
created test_eos/frontend/components/root.jsx
created test_eos/frontend/components/app.jsx
created test_eos/frontend/components/router.jsx
created test_eos/frontend/middleware/
created test_eos/frontend/middleware/master_middleware.js
created test_eos/frontend/reducers/
created test_eos/frontend/reducers/root_reducer.js
created test_eos/frontend/store/
created test_eos/frontend/store/store.js
created test_eos/frontend/util/
created test_eos/frontend/index.jsx
Installing front end dependencies. This could take a few minutes...
Done
IF YOU USE NVM RUN THE FOLLOWING COMMANDS:
cd test_eos
npm install
Created Express Server
Installing server dependencies. This could take a few minutes...

D:\>dir test_eos
 Volume in drive D is DATA
 Volume Serial Number is 2ECC-2F76

 Directory of D:\test_eos

09/29/2016  08:33    <DIR>          .
09/29/2016  08:33    <DIR>          ..
               0 File(s)              0 bytes
               2 Dir(s)  394,897,055,744 bytes free

D:\>cd test_eos

D:\test_eos>npm install
npm WARN enoent ENOENT: no such file or directory, open 'D:\test_eos\package.jso
n'
npm WARN test_eos No description
npm WARN test_eos No repository field.
npm WARN test_eos No README data
npm WARN test_eos No license field.

[alexmattson]

This is good to know as all of our test machines are osx and linux. I will run windows through bootcamp and attempt to recreate and locate the problem.

[k-grube]

Oh, I should add, this occurs on Windows 8, Windows 8.1 and Windows 10. The command is launched from an administrative command prompt.