Windows explorer continually restarting with latest Filr Client (24.4) and preview pane turned off

I have been following this issue for the past few months:

 Issues with FilrAppHook64.DLL Causing Windows Explorer Crashes 

However, even when following through with the recommended "fix" of turning off the preview pane, but now we are seeing the issue even with preview disabled. Is there a timeline from OT around a fix being released so that we can actually have a usable product again?

  • 0  

    Hi,

    I don't have reports about this problem, maybe related to AV or something in that direction ?

    David

  • 0 in reply to   

    Thanks. I am working to get some consistent time with one of the devices we are seeing the issue with so that I can dive in more deeply. That is one thing we want to try.

  • 0  

    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.

    Rodney

    If you found this post useful, give it a "Like" or click on "Verify Answer" under the "More" button.   This helps others.

  • 0 in reply to   

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

  • 0   in reply to 

    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?

    Rodney

    If you found this post useful, give it a "Like" or click on "Verify Answer" under the "More" button.   This helps others.

  • 0 in reply to   

    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.

  • 0   in reply to 

    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.

    Rodney

    If you found this post useful, give it a "Like" or click on "Verify Answer" under the "More" button.   This helps others.

  • 0 in reply to   

    Here is the last cumulative update I can pull from our monitoring service:

    2024-12 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5048667)

    OS version is: 10.0.26100

    I can try and pull more info, but I will probably need to get my hands on the device.

  • 0 in reply to 

    Another strange occurrence is that it seems to work more consistently when it is NOT hooked up via HDMI to an external monitor. Sadly, I have not been able to recreate it with what I have in the office.

    They are corporate devices, but we do not control the updates at the moment.

  • 0   in reply to 

    Ok, I'll run some tests on a few 24h2 vms with the dec CU, but my work laptop is on that version as well and so far no issues, but I'll check the CU version in case it hasn't had time to patch past November

    external monitor causing issue is a definite oddity as I've never seen that in years using Filr going back to 1.0.1. I'll attempt to reproduce via my laptop but this is a new one.  I assume they are doing extended display and not mirrored or external only correct? I always find it odd when a user hooks up a laptop to an external display then chooses not to use the laptop as one of the screens for at least some form of app display such as email or messaging.

    Rodney

    If you found this post useful, give it a "Like" or click on "Verify Answer" under the "More" button.   This helps others.