Any solutions for the explorer.exe memory leak?

ShamrockRig · Oct 20, 2021

Im on 22478.1012 on the dev channel and its absolutely fixed, so id assume it was in the post for everyone else.
Im on intel but i dont think the explorer issue had anything to do with the cpu's. More of an os issue

Globespy · Oct 20, 2021

Ruben said:
I hear you.. I myself did not want to be on Insider/Beta rel. but this one by far for me has been an exception I never opted in for the insider and did not enable it thus however I did d/l and create the iso from uupdump and have been having a very pleasant "Windowy 11" experience thus far initially Premiere Pro could not use up all the 64 cores on the prev. builds of Windows 11 sometimes it (Premiere Pro) did and sometimes it did not. However with this build (22000.282) no such issues 'each and every' time I render a project it uses all the 64 cores no memory leak issues. I am very much satisfied with this build.. rest is up to AMD when they do release a patch let's see which side the cookie crumbles then.

So you did a completely fresh install using the insider build? Or was there a way to update?
Thanks again for your reply.

Ruben · Oct 20, 2021

Globespy said:
So you did a completely fresh install using the insider build? Or was there a way to update?
Thanks again for your reply.

Yes.. I did a fresh install. No other way to update to this build AFAIK. MS should release a patch by next week regarding the same.. I am not too sure though they usually do release a patch every 1st and last Tuesday of the month, you can hold up till next week and see if there is any other build rel. for General Availability, and this particular release (2000.282) has a huge change log but the issue as such is def. fixed in this rel.

ShamrockRig · Oct 20, 2021

Ruben said:
Yes.. I did a fresh install. No other way to update to this build AFAIK. MS should release a patch by next week regarding the same.. I am not too sure though they usually do release a patch every 1st and last Tuesday of the month, you can hold up till next week and see if there is any other build rel. for General Availability, and this particular release (2000.282) has a huge change log but the issue as such is def. fixed in this rel.

New dev build out about 10 minutes ago

Ruben · Oct 20, 2021

Devlin1888 said:
New dev build out about 10 minutes ago

I meant a release to public build .. I highly suspect if Globespy would update to a dev. build

ShamrockRig · Oct 20, 2021

Ruben said:
I meant a release to public build .. I highly suspect if Globespy would update to a dev. build

Id imagine if the dev update had it it wont be long away for the normal release. Was just a so ya know. Would rather mention it and it be useless info than not say anything and it turns out to help someone:) But yeah i doubt he would

Ruben · Oct 20, 2021

Devlin1888 said:
Id imagine if the dev update had it it wont be long away for the normal release. Was just a so ya know. Would rather mention it and it be useless info than not say anything and it turns out to help someone:) But yeah i doubt he would

Yes it's def. worth mentioning

and thanks again for the heads up on the dev. build.

Ruben · Oct 20, 2021

Always try newer dev. Win builds with an extra layer of durex protection, better safe than sorry (mental note to myself)

ShamrockRig · Oct 20, 2021

Ruben said:
Always try newer dev. Win builds with an extra layer of durex protection, better safe than sorry (mental note to myself)

AV free since 2018 and also have the auto sample sub off in settings too. Best extra later of durex is the layer inside ya head! 0 issues since i turned it all off btw xD

Ruben · Oct 20, 2021

Devlin1888 said:
AV free since 2018 and also have the auto sample sub off in settings too. Best extra later of durex is the layer inside ya head! 0 issues since i turned it all off btw xD

It's not the AV issues that bother me a tad bit.. it's more of the new(er) features in the dev build which my machine would not digest completely that might trigger off something unexpected with the machine and in turn lead to a greater chain of events like for example in the last dev. build I tried to update to (10.0.22478.1000) was not behaving the way it was supposed to, I was getting random blackouts with the monitor had to macrium back to the last stable Win 11 build

ShamrockRig · Oct 20, 2021

