We have a Shell window registered under Control Panel. We use Win API CoCreateInstance to create an instance of it on the local system. Earlier this used to use the default explorer.exe process (the one used for tray icons and taskbar). But after installing the recent updates KB4579311 and KB4577671 on Windows 10, we see that a new explorer.exe process is started with /factory switch. It looks something like this in the task manager.
C:\windows\explorer.exe /factory,{5BD95610-9434-43C2-886C-57852CC8A120} -Embedding
We also observed that now launching Control Panel always runs it in a separate explorer.exe with a similar "/factory" switch.
There are also couple of new registry keys which look related - these do not exist on machine without updates.
HKEY_CLASSES_ROOT\CLSID\{5BD95610-9434-43C2-886C-57852CC8A120}
HKEY_CLASSES_ROOT\CLSID\{5BD95610-9434-43C2-886C-57852CC8A120}\LocalServer32
My question is - Has something changed in these recent updates that causes this behavior? Is there a way via some preference or registry settings to force the default explorer.exe to be used?
Is this a conscious design change to always use a separate explorer.exe for opening Control Panel and all the programs registered under it? If so, is there some documentation update or articles that provides more insights into this?