During our testing of PrePoMax, we noticed that when launching the main executable, the Publisher is shown as “Unknown.”
Our SCCM team was able to reproduce the same issue. Could you please check and advise why the publisher appears as “Unknown” when running the executable?
Your support will help us proceed with our internal deployment.
Most open-source software, including FreeCAD, has that warning from time to time on the first run (because signing the binaries is not so straightforward). It can be skipped (safely in this case if you downloaded the files from the PrePoMax homepage) by clicking “Run anyway” and then it won’t appear again. Of course, if you are still concerned about the security of these builds, you can easily compile PrePoMax yourself in Visual Studio, following the instruction on GitLab. I can help with that, if needed.
From what I know, the blue Microsoft Defender SmartScreen warnings (that can always be skipped) disappear once more users download and run the software, so it happens only with new versions for some time (maybe a few weeks) after their release. So if it happens for you with PrePoMax 2.5.0, keep in mind that it was released a few days ago and the warning should go away soon even for new users that haven’t skipped it yet.
they replicated your test case and the issue still occurs. The root cause appears to be that the Publisher is shown as “Unknown.”Also, per the packaging guideline, placing this package directly under *C:* (instead of C:\Program Files) would violate the rule: “No executables outside of %PROGRAMFILES%*.
Error : The error popup that appears when launching the main application. Can you help to fix this issue and release SCCM package for this.
Note: Previous chat , you told like these builds, you can easily compile PrePoMax yourself in Visual Studio, following the instruction on GitLab. I can help with that, if needed. Can we try this ?
PrePoMax should be installed in directories that don’t require admin rights (are not protected). Can’t you use such a folder ? This seems to be a blockade coming from your OS, not PrePoMax itself. I mean, the error message is generated by PrePoMax, but it only checks system access rights in the current installation directory.
It is usually so that if compiled PrePoMax does not work, the compiled version will also not work. Since PrePoMax is not installed on the PC, it starts without admin security credentials, so it must be in a folder where user credentials are sufficient to create and delete files.
My suggestion for the OP to compile themselves was for a different reason, but right - in the case of this new issue, simply changing the directory to a non-protected one or getting admin rights should be sufficient. I use the same directory on a laptop, but with admin account.