Yes, it's very enlightening to see that this issue has been known for about 11 years. It should have gotten fixed shortly after that.

InstallAware gave very little information on the specific cases where this vulnerability could be exploited. Is there any, except for that email titled "Critical InstallAware Vulnerability Mitigation" ? I'm asking, because in there there's no information at all about possible exploits. If...

X15, Build 3.22.2022.

I'll try to replicate it.

Currently there is no way to get the offending line (I'll try to forward such request). Thank you. We use madExcept for error reporting. It gives more detailed information including the call stack to the point where the error occurs. As first, you should check if you can verify the presence of an i...

Our normal single-exe-builds are created without problems.
While trying to to convert any of our projects to an MSIX build we get the following error message:

What needs to be changed to get rid of these parsing problems?

Our projects consists of several script files each.
A handfull of our customers get the attached error message during the installation.


Is it possible to add the offending line, not just its number?
Or is there a way, to find out what line it actually is?

Correct

As stated in the topic header - even twice, once on Friday right after downloading the setup file, then again yesterday. The latter one was 3 bits larger, so I thought it would be the right one now, but it wasn't. I even uninstalled and reinstalled the setup after each try. Update: I gave it a third...

Do you have any chance to send me a minimal project with the steps required to reproduce the issue? As I wrote: ...it doesn't happen with freshly created projects... Our projects are huge. They have grown over many years and versions. Without having a clue what could cause these folders to not get ...

After installing X15, the splash and the version info correctly show X15.
The new License file sets them back to X14.

I see. This is already a feature request: It's a bug, still unresolved since 15 years. Here is an article about the Decimal separator . All countries that use a comma as decimal seperator use a dot as thousand separator. We wouldn't be able to sell a single license of our software to American custo...

1+

I know this type of Windows errors message in the context of trying to write to a write protected directory, e.g. one that is under Ransomware Protection. It's very misleading and not suitable for this scenario, since it claims that it cannot find something at a certain place where it's actually sup...

I don't remember whether or not this was the case when I installed the very first release of X13.
Here, the current single file setup (30.01.00.2021) correctly displays X13.

Thank you, Francesco, the new single file setup installed correctly. Can you tell what happened? A corruption during download seems unlikely. The setup file itself would have thrown an error message but it run through as it always does. Therefore I think even an md5 hadn't been useful in this case. ...