1. FILIBERTO SOSA
  2. PowerServer 2020 or older (Obsolete)
  3. Friday, 18 October 2024 19:42 PM UTC

We are still on PowerBuilder 2019R3 and PowerServer 2020 and our application was working fine.   We normally use kernel32.dll to access some windows functions.   Some of our users upgraded with the latest Windows 11 24H2 version and the application stopped working.  We went to the forums and they say that now, with the latest Windows 11 version, Microsoft prevents applications to run from inside the browser.   I went and removed those karnetl32.dll functions but we are still facing issues running our application on those machines.   I know that Appeon does not support PowerServer 2020 on Windows 11, but I would like to know if there is a workaround to fix this issue.

Thanks

Fili Sosa

Marco Meoni Accepted Answer Pending Moderation
  1. Wednesday, 27 November 2024 16:17 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Hello,

although the issue has this technical solution

https://www.appeon.com/developers/get-help/knowledgebase/4611

the reality is that companies are usually not collaborative.

They are reluctant or contrary to changing PC local policy.

This is because "...replace JScript by loading JScript9Legacy in place of Jscript..." sounds itself like a security leak.

Question now is whether 24H2 represents the actual shutdown of PS 2020.

Is Appeon going to distribute a PS 2020 update working with JScript instead of JScript9Legacy, therefore no changes to PC policies?

Thanks,

.m

Comment
  1. Kai Zhao @Appeon
  2. Thursday, 28 November 2024 01:52 AM UTC
Windows 11 is only officially supported in PowerServer 2022 and newer, and there is no plan to officially supported in PowerServer 2020. Since there is a risk that future Windows 11 update breaks this workaround, you should have plans to upgrade ASAP to PowerServer 2022 and newer.
  1. Helpful
There are no comments made yet.
FILIBERTO SOSA Accepted Answer Pending Moderation
  1. Thursday, 24 October 2024 18:18 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

We fixed the problem also in Windows 11 Home.

We found that we can also install the Group Policy Editor in that Edition of Windows 11.

The application is again fully functional.  Thanks a lot! 

Comment
  1. Kai Zhao @Appeon
  2. Friday, 25 October 2024 07:00 AM UTC
Glad to hear that, you can also set JScriptReplacement in the registry to use the old JavaScript engine referring to the resolutions below:

1. For single-user environment
Please add the following to [HKEY_CURRENT_USER\Software\Policies\Microsoft\Internet Explorer\Main]:
Value Name: JScriptReplacement
Value Type: REG_DWORD
Value Data: 0

2. For multi-user environment
Please add the following to both [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Internet Explorer\Main] and [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Policies\Microsoft\Internet Explorer\Main].
Value Name: JScriptReplacement
Value Type: REG_DWORD
Value Data: 0
  1. Helpful
There are no comments made yet.
FILIBERTO SOSA Accepted Answer Pending Moderation
  1. Thursday, 24 October 2024 17:56 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 3

Thank you very much Kai Zhao

This is a good solution for my PowerServer 2020 running on Windows 11 24H2

PowerServer 2020 application does not work well on Windows 11 24H2 | Appeon

However, the Group Policy Editor is only present in Windows 11 PRO Edition.

What about Windows 11 Home Edition?  Do you have any idea on how to work on these policies?

 

Comment
There are no comments made yet.
FILIBERTO SOSA Accepted Answer Pending Moderation
  1. Wednesday, 23 October 2024 23:18 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 4

Hi, this fix worked fine with Windows 11 22H2.

This week, we have a problem with the current release of Windows 11 24H2.  Our application is crashing.

As I have read, this Windows update has a lot to do with security.

For example, in our application we were able to access windows functions in libraries like kernel32.dll.

With this windows update, we are not longer allowed to use windows system libraries, and that is one of the reasons our application was crashing.

We will keep this post updated once we remove all access to windows system libraries to see if our application run fine again.

Thanks!

Comment
There are no comments made yet.
Kai Zhao @Appeon Accepted Answer Pending Moderation
  1. Monday, 21 October 2024 00:36 AM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 5

Hi Fili,

Please refer to the article below to solve it.
PowerServer 2020 application does not work well on Windows 11 24H2 | Appeon

Regards,
Kai

Comment
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Saturday, 19 October 2024 17:03 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 6
Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.