Here's my problem:
Development environment: Windows10
Target environment: Windows 10 & Windows 11
When I want to distribute a finished B4J project, I have a stand-alone package created with the built-in B4J packager, zip the directory and I can distribute this zip file. Perfect.
If the programme was already installed on a Windows10 computer that was then updated to Windows11, there are no problems.
On a new computer with Windows11, the programme does not start or has a strange appearance and crashes.
When creating the package with the Packager, a small EXE file is created. I assume that this is some kind of wrapper that then prepares Windows for the JAVA application and starts the application.
Fix: If you search for compatibility problems via the context menu of this EXE file, some are found and fixed by Windows. After that, the programme runs without any problems. Has anyone ever had this problem?
Development environment: Windows10
Target environment: Windows 10 & Windows 11
When I want to distribute a finished B4J project, I have a stand-alone package created with the built-in B4J packager, zip the directory and I can distribute this zip file. Perfect.
If the programme was already installed on a Windows10 computer that was then updated to Windows11, there are no problems.
On a new computer with Windows11, the programme does not start or has a strange appearance and crashes.
When creating the package with the Packager, a small EXE file is created. I assume that this is some kind of wrapper that then prepares Windows for the JAVA application and starts the application.
Fix: If you search for compatibility problems via the context menu of this EXE file, some are found and fixed by Windows. After that, the programme runs without any problems. Has anyone ever had this problem?