I'm having the similar problem with a new system.
I've tried to uninstall and reboot but the driver re-installs itself every boot.
In the BIOS there is an option for AHCI or RAID but that's the closest I can find and neither work.
I have an NVMe M.2 and a mechanical HDD but no optane memory.
Motherboard and processor are compatible but the error comes up every login.
Any other possibilities without having to dive into the registry or polices would be appreciated.
You should never "dive into the registry or policies:.
What operating system? Windows 10? What version? 1809?
What is your processor model number?
Are you a laptop or a desktop? What model number and manufacturer?
I was forced to reinstall windows 1903 due to botched software from ASUS and TBM was installed by default. I uninstalled the program and it's not showed back. Will you please inform me when you closed up the security issue about accessing the hardware directly?
So far still no luck. When I installed the prior version it came back with an install failed error message. I'm using the latest BIOS on a ROG STRIX x299-e gaming motherboard.
I've also tried to disable the turbo options in the BIOS and see if I can uninstall it after that, but that didn't work.
When I try to uninstall the application I get this:
Followed by a reboot prompt. Which brings us back to the questions, what is the purpose of ITBM and why can't I remove it?
Also why is it so far into the system?
I've disabled the service (ITBM) then rebooted and still that boot-up message shows after login.
I have troubling feelings between software and hardware having such a security vulnerability.
wrtechnopath, Thank you very much for your response.
Based on the picture, as you mentioned previously, we can confirm that the latest BIOS version is already installed in your computer.
According to the information that is showing on their forums support, in the link provided previously, there are some BIOS versions that will not work properly with the Intel® Turbo Boost Max Technology, since ASUS is also the one the provides the driver for this feature and they can customize the features and functions on their devices as well as the BIOS settings, we recommend to get in contact directly with them to check if maybe there is a fix or another BIOS version or driver needed to address this problem:
Additionally, there are some reports stating that the problem is actually related to the Windows* version being used because the problem does not happen with some other Windows* builds.
So, as an option, you can always get in contact with Microsoft directly to verify and confirm that information and to check if there are further suggestions on this topic.
Intel Customer Support Technician
Under Contract to Intel Corporation