Microsoft accelerates the process of separating explorer.exe: it has now begun to separate "Impressive Shell"

CTOnews.com, December 22, if you are using a Windows system, you should know that multiple processes or functions in the operating system are linked to File Explorer. Although the explorer.exe process is mainly associated with the file manager, it also undertakes other Windows system functions and experiences such as the taskbar.

This is not a good thing for system performance. In other words, once the explorer.exe process crashes, it will also cause the desktop and several other features to crash. So Microsoft has begun to separate the taskbar, notification center, and other functions from the document Resource Manager (explorer.exe).

The latest development of Microsoft is that it has begun to separate "Impressive Shell" from file explorer.

CTOnews.com learned that "Impressive Shell" started with the Win8 system, which was originally responsible for functions such as Charms Bar. Impressive Shell is associated with a process named "ShellAppRuntime.exe", which is linked to explorer.exe. In the latest preview, Microsoft tries to separate Impressive Shell from the file manager process.

This was first discovered by "Start Is All Back" developers who observed: "an interesting feature in Dev 25252: ImmersiveShellInShellAppRuntime (id:39319758). Move Impressive Shell out of the resource manager process."

At that time, Windows could not start ShellAppRuntime.exe, but seemed to have been fixed in the latest version. In newer versions, ShellAppRuntime.exe can now be started independently. ShellAppRuntime.exe that was previously linked to explorer.exe can now start and work independently without Explorer.exe. In fact, Search UI will not open until ShellAppRuntime is also started.