Recently Explorer crashes with ntdll.dll

[prokopes_]

Thank you, we're checking what might be wrong. I will try to keep you posted.

[markinson]

I follow this discussion, hoping so much that a decisive solution can soon be found, because this inconvenience is really annoying and the temporary remedy, by someone found and fortunately suggested (disable the antivirus from the contextual menu - context menu - of files, folders, etc.), really "weak", especially for the typical features that an antivirus must have.

My configuration:
Avast! Free
Ver 23.9.6082 Build 23.8.8416.791 >>> the issue is present
Ver 23.9.6082 Build 23.9.8494.792 >>> the issue is present

O.S.: Windows 10 PRO recently updated

Process that crashes: Explorer.exe
Dll who crashes: ucrtbase.dll

I specify that, even or at least in my case, everything seems to have originated with the latest versions of the antivirus and the Windows 10 PRO operating system (O.S.) cumulative update of September 2023-09 KB5030211.
Finally, the "twin" antivirus also seems to suffer from the same inconvenience: here.

Let's hope so ...

P.S.
Sorry for my English!

[prokopes_]

Hi, we just released a new fix addressing this problem. The fix should work with both program versions 23.8 and 23.9. There should be no need to reboot the device to apply the fix.

Can you please check if you still see new explorer.exe crashes?

[lucasfrance]

Thank you very much !

After a short testing session in my win 7 partition, it seems the 795 micro-update properly fixes the problem on the 23.9 version !!!

Should the right click issue occur again, I will report back.

THANK YOU.

BR.

[markinson]

Hi, we just released a new fix addressing this problem. The fix should work with both program versions 23.8 and 23.9. There should be no need to reboot the device to apply the fix.

Hi! I tried just now to update my program (23.9.6082 Build 23.9.8494.792), but the micro-update (fix) is still not available. Have I to wait? (I'm in Europe-Italy).
Thank you in advance for your help!
Cheers.

[lucasfrance]

Got it here in Switzerland...

[prokopes_]

Hi, we just released a new fix addressing this problem. The fix should work with both program versions 23.8 and 23.9. There should be no need to reboot the device to apply the fix.

Hi! I tried just now to update my program (23.9.6082 Build 23.9.8494.792), but the micro-update (fix) is still not available. Have I to wait? (I'm in Europe-Italy).
Thank you in advance for your help!
Cheers.

Yes, it should arrive automatically. If you still haven't received it, can you please reboot your computer and check the program version again? The fix version should end with 794 or 795.

[Gizm0]

Hi, we just released a new fix addressing this problem. The fix should work with both program versions 23.8 and 23.9. There should be no need to reboot the device to apply the fix.

Can you please check if you still see new explorer.exe crashes?

Thank you  , i guess my avast automatically updated with the fix, now the version is 23.9.6082 (build 23.9.8494.795).
For now no more ntdll.dll error occured.
But my question is why version 23.9.6082 and his fix automatically updated while the app was on manual update ? this never happened before.

[prokopes_]

Hi, we just released a new fix addressing this problem. The fix should work with both program versions 23.8 and 23.9. There should be no need to reboot the device to apply the fix.

Can you please check if you still see new explorer.exe crashes?

Thank you  , i guess my avast automatically updated with the fix, now the version is 23.9.6082 (build 23.9.8494.795).
For now no more ntdll.dll error occured.
But my question is why version 23.9.6082 and his fix automatically updated while the app was on manual update ? this never happened before.

Good question. The "Manual update" is only relevant for "program updates". This particular update was a "micro update" within your "current" program version (23.9.). I hope that makes sense.

[Gizm0]

Hi, we just released a new fix addressing this problem. The fix should work with both program versions 23.8 and 23.9. There should be no need to reboot the device to apply the fix.

Can you please check if you still see new explorer.exe crashes?

Thank you  , i guess my avast automatically updated with the fix, now the version is 23.9.6082 (build 23.9.8494.795).
For now no more ntdll.dll error occured.
But my question is why version 23.9.6082 and his fix automatically updated while the app was on manual update ? this never happened before.

Good question. The "Manual update" is only relevant for "program updates". This particular update was a "micro update" within your "current" program version (23.9.). I hope that makes sense.

Yep that makes sense for the "micro update" but same thing happened last week when my program automatically updated from 23.9.6044 to 23.9.6082, it's so weird...
Upper in the topic @BEX64 describes the same thing.

[markinson]

Yes, it should arrive automatically. If you still haven't received it, can you please reboot your computer and check the program version again? The fix version should end with 794 or 795.

I can confirm: the micro update 795 (my current version is 23.9.6082 - build 23.9.8494.795) arrived automatically, without the need to restart the computer.
Hopefully the explorer crash issue has been fixed. I re-enabled the Avast context menu shell extension and now I will do some testing for this and then report back here on the forum.

For now, thank you very much for the support provided! 

[markinson]

As far as I have been able to verify so far, the problem has never recurred. The fix worked!

Thank you so much for your timely support. 

[markinson]

Unfortunately, in my opinion, another equally serious, perhaps more, issue, after the micro-updated (fix) 795 (now version 23.9.6082 - build 23.9.8494.795), the function of scanning the incoming messages (in my case through the IMAP protocol) blocks the arrival and updating of mail folders. As soon as this option is disabled, the mail program resumes immediately to work and the messages are again downloaded/synchronized.

I will open a new thread for this new problem. 

Thanks for the attention.