Installer fail - Fails to find correct clock speed

[BlueLineFive]

Just did all the latest available updates to my Windows 11 PC (as of 2025-02-24).

Went to install TurboTax 2024. The installer reports that the PC does not met the minimum requirements for clock speed.

However, it seem this is a bug introduced by the Windows updates as depending where I go to get the current clock speed of the machine, I get results of either 800 MHz or the actual running speed of 3.0 GHz.

How can I bypass the system requirements check of the installer so I can install the app?

[TurboTaxAniqua]

It looks like that there is an issue with the OS. we suggest Visiting  Windows Support for help updating your computer. 

Minimum requirements needs to be meet in order for a successful installation of the software.

Thanks for choosing TurboTax.

[BlueLineFive]

Thanks for the reply. Not sure where to swing the finger at this one.

Quick timeline. Purchased Turbo Tax 2024 from the Intuit on-line store in January 2025. Did not install the software. About mid-February 2025, updated the computer with all the latest Windows 11 updates. Then tried to install Turbo Tax from the package dowloaded in January. Install failed with the message "The Processor (CPU) on this machine is insufficient for running TurboTax. Please upgrade your Processor to one with 2GHz or higher, and then try to install again."

Long story short , seems as of the latest Windows 11 Updates, it now differentiates between processor “Base” clock speed and the actual running clock speed of the processor.

Installers now need to be aware that base speed cannot be used to determine current processor clock speed.  

I downloaded Turbo Tax again today from the Intuit site. This time the software did install so it seems Intuit found the problem and revised the Installer. The “This PC -> Properties” box still reports the clock speed as the Base speed, not the current running clock of the processor. "Task Manager -> Processor” reports both the Base and current clock, the latter is what is shown dynamically in the graph.

So kudos for Intuit for fixing the issue, but not sure why Microsoft chose to break the API that caused the issue in the first place.