Ok, as I suspected. That system doesn't have AMT or iTPM. So there's nothing you have to do as far as ME firmware and drivers are concerned.

Those old Windows versions of the tools don't seem to work on newer operating systems. Personally I tested the DOS versions using DOSBox and these do run but of course I would only use that method for displaying info and not flashing. For flashing, an actual DOS environment is needed. If you want to see the fpt -i output then boot into dos and test it but I'm certain this system doesn't have AMT support. Personally I wouldn't mind seeing some pics from the dos MEInfo to be absolutely certain but 99% it's what I'm saying.

No, the chipset may be capable of AMT but the BIOS lacks any support for it including MEBx and other needed BIOS modules. Besides, even if you tried you would only end up bricking the system. I'll stick to what I said before: nothing related to ME driver or firmware can be performed on that system. If you want at some point to run the tools of the ME4 System Tools package, remember to use them under native DOS and not Windows (at least for flashing). That's all really.

It's built in the chipset, you can't see it. Different chipsets had different capabilities built-in. Before ME6, it wasn't obligatory to have the ME engine operational. At PCH and onwards it became part of the platform.

@ rootuser123:

Based on past experience, that is a BIOS/OEM issue and not related to ME. There is no option to disable FWUpdate at FIT either way (for Corporate it can be done through MEBx). Make sure you have the latest BIOS applied from Gigabyte (check for beta as well at tweak-town, stasio threads) and that you are using the latest FWUpdate tool (1191 as of now).

@ Skylake Users:

Be very careful which firmware you flash! FWUpdate does not check if you are trying to flash LP firmware over H or vice versa. If you flash the wrong SKU you will end up with a brick. Always double-triple check before flashing.

Other people had this issue in the past and only after applying newer BIOS versions did the problem go away. It's BIOS related, not ME. Either contact Gigabyte support or wait for them to fix it eventually.

@ error-id10t:

The driver has nothing to do with the firmware. And it's irrelevant to what I warned about above.

@ apoklyps3:

No, update your other system drivers like audio and the rest. Not relevant to ME firmware.

Just because it doesn't fix high DPC latency it doesn't mean it's useless. What you are saying makes absolutely no sense.