WDAC Compatibility Issue with PrimalSQL 2024

[systeembeheer]

I installed PrimalSQL on new computer to verify this and have not found any .dll files being generated in a folder such as you indicate. Not on startup, nor when establishing a database connection. According to the development team, there is no such functionality within the product. Our guess was that maybe this is something a database driver might do, but according to your last post you do not even get that far.
That is a little suspicious to say the least.
So the first question is, did you download the product actually from our site and verify the digital signature on the installer?
Secondly, we really need you to zip up these dll files and upload them for further investigation.

Hi Alexander.

I downloaded the install file from the Sapien website en checked the digital signature.

The DLL files seams only be visible when they are blocked, like by WDAC.
Maybe if it is working they are automatic removed by the software.

I uploaded the DLL file and the error screenshot to the SAPIEN Support Uploads

Have you also done the test with WDAC and Dynamic Code Security enabled?
Because if we Disable "Dynamic Code Security" it is working.
(This is not what we want for security reasons because we disble this for all Apps on the computer)

If you need anymore information please let us know.

Thanks in advance for your assistance.

[brittneyr]

Do you have any issues with our other software? Can you please test this if you do not know with PowerShell Studio?

[Alexander Riedel]

The dll in question is found to be generated by the Microsoft JIT (Just-in-time) compiler. It is a part of the .NET architecture that compiles a .NET (C# in this case) application into binary code on the target machine when run.
So in essence Microsoft is here using its right hand to slap the wrist of its left hand.
Unfortunately there is nothing we can do about that and it appears to be a quite common issue with WDAC.
I can only recommend to contact Microsoft in that matter.

[systeembeheer]

The dll in question is found to be generated by the Microsoft JIT (Just-in-time) compiler. It is a part of the .NET architecture that compiles a .NET (C# in this case) application into binary code on the target machine when run.
So in essence Microsoft is here using its right hand to slap the wrist of its left hand.
Unfortunately there is nothing we can do about that and it appears to be a quite common issue with WDAC.
I can only recommend to contact Microsoft in that matter.

Thanks for your response.

It seems to me that the PrimalSQL software addresses the .NET architecture and can also adjust how .NET responds.
You speak of a .NET (C# in this case) application, but it seems to me that PrimalSQL is that .NET application, because otherwise this issue would not exist.
If the opinion is that it is with Microsoft, you could check with Microsoft why the PrimalSQL as a .NET application cannot handle WDAC. You can also give Microsoft the correct information about the application.

Thanks in advance

[Alexander Riedel]

We have no affiliation with Microsoft, so we have no channel to use really. We have no influence over how the .NET framework works nor do we have any influence over WDAC. Microsoft does not need any application details from us, the issue is well known it appears from what we can tell. Maybe I did not express this correctly, but this is not a problem isolated to PrimalSQL. Virtually any .NET application, and there are thousands, will face this issue when WDAC is enabled as it is in your case. There is literally no chance that the Visual Studio or the .NET team will change how the JIT compiler works. That would be a major undertaking I am sure.

The WDAC team, whoever they are, is much more likely to add or already have a way to avoid this particular problem. Since you are using WDAC and not us, we would have no way of testing any remedy they might offer.