Ruben said:
It's not the AV issues that bother me a tad bit.. it's more of the new(er) features in the dev build which my machine would not digest completely that might trigger off something unexpected with the machine and in turn lead to a greater chain of events like for example in the last dev. build I tried to update to (10.0.22478.1000) was not behaving the way it was supposed to, I was getting random blackouts with the monitor had to macrium back to the last stable Win 11 build

Ahh really man that sucks, Yeah ive heard some people have some issues, Biggest one i had was the explorer.exe restarting itself making the taskbars disappear for a second til it restarted, Thats been the biggest issue i think ive had so far and it was sorted weeks ago. The dev builds are going back to less stable i believe than what they have been due to properly trying new features now that the stable public version is fine

Ruben · Oct 20, 2021

Devlin1888 said:
Ahh really man that sucks, Yeah ive heard some people have some issues, Biggest one i had was the explorer.exe restarting itself making the taskbars disappear for a second til it restarted, Thats been the biggest issue i think ive had so far and it was sorted weeks ago. The dev builds are going back to less stable i believe than what they have been due to properly trying new features now that the stable public version is fine

Exactly my point..:)

ShamrockRig · Oct 20, 2021

Ruben said:
Exactly my point..:)

Just weird that some issues other people just do not have and some do. Joys of dev builds

Globespy · Oct 20, 2021

Hmm....not sure I want to wait until November (potentially).
Wonder if I just enable insider and it should be a CU? Then just disable after to avoid insider builds beyond that on this machine.

Almighty1 · Oct 20, 2021

I am on 22000.282 and I have the issue because explorer.exe is still on 22000.120 is probably the reason why. I can close my 200+ chrome tabs but the memory never gets released.

ShamrockRig · Oct 20, 2021

Almighty1 said:
I am on 22000.282 and I have the issue because explorer.exe is still on 22000.120 is probably the reason why. I can close my 200+ chrome tabs but the memory never gets released

Over 200 chrome tabs? What in the...Nevermind i dont even wanna know xD!.

Stigg · Oct 20, 2021

I'm not sure how many people notice it, but I sometimes see explorer.exe restart itself.

ShamrockRig · Oct 20, 2021

Stigg said:
I'm not sure how many people notice it, but I sometimes see explorer.exe restart itself.

I'd imagine everyone would notice it, The taskbar and any open folders etc close straight away. Unless theyre afk of course

RFS · Oct 20, 2021

Stigg said:
I'm not sure how many people notice it, but I sometimes see explorer.exe restart itself.

Yes that happens with me too. Twice so far on 11 according to Reliability Monitor. But then it was also doing it on W10 before the upgrade too.

Like this, for example

Description
Faulting Application Path: C:\Windows\explorer.exe

Problem signature
Problem Event Name: APPCRASH
Application Name: Explorer.EXE
Application Version: 10.0.22000.120
Application Timestamp: e846e749
Fault Module Name: twinui.pcshell.dll
Fault Module Version: 10.0.22000.132
Fault Module Timestamp: 7a0688ac
Exception Code: c0000005
Exception Offset: 00000000005628bf
OS Version: 10.0.22000.2.0.0.768.101
Locale ID: 2057
Additional Information 1: 7ed1
Additional Information 2: 7ed143d9573b4373eb0b0a21ad148c5f
Additional Information 3: f419
Additional Information 4: f419cc10eb921adb65e92e44dd81d539

Almighty1 · Oct 20, 2021

Devlin1888 said:
Over 200 chrome tabs? What in the...Nevermind i dont even wanna know xD!.

Well, it's from years of stuff and that's nothing. When Windows 11 first appears on July 3, 2021 because of the weekly reboots, I actually didn't restore all the tabs each time with Tabs Outliner. It's obviously you're not a power user.

Regardless, people are still experiencing the issue, they had provided fixes with some in the Dev channel a month ago which was after 22000.120 so it might only occur in certain instances. It may not even be a memory issue but more of a Windows resource issue as those are limited.

See Windows Insider Program