Exe won't run on Windows 10

[ts-soft]

And Driver on 64-Bit OS have to use 64-Bit only!
Driver on 32-Bit OS have to use 32-Bit only!

[Falko]

https://msdn.microsoft.com/de-de/librar ... 85%29.aspx
https://msdn.microsoft.com/de-de/librar ... 85%29.aspx

okay??

[Dude]

Hang on: none of this makes sense. I've always read that a 32-bit exe will run on both 32-bit OSes and 64-bit, due to 32-bit emulation on 64-bit. Therefore, I've always coded with 5.31 32-bit PureBasic on my 64-bit Windows 7 OS. When I build an exe that way, it's always run fine on 32-bit Windows XP, and also always run fine on 64-bit Windows 7.

But now, that same exe won't run on Windows 10. Why not?

[Bisonte]

Not the *.exe is the problem. It's the *.dll

You don't have to mix x86 and x64....

[heartbone]

I'm using PureBasic 5.31, 32-bit, on a 64-bit PC running Windows 7 Ultimate. When I build an exe and send it to a friend running Windows 10, 64-bit, the exe throws up this error. Any suggestions on how to resolve this? Thank you.

I believe I answered your original question, perfectly.

Hang on: none of this makes sense. I've always read that a 32-bit exe will run on both 32-bit OSes and 64-bit, due to 32-bit emulation on 64-bit. Therefore, I've always coded with 5.31 32-bit PureBasic on my 64-bit Windows 7 OS. When I build an exe that way, it's always run fine on 32-bit Windows XP, and also always run fine on 64-bit Windows 7.

But now, that same exe won't run on Windows 10. Why not?

But now what you are asking is way out of my league.
Good luck.

[DontTalkToMe]

Both the factions here need an interpreter, and you a pair of glasses.

You are telling you compiled a 32 bit exe which is not running on your friend computer, on Win 10.

The others (excluding myself) saw a 64 bit DLL and are talking as if you were calling it from your 32 bit exe.

The points here are:

It's not working on your friend's Win 10, not on Win 10 in general.

The 64 bit DLL is from nVidia's Geforce Experience and it's trying to start not because your program is invoking it.

Does your program use OpenScreen() ?

In any case as is said before, based on what you told us (so almost nothing) the problem is probably a corrupted or bugged Geforce Experience installation of your friend computer.

He can fix it, remove it, upgrade it or try to disable some of the nVidia services while trying your exe to see which one is responsible, or google about the message in the messagebox and try the suggested fixes.

[Dude]

Does your program use OpenScreen() ?

No, but it does create a fullscreen window that copies another window's image with bitblt. I emailed my friend and told him to try reinstalling or updating GeForce Experience. Thanks to everyone that replied.

[Danilo]

It's very unlikely that 'system32' contains a 64-bit DLL. It's just a file name, and it seems it has to do
with Nvidia Audio stuff. Actually the file is missing, so why do some people think you try to call a 64-bit DLL?

[DontTalkToMe]

and it seems it has to do with Nvidia Audio stuff

nvspcap64.dll ==> NVidiaShadowPlayCAPture

See ShadowPlay

Currently all the nVidia Geforce Experience software (bundled with the driver) is crapware, it's the thirst thing I deselect when installing a nVidia driver. Unless you desperately need it and you can't replace it with comparable software, my suggestion is to avoid it.

[PureGuy]

There are two dll's on my Windows 7 x64.

nvspcap.dll (in \Windows\SysWow64)
nvspcap64.dll (in \Windows\System32)

If he want's to compile his program as x86, than he should load the first one.

[DontTalkToMe]

:-O

[jack]

perhaps it's already mentioned, on 64-bit windows the 64-bit dll's are stored in windows/system32 and the 32-bit dll's are stored in Syswow64