After many hours of attempts i am looking for some advice / suggestions my sons set up and my sanity after spending days trying to resolve this for him.
The Latitude 7490 is running Win 11 Pro and does have Thunderbolt available on the laptop (Activated in the Bios as per other posts) but using a WD19 Dock. I am aware there are limits to using such a dock without a Thunderbolt version dock to get 2 x 2560x1600 on both monitors so i resounded myself to 1920 x 1200 as this was what i understood the tech specs of the WD19 allowed but even this i cannot achieve on both monitors.
I have borrowed several others docks to find a resolve, namely a D6000, TB16 (which does have Thunderbolt) or a WD15 but alias i cannot get any of these to allow 2 x 1920x1200 on each either). I can select this resolution on one monitor but then the other only gives 3 profiles in Display Resolution, 2048x1080, 1024x768 or 800x600. Even going onto the Monitor and Intel UHD 620 graphics properties through Advanced Properties the modes are not in the same which i undersood at the lesser resolution would be to make them the same.
I have updated the Latitude firmware and drivers, installed latest Thunderbolt centre software. I have updated firmware on the docks but this has not made any resolve (The TB16 gave a firmware update error when installing - DellDockingStationFwUp_1.0.5_TB16_20210716 - that cyles the monitor every 30 seconds or so and as yet i have not managed to overcome this so i have given up on that for now).
I have tried even using an HDMI direct into the laptop and a docking station but the HDMI does not appear to be anywhere close to the resolution of the Display Port monitor.
The Dock and Monitor were in storage while we moved and the only thing i can think off was that i had changed the Monitor Drivers to get around a similar issue a 24months ago. Since moving 6 months ago the only change has been win 11 pro (outside of the above firmware/driver updates while attempting to resolve the issue)
I have currently settling for 2048 x 1080 but one has a 60hz refresh while the other is 24hz with no option to change either which i find rather perplexing as its all Dell equipment (monitors are 2 x UP3017 if that makes any difference).
First, the display model absolutely can make a difference. Next time it might be worth mentioning that before the very last sentence of the post. If your results had only been experienced when using a WD19 and a WD15, then I would have said that the likely issue was that even if you are selecting 1920x1200 resolution, Windows may only be changing the render resolution, but not the active signal resolution, i.e. the system would still be sending a 2560x1600 signal on the wire, in which case you wouldn't be freeing up any actual bandwidth by using a lower resolution, and that might then be why you can't achieve 1920x1200 on both displays. The way that could potentially be fixed would be to set the resolution using Intel HD Graphics Control Panel / Command Center rather than Windows Display Settings. But you also mentioned using the TB16 and the D6000. They both operate in completely different ways from the WD19/WD15 and even from each other. The TB16 should allow dual 4K 60 Hz or even triple QHD from your system if it has Thunderbolt, and the D6000 should allow dual 4K 60 Hz + 4K 30 Hz all through the dock even from a non-Thunderbolt system thanks to its use of "indirect display" technology called DisplayLink -- not to be confused with DisplayPort. I'm also not sure what you mean that using the built-in HDMI output caused the display to "not appear to be anywhere close to the resolution of the DisplayPort display". The HDMI output on the 7490 and the HDMI input of the UP3017 both support HDMI 1.4, which is enough for 2560x1440, but I'm not actually sure about your display's native setup of 2560x1600. Not all displays support their native resolution and refresh rate on all of their inputs, and typically it's HDMI that can lag behind simply because historically, HDMI has lagged behind DisplayPort in terms of capabilities. But just to be sure, did you actually check Windows Display Settings to verify that the display connected that way was in fact running in that mode when you had it connected via the system's HDMI output? And also make sure it was set to the same scaling setting as the DisplayPort display? If all of that looks good, then I'm not sure exactly what you mean by your description. Maybe posting a photo of the differences you're seeing would be useful.
But if you want to get both displays running through a dock for convenience, first of all I really wouldn't recommend running 2560x1600 display at 1920x1200. A 30" display using only 1920x1200 resolution results in only 75 pixels per inch. The Windows reference standard is 96 ppi, just for context. So that alone is going to result in fairly grainy looking text, and on top of that, you'll have the additional scaling issues caused by the fact that you're mapping a 1920x1200 signal onto a 2560x1600 physical pixel grid, and the former does not map cleanly onto the latter.
So I would focus on getting a setup that allow you to run both displays at their native resolution. You'll get a much sharper image and much more workspace. For that, the TB16 would be the ideal choice, with the D6000 being the fallback if the potential drawbacks of DisplayLink technology are acceptable to you (which I wrote about in the post marked as the answer in this thread.) But I would suggest that you focus on one of these dock choices rather than trying to troubleshoot four very different dock models. With the TB16, I would suggest using the DisplayPort and Mini-DisplayPort outputs, and with the D6000 I'd suggest using the DisplayPort outputs and also making sure you have the latest DisplayLink software direct from DisplayLink.com.
Thank you kindly for the expliantion on active and render signals, not something i was aware of but makes total sense. I will perservere with the Tb16 and attempt to update again without the error. The D6000 was my first go to solution but it does seem to have a conflict with the computer - i suspect the USB-C cable may be damaged but i regardless it has put me on a track to hopefully resolve the issue. I will report back when i (hopefully) have some good news on this.