exe was not run in some of the win10 pro 64

[moricode]

i have compiled 3 apps in 32 bit exe and all run fine in win 7 /8.1 32 or 64 bit , and tested with win 10 , one of the exe can't run on some of the win10 pro pc , we have total 12 unit win10 pc

Detail:
compiler : pb 5.72 32bit, win 8.1 64bit, SQL server native client 12 ODBC driver ,
GUI : native GDI32 WinApi for Display and Printer output
No thirdparty / External DLL


software exe:

Workflow.exe , 32bit , , run fine on win 7/8 , most the time run fine in win 10 , but sometime it get killed when launch , re-launch and run fine
printBill.exe 32 bit , run fine on win 7/8 , run on 9 win 10 pro , not run in 3 win 10 pro , exe process was kill immediately when run
employee.exe 32bit , run fine


only win 10 pro 64 was giving problem so far , i has no idea what is the cause and how to solve it

[jacdelad]

It's a bit hard without any hint about the programs themselves...

[Kiffi]

Perhaps there are entries in the window event log?

[tua]

Most likely, there will be one or more good reasons for such intermittent, seemingly 'random' behaviour - it's almost never a bug in the language.
PB is not perfect, has known bugs, but I'd still rate it as very solid & reliable!

I would try this:

1) Make sure that everything is built with 'EnableExplicit' - if not, you're just asking for trouble
2) See if the problem goes away by building your exes with PB 6.10 - by far the easiest way out if it works
3) Win7? Win8? These have been unsupported since Jan2020/Jan2023 - ideally, these should be Win11, as even Win10 loses support in Oct. 2025
The more OS versions you run, the more potential for trouble...obviously
4) Check if the failing machines share some common characteristics, such as OS patch level and hardware/drivers that might give you a clue (graphics adapters are fairly often the culprits)
I once had Delphi exes failing only on machines that had a certain Canon printer driver installed!
5) if Kiffi's advice doesn't yield anything, insert your own logging code/debug statements at certain points to see how far your code gets before the program stops working. Turn on Warnings, Debugger, Purifier
6) Finally, you could also just install PB on a failing machine and run the code live there - might shed some light on things

Good luck - please report here what it was should you find it so we can all learn from it!

[RASHAD]

I think that the problem comes mostly from the target computer
It could be that the target computer lack some of the requirements of your software and you didn't made the right checks
Make the proper checks for the needed memory ,needed DLL's ...etc
Good luck
Note:
Windows 10 & 11 are now very strict so if you are running another outsider software (Using RunProgram() or any thing else) it will consider your software a virus or unwanted software and stop it

[moricode]

6) Finally, you could also just install PB on a failing machine and run the code live there - might shed some light on things

hi dude , thanks for this priceless hint.

luckily , one of the failing machine allow me to compile / test and run today , and this is the reason:

my app will enumerate installed printer and look for the epson matrix printer (multiple) and store to a list, and show the first printer on start up running,
the failing machine has no matrix printer installed , so it crash when look in 1st element in list .

solve :
i had add pre-check condition that if no item in list , will show "No Matrix Printer Installed" instead of Null ptr in list.


i mistake that couldn't imagine earlier there is different PC setup on site.

Thanks all master here.

[moricode]

but it is weird and strange that the OS doesn't show any msg box , alert or something , it feel like nothing happen when you run your apps ,
usually it will show a msg and ask you to contact Microsoft bla bla bla , but there just silent

[mk-soft]

As we do not know the code, we do not know whether you have carried out all the analyses.

- Many PB functions return a successful result.
- Handles and ID'S are declared as integers.
- Used *Pointers for memory pointers and checked.
- On memory request whether this was successful.
- Memory also properly released again.

[tua]

Awesome - glad I could help. That's another thing that I absolutely love about PB: You can install it on a machine and run your code there in less than 5 minutes!

The best troubleshooting I know of if you have such access to a failing PC.