Impero Client Causing Being Odd!

[IanT]

Hi all,

 

We’ve been chasing down a really odd issue and finally pinned it down to the Impero Client.

 

On our Windows 11 (24H2, latest cumulative update) machines, when a anyone logs in and uses Word (M365 Apps), dropdown menus (e.g. font selector) disappear as soon as you try to scroll, This makes Word basically unusable for those users.

 

After a lot of testing we confirmed:

• If we disable the Impero services (Impero Service Starter, ImperoClientSVC, ImperoGuardianSvc) → issue immediately disappears.

• If we start the impero services, boom the issue comes back!

 

So this is 100% tied to Impero injecting itself into the session.

 

Has anyone else seen this on Windows 11 24H2? If so, did you manage to get a fix or hotfix from Impero? We’re planning to escalate to their support, but I’d be keen to know if this is widespread.

 

See video!

 

[6Foot2]

Not this, but I have seen an unrelated issue caused by Impero.

 

For a while I had been upgrading Impero in place instead of removing the old version, creating a new package and deploying that.

 

The problem came to light when I was forced to use new cheaper laptops that I had not tested on our network. By that time I had deployed five, maybe six, Impero inplace upgrades without issue (until these new cheap laptops) so the problem took a while to track down.

 

👍

[DrCheese]

14 minutes ago, 6Foot2 said:

Not this, but I have seen an unrelated issue caused by Impero.

 

For a while I had been upgrading Impero in place instead of removing the old version, creating a new package and deploying that.

 

The problem came to light when I was forced to use new cheaper laptops that I had not tested on our network. By that time I had deployed five, maybe six, Impero inplace upgrades without issue (until these new cheap laptops) so the problem took a while to track down.

 

👍

 

Yes, I had similar with Netsupport back in the day - I'd always just done upgrades when pushing out via GPO. This wasn't something they had tested for so it would leave junk from old installs around that would then interact & cause issues.

 

Best way in any GPO is to remove the old MSI and push the new ones - Have moved to that over the years.