Windows – “Input Not Supported” on Acer S241HL Monitor with HDMI after Windows 10 Fall Creators Update

The Microsoft stock answer is as follows.

Method 1:

You may try these steps to reset the Windows update components manually and check.

1. Press Win+X on the desktop screen of the computer.
2. Select Command Prompt (Admin)

3. On the open Command Prompt window copy and paste the commands :

   net stop wuauserv
   net stop cryptSvc
   net stop bits
   net stop msiserver
   ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
   ren C:\Windows\System32\catroot2 catroot2.old
   net start wuauserv
   net start cryptSvc
   net start bits
   net start msiserver
   

4. Exit the command prompt and check.

Delete the renamed folders if everything is correct.

You can try the following step if the issue persists.

Method 2:

Check if the region is correct. Follow the steps mentioned.

1. Type "Region" on the Start screen. Click "Settings" and press Enter.
2. On the "Format" tab, select "English (United Kingdom)".
3. Click "Languages Preferences"> "Add a language" and add "your language".
4. Once added, select it and click "Move Up" to make it the first language. Close the Language window.
5. On the "Region" window, click "Additional Settings" and check if the values are same.
6. Click the "Location" tab and change the Home Location to "your country" and then click OK.

Success/solution!
I have the same system (more or less, same x299 MB and 960 Pro NVME drive).
I got this to work, finally, after building custom boot media, trying some things reported, like disabling SMART, and more.
Nothing worked, and I was unwilling to trash my install and do a clean one, at least not yet...

What did the deal for me was moving the drive into a "fake RAID" mode, by enabling it under IRST. I'm almost positive this abstracts (i.e. doesn't use) the NVME bus, and then update to 16299.19 (with patch) went off without a hitch, finally!

Afterwards, I "flipped" it back to AHCI, so it could run through NVME and re-installed the Samsung NVME driver.
Under IRST I was getting about 50% performance (50% of the Samsung driver, which gives me about a 40% boost over the Inbox NVME driver), so basically about half-speed of NVME.
I'm set though, and hopefully this will help others that are stuck on the Fall Creators build, with a Samsung NVME drive...
Good thing to "keep in the back of your mind" too, whenever a major update needs to boot minimally, this might still be necessary (depending on NVME Windows integration AND BIOS updates).