SENSO error

[Sylv3r]

Has anybody come across this over the last couple of days where when attempting to open Office documents a SENSO error appears on screen about SensoH64.dll not designed to be run on Windows. If you click OK - it continues to load fine.

 

We've seen this on a number of schools across our trust but not in huge numbers so it's not impacting everybody.

 

SENSO support have identified an issue with Windows 24H2 but these devices all appear to be on 22H2 that we have seen so far. Senso are recomemnding disabling Application Inspection but isn't that a fundamental part of the solution we are paying for?

 

Thanks

 

Andrew

[Oaktech]

No errors across my 3 schools that are using it.

[happydave]

I've seen this a few times for one site using senso, and once in another using impero so far.

 

Do you have a link to senso's acknowledgement of this? It would be handy to track the issue.

[Sylv3r]

I've seen this a few times for one site using senso, and once in another using impero so far.

 

Do you have a link to senso's acknowledgement of this? It would be handy to track the issue.

 

I don't have anything in writing - it was just what a member of the team had told me after speaking to someone over the phone I think.

[Quinn]

I have this exact issue with one teacher surface pro 9. Did you manage to get to the bottom of it? I've reinstalled the application multiple times. Edited March 6, 2025 by Quinn

[Quinn]

UPDATE, just got a reply from Senso as they are still working on it.

 

"In December, Windows introduced Ai.exe, which is causing a DLL error with the SensoH driver; we are investigating this and can see it is impacting some other third parties as well.

 

Disabling application logging resolves the issue temporarily and will only affect devices where application logging is enabled."

[CHiLL]

"ai.exe - bad image" also affected Impero and they said it was because it hooks into every running DLL, which caused issues with this updated executable with Microsoft. Their temporary solution was to add "ai.exe" into their injection exclusion list within the Impero server and that stopped the issue straight away. I don't know if this is how Senso works or if they have a similar solution.

[toffee_paul]

@CHiLL Did Impero ever fix this, do you know?

[CHiLL]

On 11/06/2026 at 16:31, toffee_paul said:

@CHiLL Did Impero ever fix this, do you know?

This was a Senso error, not Impero. Adding ai.exe into the injection exclusion list fixed it and I've not had the issues since. Whether it's been fixed on their end and this fix is no longer required, I don't know.

[toffee_paul]

@CHiLL Sorry I meant to say did Senso ever fix it, not Impero.  We use Impero and adding ai.exe into the injection exclusion list didn't resolve it for us.  We are on v8.6.32 which isn't the latest so it may be a newer version fixed this. The changelog doesn't seem to mention it though. Looking at Senso as a potential Impero replacement, are you happy with it?

[CHiLL]

3 minutes ago, toffee_paul said:

@CHiLL Sorry I meant to say did Senso ever fix it, not Impero.  We use Impero and adding ai.exe into the injection exclusion list didn't resolve it for us.  We are on v8.6.32 which isn't the latest so it may be a newer version fixed this. The changelog doesn't seem to mention it though. Looking at Senso as a potential Impero replacement, are you happy with it?

To be honest, since this is a primary we don't use it that often. It ticks most of the boxes. In my secondary, we still use Impero with an on-site server as the cloud versions are just not as good as the on-prem version. WOL is hit and miss and clients will often appear offline In Senso despite they are online, whereas it's much more reliable in the on-prem Impero. If prices were comparable and I was only dealing with on-prem devices (not remote devices), I'd probably stick with Impero.

[OLPTech]

Try injection excluding aimgr.exe as well as ai.exe that's what we have and haven't seen that error message since.

We had a mixture of Senso, Netsupport School/DNA and  Impero at our sites but moved them all over to Impero in the end as it worked better for us and was more reliable.

 

Mixture of primary and secondaries

 

Thanks

[Boredguy]

20 minutes ago, toffee_paul said:

@CHiLL Sorry I meant to say did Senso ever fix it, not Impero.  We use Impero and adding ai.exe into the injection exclusion list didn't resolve it for us.  We are on v8.6.32 which isn't the latest so it may be a newer version fixed this. The changelog doesn't seem to mention it though. Looking at Senso as a potential Impero replacement, are you happy with it?

Try adding the offending file that Impero warning message brings up to the injection exclusion list on your server.
We had to do this for Excel last summer cause the ai.exe was complaining whenever Excel was launched on certain devices... since then it's been peaceful

[Steve21]

21 minutes ago, toffee_paul said:

@CHiLL Sorry I meant to say did Senso ever fix it, not Impero.  We use Impero and adding ai.exe into the injection exclusion list didn't resolve it for us.  We are on v8.6.32 which isn't the latest so it may be a newer version fixed this. The changelog doesn't seem to mention it though. Looking at Senso as a potential Impero replacement, are you happy with it?

it's terrible! Coming from an Impero background to Senso V2 and we have had nothing but problems all year with it - Waiting months for bugs fixes, just to have it broken again when another patch comes out

There's no reliability in any part of it, whether it's trying to view screens, shutdown, wake up etc

We'll be looking at alternatives at renewal

Steve