3 Replies Latest reply on Jul 26, 2018 6:38 AM by Intel Corporation

    Quantization Range value in Control Panel does not persist after reboot (Windows 10 Pro)


      I was originally having a problem, with my mouse cursor not showing in the Google Chrome Developer Mode. It was fixed by changing the Quantization Range value to Full Range, as per this StackOverflow page:


      Cursor not showing in Device Mode (Google Chrome) - Stack Overflow


      However, every morning the problem re-appears when I turn on my computer. I need to go into the Intel Graphics Control Panel, change the Quantization Range value (which is already on Full Range) to something else, click apply, change it back to Full Range, click apply again, then exit the control panel. The issue is then resolved.

      It seems to me that the value is being saved by the control panel, but not actually being applied (by the driver?) upon system boot. System information is below:


      Intel(R) HD Graphics 530

      Report Date: Monday, July 23, 2018

      Report Time [hh:mm:ss]: 12:35:50 PM

      Driver Version:

      Operating System: Windows* 10 Pro (10.0.17134)

      Physical Memory: 32640 MB

      Vendor ID: 8086

      Device ID: 1912

      Device Revision: 06

      Video BIOS: 1031.0