So if you don't already know, Classic Shell is no longer in development, the good news is it currently still works with 1803 flawlessly, but who knows if that will last in the future with how Window 10 evolves.

But there's more good news, it's been forked and the fork is called Classic Start, it's basically the exact same thing currently, but it's worth keeping an eye on it, and I'd imagine in the future people will move to that from Classic Shell as Classic Shell slowly starts to break with W10 updates.

Also can you make sure you support Classic Start the same way to do with Classic Shell?

Classic Shell is no longer actively developed;
www.classicshell.net/forum/viewtopic.php?f=4&t=8147

Classic Start Github;
https://github.com/passionate-coder/Classic-Start

So I saw this in the latest beta changelog;

"Change: Added support for Open Shell (a Classic Shell fork)"

And I just want to let you know (maybe you already know) that their original name Classic-Start which is what my topic was about, had to get changed due to a copyright issue, they then changed the name to NeoClassic-UI which wasn't well received by the community I guess, so they changed their name again, this time to Open-Shell. So it's been quite the clusterf**k trying to follow this project.

Anyway they seem to have settled with Open-Shell for now, just letting you know.

https://github.com/Open-Shell/Open-Shell-Menu

Yeah I figured you got it right since you used the correct name in the patch notes, but you never know, it's worth noting the Classic Shell currently still works great with 1803 but breaks with 1809 so people will want to get ready to jump ship for when that times comes, it's good to know DF will be ready and waiting.