Hello. Currently running Insiders build 20H2 or version 19042.546. Last night, with the Nexus docker on the desktop, the above KB was installed. Directly afterward, the ability to run "msconfig" from Task Manager was missing. Further, Task Manager itself would always open to the default blank white square and not remember any Processes that I'd unchecked to NOT be displayed.

I de-installed the Nexus docker and Task Manager would then remember my settings and open properly--once the machine was restarted. Installed Nexus again and Task Manager would only open to defaults with no memory--upon machine restart.

The msconfig run-from-Task-Manager issue--I was able to restore its path in the registry; it had completely vanished.

Could you take a look at this, please? To clarify--I made a snip of how Task Manager opens upon machine restart with the Nexus docker installed. Only happened after that KB was installed. Tx!

I know a number of developers who refuse to work on unreleased versions of Windows (and associated KBs). Why? Because they could "fix" a problem that MS created (often spending many hours doing so) only to find that MS fixed their own problem later and now the developer (possibly) has to undo their own fix. Regardless, it wastes a lot of time.

If you are using the Insider Edition of Windows, I strongly suggest you report issues to Microsoft. After all, Jorge didn't change anything for a Microsoft component to stop working correctly. I'd far rather see him fix current bugs and add new features than to chase something down that might be a non-issue by the time the rest of us download a released version of Windows.

Remember, the Insider Edition inherently means you agreed to test it for Microsoft and report issues to them.