No improvement after uninstalling Photos.DLC.MediaEngine and a reboot. Still 30% to 50% persistent CPU burn from Shell Infrastructure Host.
Are there any other solutions?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have two computers on Windows 11 22000.318 and on both of them when I connect my 512GB Samsung SSD "shell infrastructure host" starts to use a lot of CPU and power usage is "very high" in task manager. I understand this may be normal when browsing large folders on the SSD or copying files to/from the SSD but even if I close all the File Explorer windows to the SSD "shell infrastructure host" continues to use a lot of CPU. If I try to eject the SSD it says its in use. So my only option is to log out of Windows and log back in and that stops "shell infrastructure host" and it goes back to normal. Could this problem be part of the Windows 11 memory leak bug with File Explorer I've been hearing about? Or maybe something to do with indexing going on? My external SSD has thousands of photos and I am using the Photos app.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
No improvement after uninstalling Photos.DLC.MediaEngine and a reboot. Still 30% to 50% persistent CPU burn from Shell Infrastructure Host.
Are there any other solutions?
This CPU heating issue is getting much worse lately. I'm going to try the suggestion to uninstall Photos.DLC.MediaEngine
That's great! Thank you very much 👍
1- Drag and Drop: Google it. Please!!!
2- Dear believe me... The file is different from folder :D https://mspoweruser.com/windows-11-did-away-with-folder-icon-thumbnails-and-we-did-not-even-notice/
3- Disable the more options???!!! Why should I do that?!
Thank you for your response.
Found it! Thank you very much. I have been browsing some images folder with the photo app and so far the problem hasn't occur again yet so maybe it actually worked.😊