This is still an issue in a Windows Server 2022 environment (upgraded from a Win 2012 R2 environment a couple of years ago). There's obviously a bug somewhere, or something not addressed in Active Directory. I was starting to go a bit wild over this myself. My printer name has the slash, but obviously the actual share name completely eliminated the slash (Windows won't permit invalid characters when you initially create the share). It's a bit silly the Group Policy editor chokes on this, but I'm not going to fret. Thanks for the solution - I didn't think to look for the problem in this manner. Surprised your video hasn't attracted more attention.

such a life saver. Thank you

Nice Freddie good job

Thank you! This is exactly the issue i was running into myself :)

Saved me. MANY thanks! (Same damn printer too)

Great video and very detailed.