I got a 40" 4K TV that I am using as a monitor via HDMI. It basically works great, except that whenever the monitor turns off or goes to sleep, all my windows resize to a tiny section of top-left corner. This is a common problem, with people asking about it all over the internet, but I haven't found any solutions that actually work for a GeForce GTX 970 (on Windows 7, 100% scaling).
From what I've seen, one solution is to create an EDID profile as a txt file with the correct resolution, and have the video driver use that instead of trying to get it from the TV. Some Nvidia cards support that feature, the GTX 970 does not. I thought by now it would, or that there would be a work-around to emulate this feature, but I couldn't find it.
I've also seen solutions that involve deleting and creating registry keys, but the keys I'm supposed to see according to the instructions aren't in my machine, and I have lots of keys they don't mention. I'd certainly be willing to go this route if the instructions were clear.
I don't know if it's relevant, but I also have a 1080p graphics tablet/monitor connected via a DP->HDMI 2.0 converter. I've not turned that monitor on for a while, and this resizing behavior happens the same regardless of whether that monitor is connected. When I had a 1440p monitor connected via DP this behavior did not happen.
Any help you can offer is greatly appreciated. Thanks in advance!

I got a 40" 4K TV that I am using as a monitor via HDMI. It basically works great, except that whenever the monitor turns off or goes to sleep, all my windows resize to a tiny section of top-left corner. This is a common problem, with people asking about it all over the internet, but I haven't found any solutions that actually work for a GeForce GTX 970 (on Windows 7, 100% scaling).

From what I've seen, one solution is to create an EDID profile as a txt file with the correct resolution, and have the video driver use that instead of trying to get it from the TV. Some Nvidia cards support that feature, the GTX 970 does not. I thought by now it would, or that there would be a work-around to emulate this feature, but I couldn't find it.

I've also seen solutions that involve deleting and creating registry keys, but the keys I'm supposed to see according to the instructions aren't in my machine, and I have lots of keys they don't mention. I'd certainly be willing to go this route if the instructions were clear.

I don't know if it's relevant, but I also have a 1080p graphics tablet/monitor connected via a DP->HDMI 2.0 converter. I've not turned that monitor on for a while, and this resizing behavior happens the same regardless of whether that monitor is connected. When I had a 1440p monitor connected via DP this behavior did not happen.

So that's it? Three days and no solutions for a common and straightforward problem? Does NVidia really care about its customers and reputation so little? NVidia already has a solution available for some of its video cards, I'm just looking for how to implement EDID export/import on a different card. Is this really so difficult?

So that's it? Three days and no solutions for a common and straightforward problem? Does NVidia really care about its customers and reputation so little? NVidia already has a solution available for some of its video cards, I'm just looking for how to implement EDID export/import on a different card. Is this really so difficult?

For example, this document from the Microsoft Hardware Dev page seems like it contains the relevant information to create a custom EDID for any monitor:
https://docs.microsoft.com/en-us/windows-hardware/drivers/display/overriding-monitor-edids
But it's not really instructions for a novice to complete the task, but rather details for somebody who basically understands these topics. I'm the former more than the latter, but there should be people here who understand that document and can post a novice-friendly user-guide to setting this up. Or better, NVidia could make and provide a utility that does this under the covers.

But it's not really instructions for a novice to complete the task, but rather details for somebody who basically understands these topics. I'm the former more than the latter, but there should be people here who understand that document and can post a novice-friendly user-guide to setting this up. Or better, NVidia could make and provide a utility that does this under the covers.

Yes, I realize this is a user-to-user forum. I'm pursuing the NVidia support route, but I fully expect them to be unresponsive and provide no assistance. After all, this problem has been known for years and there is no official or built-in solution so far.
I also expect that some computer-savvy customers have run into this problem, created a fix, and would be able to share it. Especially considering the EDID info I found, I find this much more likely than NVidia actually providing support.

Yes, I realize this is a user-to-user forum. I'm pursuing the NVidia support route, but I fully expect them to be unresponsive and provide no assistance. After all, this problem has been known for years and there is no official or built-in solution so far.

I also expect that some computer-savvy customers have run into this problem, created a fix, and would be able to share it. Especially considering the EDID info I found, I find this much more likely than NVidia actually providing support.

Until about 3 weeks ago the people at NVIDIA "support" were throwing worthless tasks at me trying to get rid of me, but had no idea how to address, let alone solve, the actual problem. Finally 3 weeks ago they escalated me to a "Level 2 Technical Support group for further attention". I haven't heard anything further from them for these three weeks, so it doesn't look like the problem is going to be solved by anybody at NVIDIA.

Until about 3 weeks ago the people at NVIDIA "support" were throwing worthless tasks at me trying to get rid of me, but had no idea how to address, let alone solve, the actual problem. Finally 3 weeks ago they escalated me to a "Level 2 Technical Support group for further attention". I haven't heard anything further from them for these three weeks, so it doesn't look like the problem is going to be solved by anybody at NVIDIA.

probably because the answer has already been posted for years.
This is an issue of windows behavior when the screen goes into a sleep deep enough to trip the hotplug detection and revert to the generic resolution that is set to 800x600 by default which is used when no monitor is connected.
if you connect to the system with a remote desktop app while the monitor is unplugged you can change this virtual resolution.
Changing the values of DefaultSettings.XResolution in the registry might fix it.

This is an issue of windows behavior when the screen goes into a sleep deep enough to trip the hotplug detection and revert to the generic resolution that is set to 800x600 by default which is used when no monitor is connected.

if you connect to the system with a remote desktop app while the monitor is unplugged you can change this virtual resolution.

Changing the values of DefaultSettings.XResolution in the registry might fix it.