I reviewed your response and carefully read each item in "Video and Display Settings" description.
They do not resolve the issue that this posting is about.
The issue is a major bug that Microsoft introduced in several builds and then fixed it.
It's actually linked to a new feature change in 1809.
Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class{4d36e968-e325-11ce-bfc1-08002be10318}\0001
FeatureTestControl