If you were to switch from your 2015 Pro to the M1 MacBook (even the Air), it will feel like a whole new World. Only the existence of AMD's Ryzen CPUs made Intel add more Cores (13" got 4 Cores, 15" got 6 and 8 Cores). Core count was the same, so was CPU-Benchmark numbers. Intel made basicly almost 0 progress from 2015 to 2017. The M1 compared to Intel's 2020 Chips (10th Gen IceLake) was a bigger progress, than what Intel did in the last 5 Years. To answer that last question, i dare to say: Otherwise, wait for the M1x chip mid 2021~, and see how Apple Silicon develops. Unless you want to satisfy your "new toy syndrome". However: I personally would not upgrade, if the 2015 model still does anything you need. a Macbook Pro 16", it's only natural, that it would completely destroy any 2015 Macbook Pro in terms of Performance. So, to answer the original Question in this Post: Since the M1 already beats the 2020 Pro models, even trade blows vs. Still: Both of them would be far behind an M1. 15" was a pretty good difference, and the 15" with Quad-Core CPU would still be quite useable today, compared to a Dual Core model.# I’m more concerned with the fact that shutting these things off never occurred to them as something you might want to do without this level of effort.The 13" Pro only had access to a Dual Core, while the 15" not only had a Quad Core, but also a dedicated GPU. MID 2015 MACBOOK PRO WINDOWSI could gripe about the ever-evolving relocation of settings but if you’re shocked by this then you haven’t been using Windows long enough. I also had to edit the registry twice and implement yet another github sourced hack to get the taskbar, start menu, and context menus back to working the way they had in the past. However, I’m not going to lie about my experience a mere two days into the test drive. MID 2015 MACBOOK PRO HOW TOI then learned how to install rEFInd from Windows and solved the second piece of this puzzle. It turns out there’s a flag in rEFInd in the config file called ‘enable_and_lock_vmx’ that when uncommented and set to ‘true’ will resolve the issue. I’ve never liked BootCamp and in the past I’ve always relied on the rEFInd boot manager available here : and casually dealt with the odd occasion that virtualization wouldn’t work in Windows because a reboot would usually sort it out.Īs I wasn’t expecting to be dual-booting for the time being, I did not have rEFInd installed and spent a ton of time Googling the answer (which was always resetting the NVRAM or BootCamp or both). The traditional route would be to dual-boot macOS and Windows 11 using BootCamp and BootCamp will set the proper flags in the NVRAM. The problem here is that the NVRAM doesn’t enable hardware virtualization by default and no amount of resetting it will make it so. Crisis averted for now … until I wanted to start installing the additional Windows features required for WSL and found them greyed out. or a used 2017 macbook air 1.8 GHZ i5 8gb for 540 dollars. The tool was dead simple to use and Windows 11 not only installed but updated as well with no issues. Is the 2015 Macbook pro still worth it in 2021 I can grab a used 15 inch mid 2015 macbook pro with 2.5 GHZ i7 16gb and radeon graphics for 700 dollars. This required a visit to for a workaround to create installation media as the Microsoft-provided fix will only allow you to install if you have TPM v1.2 and this generation of Macbook has no TPM at all. 2.0) to pass the hardware checks to install Windows 11. Unfortunately, the laptop is too old to have a compatible Trusted Platform Module (TPM v. I decided I wanted to test out Windows 11 from a clean install as well as the improvements to the Windows Subsystem for Linux. I happen to own a 13″ Macbook Pro from 2015 (i7, 8GB, 256GB SSD) as my daily driver.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |