2021 Admin Does Not Show Upper Menu

Jmaitino, good on you for sorting that out. And yep, changing that default scriptsrc value back to its default (/cf_scripts/scripts) is a quick short-term fix to solve the Admin problem. But beware that it's not the right long-term solution, if your web server (IIS or Apache) sites have a virtual directory with the path that you found it set to.

I had started writing up a reply, addressing what all this is about, how it can happen (often on migrating in CF admin settings from another machine), and how you could change the value (like you did) as a short-term solution. But I also explained why that may be a problem, and then about the better long-term solution. I also addressed why this is something Adobe could handle better. But I started out with showing how to make that short-term fix, then I saw the last sentence of your reply to Dave, and that you were set for that, so I'll create a blog post instead. 🙂

In the meantime, if you still have what your original value was, and if you do confirm that your IIS or Apache web sites have a virtual directory named with that value, then the better long-term solution is this:

• put that original value back (in the Admin "default scriptsrc directory" setting). That way your web sites served via IIS or Apache won't suffer problems. And yep, momentarily your admin will have that problem again. But that can be fixed, and that's the next step.
• You'll then want to change things so that CF's built-in web server, which is used by the CF Admin, knows ALSO about and can use that "original" value you had. It's a manual tweak to CF's server.xml file, which Pete Freitag also explains here  https://www.petefreitag.com/item/867.cfm.

Hope that's helpful. (And really, Adobe should fix it so that if that value is changed in the CF admin, THEY make this needed change in the server.xml for us.)