Novice Mac users should not use this application. This utility is truly only intended for advanced users, if you are not comfortable with the idea of modifying kernel extensions and the ramifications of that, using uncertified third party software, nor the idea of intentionally slowing down a Mac by disabling hardware features, this is not for you. The utility will load and unload kernel extensions to force TurboBoost to be disabled or back to the enabled default state through user interaction with a menu bar item. You can for sure use one for browsing the internet (I use mine to view Twitch while working) but it’s segregated on its own subnetwork using firewall rules, so no matter, if it gets popped there, is nothing on it and the attacker won’t be able to see my other devices on the network.To accomplish this task, we’ll use a third party Mac tool called “Turbo Boost Switcher for OS X” that is compatible with OS X El Capitan but not MacOS Sierra (yet), this app also requires a modern Mac CPU like a Core i5 or Core i7. Obviously, there are some major drawbacks in doing this, firstly both the device and OS are EOL (End of life) so neither is receiving security updates any longer, so if you have a surface pro 4 and are using it to browse the internet and do banking etc I would upgrade to a newer device before your device gets popped by an attacker. I had issues with overheating and screen filker when I picked up my old Pro 4 and the previous owner had installed 21H1 on it, reverting back to the original 1507 fixed all my issues and gave me the ability to change the CSEnabled settings in the reg. The reason most of you Pro 4 users are experiencing issues with power optimisation or overheating is that the OS build you are using is probably not designed for a legacy device like the Surface Pro 4. Reverting back to the last support version of Windows will most likely fix your issue, the Surface Pro 4 was designed to only support Windows 10 version 1507, build 10240 (year 2017). For Surface Pro 4 users (And all legacy device users I suppose), the solution is to revert back to the final support version of Windows 10 for your model.
0 kommentar(er)
