Windows 10: Issues with 64bit software

Ever since i've upgraded to windows 10 (fresh install), I've had issues with running 64 bit versions of software. I'm not sure i can describe the problem accurately, but it's internet/network related. When using git, it will not relsolve hostnames or ip addresses (and i'm pretty sure you don't relsolve ip addresses, but that's the error it gives). Can use the ping command from git fine, just can't clone, push or pull. When using VLC, i can't stream videos from youtube, it comes up with an error saying the input cannot be opened. When running java applications if i use the 64 bit environment, i can't connect to anything that requires authentication (such as online minecraft servers, can connect to servers running in offline mode just fine though). I only run into these problems when using the 64bit versions of the applications, the 32bit versions work just fine. Has anyone encountered something like this before, and can point me in the right direction?

Just to add a little more info, the 64 bit versions worked just fine on windows 7 and 8.1. - which is what peeves me off the most.

EDIT: The only things i can think of, is that it there is a problem with using MinGW-w64 to compile binaries to be used on windows 10, or it's a problem with windows 10

:)

 

What is the difference between the two program folders on my C drive: C:/Programs and C:/Programs(86)?

Hi Lewis,

If you are seeing both these folders, you are running the 64bit version of Windows

Windows 64bit can run both 64bit and 32bit software.

64bit software is installed into C:\Program Files

32bit software is installed into C:\Program Files (x86)

The installer for your software will automatically decide which folder it will install into, you do not and should not change the default installation folder manually . . .

 

32bit or 64bit

Windows 10 64bit you can load 32bit and 64bit applications

Windows 10 32bit cannot run 64bit software, therefore you cannot run apps like QuarkXpress that only come in 64bit versions

64bit Windows can address in theory 16.8 million terabytes

32bit Windows can only address 4GB of which 3.12GB may only be usable depending on the version of Windows you are running

In theory 64bit is much faster than 32bit as a 64bit data word (64 1's and 0's) is processed at each cycle of your processor instead of a 32bit data word. I say in theory as there is

A lot of modern software is now optimised to run on a 64bit processor, therefore will run faster, it took a long time for software manufacturers to re-configure their software to take advantage of 64bit

Basically, if you have the option of running either 63bit or 32bit, you have nothing to lose and everything to gain by choosing the 64bit version . . .

 

Well, I'd never tried streaming media from a URL through a player like that.. but I agree, none of vlc player, winamp or zoom player succeeds in playing from youtube. And I'm using the 32 bit version of vlc player v2.2.1 on Win 10 Pro x64.

 

I think your problem is with the network/firewall settings. I use VLC 2.22 X64 and can stream from youtube: TAYLOR vs. TREADMILL - YouTube
You can try to download the new 64 bit version 2.2.2: VideoLAN - Downloads
It's an installer but actually you can just unzip it with 7-zip to your desktop and run from there

 

If only the issue was that simple. Just tried using VLC 2.2.2 X64, but i still have the same issues.



I'm pretty sure it's not a firewall issue.
I've turned off windows firewalls temporarily in the past to test this.

 

Open admin command. Copy and paste the line below, run to make sure no corrupted Windows files. (Will take a while to run):
Dism.exe /online /Cleanup-Image /StartComponentCleanup&dism /online /cleanup-image /restorehealth&sfc /scannow&pause

 

For those who come here looking for a solution, I never found a reasonable one. A more detailed diagnostic of the problem was that the 64 bit software i was trying to use could not see outside my local network ( this included VLC, Java (JRE and JDK), Git, and WaterFox). The most likely cause of the problem is an error in registry i would think. I ended up re-installing my OS (with a more recent image), and magically my problems were gone.