Please provide more detail. What exactly do you mean by the monitor not "turning off"? For example, does this mean not entering power saving mode of the monitor? Or the computer not going to sleep? or What? Also please describe the sequence of events that leads to the issue, i.e., how or when do you see it?
There are a lot of particulars involving settings in Windows and features of particular monitors, and probably also the connection to the monitor (HDMI?, or ?) that get involved here. I will review the code looking for things that might affect the PC going to sleep but the fact that other users are not complaining about this suggests it may be particular to your setup.
NOTE: This is just a replacement executable file NOT an installer.
I made a change that looks promising in my tests at least. To invoke the fix you need to use command-line option -allowDisplayOff (not cap sensitive). I'm thinking this may be the preferable default mode of operation so in the next release version I may change it so you have to use a CL Option to prevent the screen turning off.
It depends on what your fix does. I would think that allowing the monitor to turn off would be the desired outcome. I know I had the issue for over a year and only decided to track down the cause after upgrading the machine to Windows 10 and having the issue stay around. Its possible that nobody knows that VAP is the cause because I spent a week tracking it down because NONE of the tools were pointing at VAP and I only realized it after stopping it from running.
I admit to not fully understanding all the details about programming sleep in Windows but here is my best understanding of the situation:
VAP does not intend to actually let your processor sleep, because it is always checking for new (or deleted) video files in the monitored folder any time it is running. What VAP attempts to control is whether the display can turn off after the inactivity time specified for Screen (not Sleep) in Windows 10 power management settings (Settings … System … Power & Sleep). The default in VAP Ver. 1.40 is to allow the display to go off, unless prevented by the CL option -keepDisplayOn. (There is no CL option -allowDisplayOff in 1.40, since that is the default.)
A copy of VAP 136T3 no longer exists. It could be reconstructed from my Git repo but I would rather not go to that trouble since I am confident that 1.40 in default mode duplicates the functionality of 136T3 with the -allowDisplayOff CL option, with respect to this issue.
If you want your PC to actually sleep, I think you will have to exit VAP.