For the record, we're still getting broken Ajax modules when ever we try to modify the 4.9.2 web.config to work with child dotnet applications, which as mentioned earlier in this post was a non-issue with DNN 4.8.2 versions.

Here is the error that happens to our Ajax Modules
********************************************************
A critical error has occurred.
A ScriptManager is required on the page to use ASP.NET AJAX Script Components.
********************************************************

I think we're going to be stuck... or even Doomed.

I'll research this option suggested. I'm just concerned what else could that break. I'll take a look. However i would still like to know and am curious as to exactly why this was changed. From what i'm seeing in other DNN forums including this one, I'm not the only one with this issue.

We're still doing some tests to this perplexing issue. Going to test DNN 4.9.4

So far we're kinda stuck in 4.8.x and running DNN 5.x is not an option at this time. We have some rather outdated modules and skins that would need to be updated. Plus our DotNet Child applications run best under DNN 4.x we just want to get out of 4.8x and us DNN 4.9x
Getting this resolved reminds me of that Economics Teacher in Ferris Bueller's day off
Economics Teacher: "Anyone know what this is? Class? Anyone? Anyone? Anyone seen this before? Bueller?... Bueller?... Bueller? "

But seriously continued feedback would be grrreaaaate "great"