Windows Installation is a JOKE!

[hluz]

Ok. While you wait for IT, do this:

In a browser address line enter: http://wpad/wpad.dat

If your network configuration is standard you will get a file. Open with a text editor and check what is the address of the proxy used (including non standard ports). Refer to this if you need help: https://technet.microsoft.com/en-au/library/cc939951.aspx

After finding out what the proxy server address is, run the installer from the command prompt (not by double-clicking in file explorer), but before doing that set the HTTP_PROXY and HTTPS_PROXY variables as your environment requires (needing auth or not):

set http_proxy=http://your_proxy:your_port
set http_proxy=http://username:password@your_proxy:your_port
set https_proxy=https://your_proxy:your_port
set https_proxy=https://username:password@your_proxy:your_port

Then run installer from within the command prompt like explained here: https://superuser.com/questions/876933/running-exe-in-command-prompt

[tarunh]

Sadly, I agree with you. I’ve been trying to install Meteor on Windows 7 for 3 weeks, It fails for the during the first comand - Meteor create sampleappplication.

I’ve raised the issue here:
https://forums.meteor.com/t/unable-to-create-meteor-application-meteor-create-anything-gives-an-error/40073/2?source_topic_id=39997

Can someone please help me.

[funktional]

how can I edit those files then?

I tried to do this and I have no idea since my atom installed on windows cannot edit those files on the linux subsystem.

[Steve]

This is changing with Meteor 1.6.x. Not only will a 64-bit version of Meteor on Windows be supported, and the old installation process replaced, but a new Windows continuous integration environment is being setup and the full Meteor test suite is being adjusted to be Windows compliant.

Sounds great, @hwillson. Will that affect this?:

Issue: [Windows] ENOTEMPTY error when updating/reseting a project

[hwillson]

I haven’t had a chance to check yet @Steve, but I really hope so! We were able to close many other Windows related issues, so hopefully we can knock this one off shortly as well.

[abernix]

Please try the new Meteor Chocolatey installer. After installing Chocolatey, it should be possible to just run:

choco install meteor

The previous Windows installer definitely had some problems which the GUI installer made it very difficult to fix. In addition to the Meteor account login step failing for many users, the previous installer also failed to actually reinstall over an existing installation when it was re-run (without far too many manual steps).

The new Chocolatey installer is now maintained in its own repository where, in addition to being a better experience overall, we hope it will get the attention it deserves (outside contributors welcome, too!), instead of getting lumped into other issues. Hopefully, since it’s a simple bundle of PowerShell scripts, it will be substantially easier to fix any problems which do arise. For example, I’m already aware that it’s using using features which were introduced in PowerShell 3, therefore breaking for Windows 7 users who haven’t installed the PowerShell update, but the very fact that it’s a separate project and not a fancy GUI installer makes it so almost anyone in the community could make the appropriate changes to the language used in the script to fix that problem. (My bad, I wrote it!)

I’m going to lock this thread as the original post wasn’t very considerate of hard work that went into making the original installer work (even if it may have had problems), and really didn’t even provide us enough information to fix it. Talk about having our hands tied!

While I hope the new Chocolatey installer magically fixes the problem, if a problem still exists, I encourage new threads to be opened with a different tone which will hopefully shine a different light on the problem, and help us work toward a solution for both those afflicted and the community as a whole.

[abernix]

I should add for anyone who updates to the 64-bit meteor provided by the new Chocolatey installer via the above process, the experience should be better and hopefully faster! Keep in mind, as part of that upgrade process, we highly recommend removing the node_modules directory and running meteor reset, followed by a fresh meteor npm install to ensure that you’re using all the latest 64-bit builds of all binary modules in any app. (This is the same recommendation as anytime a major Node.js version is changed, or binary dependencies are changed.)