Home
>
WinDev Forum
>
Topic
WD <-> Windows10 Client problem
Posted by Erik Schwarz
|
Erik Schwarz
WD <-> Windows10 Client problem October 17, 2018 11:38AM |
Hi,
Situation:
Windev application is on a Server in a Folder together with all dll's.
Client has full Access rights on that Folder.
App is started fom Client on Server (just a link to the exe on Server)
This works since years (at least since 2005) with all Operating System combinations that appeared.
On Client the customer changed to win10.
Now when starting the following message appears:
Invalid program file. Bad Information on external libraries.
The files are ok.
Starting the app on the Server directly -> ok.
Copying all files to Client -> ok (but no real Option, if there are a lot of clients)
Right clicking on the link and choosing 'test of compatibility mode' you will be asked to test the app -> the app works.
Then you can save this Settings, but the Problem stays with the next start.
Does anybody know, where to Change something to avoid that behaviour.
Seems to be a Problem with Windows 10 (it's today the second customer where it appears)
greetings
Erik
Situation:
Windev application is on a Server in a Folder together with all dll's.
Client has full Access rights on that Folder.
App is started fom Client on Server (just a link to the exe on Server)
This works since years (at least since 2005) with all Operating System combinations that appeared.
On Client the customer changed to win10.
Now when starting the following message appears:
Invalid program file. Bad Information on external libraries.
The files are ok.
Starting the app on the Server directly -> ok.
Copying all files to Client -> ok (but no real Option, if there are a lot of clients)
Right clicking on the link and choosing 'test of compatibility mode' you will be asked to test the app -> the app works.
Then you can save this Settings, but the Problem stays with the next start.
Does anybody know, where to Change something to avoid that behaviour.
Seems to be a Problem with Windows 10 (it's today the second customer where it appears)
greetings
Erik
|
Re: WD <-> Windows10 Client problem October 17, 2018 12:53PM |
Registered: 5 years ago Posts: 296 |
|
Re: WD <-> Windows10 Client problem October 17, 2018 02:52PM |
Registered: 5 years ago Posts: 38 |
Hi Erik,
take a look here (just use Google translate if you don't understand French):
[faq.pcsoft.fr]
Regards
Steven Sitas
[www.alpha360.biz]
take a look here (just use Google translate if you don't understand French):
[faq.pcsoft.fr]
Regards
Steven Sitas
[www.alpha360.biz]
|
Erik Schwarz
Re: WD <-> Windows10 Client problem October 21, 2018 10:35AM |
|
Re: WD <-> Windows10 Client problem October 23, 2018 09:51PM |
Registered: 5 years ago Posts: 2 |
In W10, 1803, Microsoft turned off some of the services that enable peer to peer networking. As I understand it, this was to close a hole that allowed a remote exploit. Unfortunately, fixing one problem caused another. To allow peer to peer file sharing to work as it has in the past the following 4 services need to be set to automatic:
Function Discovery Provider Host
Function Discovery Resource Publication
SSDP Discovery
UPnP Device Host
This needs to be done in addition to the normal Network and Sharing Center configuration that we have all done for years to enable peer to peer sharing. WARNING: Microsoft turned off these services to fix a problem. Enabling them will allow peer to peer sharing to work as expected, but it does reopen the hole that Microsoft was trying to close.
Function Discovery Provider Host
Function Discovery Resource Publication
SSDP Discovery
UPnP Device Host
This needs to be done in addition to the normal Network and Sharing Center configuration that we have all done for years to enable peer to peer sharing. WARNING: Microsoft turned off these services to fix a problem. Enabling them will allow peer to peer sharing to work as expected, but it does reopen the hole that Microsoft was trying to close.