Could be something in very recent WIndows 11 update.

My test system I have preview builds enabled on 24H2, and with last weeks OS build 26120, just having filr installed makes explorer crash.  I had to uninstall the Filr client in order to use my computer.

Could be, we are seeing it with machines moving to 24H2.

I wasn't seeing this on the production 24h2 26100 build.   
were you on 23H2 previously and it was working there?  Or are you coming from Windows 10?

I'm not sure I can get that specific, but these devices would have been on the prior install and now receiving the service update. They were on 11 initially. For many, moving to Windows 11 update and a new version of the client.

I'm not sure I can get that specific, but these devices would have been on the prior install and now receiving the service update. They were on 11 initially. For many, moving to Windows 11 update and a new version of the client.

Are these corporate devices where you're controlling the updates?  Just wanna be sure no preview builds are sneaking in like what I'm running. 

If they were on previous windows 11, should have been 23h2, which was just some basic feature enablements to 22h2.  Their explorer was the same as far as I'm aware.

Be helpful to get the full windows build number from afflicted worksations.  should be 26100.xxxx 

also knowing latest cumulative update KB# they have installed.