explorer.exe issue

[A.lemane]

explorer.exe use more then 2 GB of memory (like a loop or something) when i open my movies folder (more then 200 GB of movies)

windows 8.1 up to date clean stat no additional softwares r installed

this is the 3 sys with this issue @@!

[exodius]

when i open my movies folder (more then 200 GB of movies)

1. I think your problem came from thumbnail cache. Explorer always generate/access thumbnail every time you open your movies.

Try to deactivate it. http://www.sevenforums.com/tutorials/10794-thumbnail-cache-enable-disable.html

2. Or try to deactivate movies/image preview :

Folder options > Click the View tab, and then check the Always show icons, never thumbnails checkbox.

Click OK, and youre done.

Or you can tweak this on windows 8 manager.

[A.lemane]

i already did some troubleshooting and that's not the problem

+

i replaced the windows default shell with icaros and media preview after that and it didn't solve it

i think it is an explorer shell that extract some tags & data from audio & video and it may not work on one or couple of my movies codec !

[rahulgi]

just try hitman pro, be on the safe side

you have installed any video player/codec?

uninstall all those preview, player softwares

are you using build-in windows media player

install klite codec with player here , during setup choose as follows

you can also try 'restart' explorer from task manager(right click explorer.exe)

let see whether it consumes extra on opening that movie folder

also look a peek at taskmanager disk activity (performance>disk no) while opening that folder

also try win build in drive error checking

[A.lemane]

nope none of those is my pb unfortunately

windows 8.1 up to date clean stat no additional softwares r installed

the sys is in a clean stat & its not windows thumbnails shell PB neither icon cache !

i format my sys partition every 2 moths (not the quick way !)

if any one want to use klite codec pack i suggest that they download & install lav filters icaros codectweack tool MPC-HC (all up to date ^_*)... the package that they need i personally prefer that way

[el_espaniol]

Hi mate...try this... :think: :

Create a new user profile and transfer all your files and settings over to it. If it is a domain joined computer you can try deleting the current cached user profile (make sure you back up the user's Desktop, Documents, IE Favourites and their Outlook NK2 and PST files)....

After things have settled down with the new user profile at some point later you can delete the corrupted user profile with the explorer.exe memory leak...It might be a problem with a Registry key or maybe a file like desktop.ini triggering the runaway explorer.exe memory usage... :think:

Hope help this. Regards... ^_^

[SoftChip]

Btw, the proper way to restart the shell (main explorer.exe process) in Win7 is

- Open the Windows menu (click the round Windows "Start" button)

- Shift-Ctrl-right-click on the glassy space above the shutdown button

You will see "Exit Explorer". Click that and the shell shuts down. Then, restart explorer through Task Manager.

Doing it this way ensures the shell is appropriately shut down and not just "killed and restarted". Also, the shell restarts under un-elevated rights like it should. Some other methods (like Process Explorer!) restart the shell in Admin rights, a security risk.

[mazigh]

Btw, the proper way to restart the shell (main explorer.exe process) in Win7 is

- Open the Windows menu (click the round Windows "Start" button)

- Shift-Ctrl-right-click on the glassy space above the shutdown button

You will see "Exit Explorer". Click that and the shell shuts down. Then, restart explorer through Task Manager.

Doing it this way ensures the shell is appropriately shut down and not just "killed and restarted". Also, the shell restarts under un-elevated rights like it should. Some other methods (like Process Explorer!) restart the shell in Admin rights, a security risk.

There are some other ways to share:

1- If you are using process lasso, it become an easy job as you right-click on explorer.exe and choose restart

2- CTRL+SHIFT+Esc and Task Manager will appear > "Details" Tab (for Windows 8 ) > right-click on "explorer.exe" then Click "End Task", the shell will disappear > then go to File> run new task > type "explorer.exe" and check "run with admin privileges.." OK and done

[A.lemane]

Hi mate...try this... :think: :

Create a new user profile and transfer all your files and settings over to it. If it is a domain joined computer you can try deleting the current cached user profile (make sure you back up the user's Desktop, Documents, IE Favourites and their Outlook NK2 and PST files)....

After things have settled down with the new user profile at some point later you can delete the corrupted user profile with the explorer.exe memory leak...It might be a problem with a Registry key or maybe a file like desktop.ini triggering the runaway explorer.exe memory usage... :think:

Hope help this. Regards... ^_^

Btw, the proper way to restart the shell (main explorer.exe process) in Win7 is

- Open the Windows menu (click the round Windows "Start" button)

- Shift-Ctrl-right-click on the glassy space above the shutdown button

You will see "Exit Explorer". Click that and the shell shuts down. Then, restart explorer through Task Manager.

Doing it this way ensures the shell is appropriately shut down and not just "killed and restarted". Also, the shell restarts under un-elevated rights like it should. Some other methods (like Process Explorer!) restart the shell in Admin rights, a security risk.

Btw, the proper way to restart the shell (main explorer.exe process) in Win7 is

- Open the Windows menu (click the round Windows "Start" button)

- Shift-Ctrl-right-click on the glassy space above the shutdown button

You will see "Exit Explorer". Click that and the shell shuts down. Then, restart explorer through Task Manager.

Doing it this way ensures the shell is appropriately shut down and not just "killed and restarted". Also, the shell restarts under un-elevated rights like it should. Some other methods (like Process Explorer!) restart the shell in Admin rights, a security risk.

There are some other ways to share:

1- If you are using process lasso, it become an easy job as you right-click on explorer.exe and choose restart

2- CTRL+SHIFT+Esc and Task Manager will appear > "Details" Tab (for Windows 8 ) > right-click on "explorer.exe" then Click "End Task", the shell will disappear > then go to File> run new task > type "explorer.exe" and check "run with admin privileges.." OK and done

problem solved

i simply selected properties on the folder that create the issue go to customize tab optimize folder for : change value from Videos to General items

[el_espaniol]

Greets...! Nice You found a way to solve the problem...!!! ^_^

Remains.

[SoftChip]

Btw, the proper way to restart the shell (main explorer.exe process) in Win7 is

- Open the Windows menu (click the round Windows "Start" button)

- Shift-Ctrl-right-click on the glassy space above the shutdown button

You will see "Exit Explorer". Click that and the shell shuts down. Then, restart explorer through Task Manager.

Doing it this way ensures the shell is appropriately shut down and not just "killed and restarted". Also, the shell restarts under un-elevated rights like it should. Some other methods (like Process Explorer!) restart the shell in Admin rights, a security risk.

There are some other ways to share:

1- If you are using process lasso, it become an easy job as you right-click on explorer.exe and choose restart

2- CTRL+SHIFT+Esc and Task Manager will appear > "Details" Tab (for Windows 8 ) > right-click on "explorer.exe" then Click "End Task", the shell will disappear > then go to File> run new task > type "explorer.exe" and check "run with admin privileges.." OK and done

Your options do exactly what I say are wrong for Explorer.exe. Using "End task", "Kill task" or restart just deletes the process and all it's memory, possibly leading to corruption. Those options are LAST RESORT options. Use the processes built-in restart options before using those damaging task killing options.

Since the OP's problem is solved, this post is only to clarify the information given above. Any further discussion on that subject should be in it's own thread, where I would gladly respond if notified :-)