5 ms·
I did not say Secure Boot causes this, the UEFI contains product key, and it does not allow to be deleted, modified or extracted. Since it is permanent there, W
by CSDude 13y ago
I did not say Secure Boot causes this, the UEFI contains product key, and it does not allow to be deleted, modified or extracted. Since it is permanent there, Windows installer fails to accept another key, or even a legitimate higher edition Windows installation.
- tanzam75 13y ago> I did not say Secure Boot causes this, Here's what you said: > Hear my fucked up story of UEFI, Secure Boot and Windows 8: Why mention Secure Boot at all? It's got absolutely nothing to do with your situation.
- CSDude 13y agoIt is a story about all of them, I did not say Secure Boot caused this problem, I said I disabled it to be able to install Windows 7.
- tanzam75 13y ago> It is a story about all of them, I did not say Secure Boot caused this problem, I said I disabled it to be able to install Windows 7. Suppose that a user buys a Windows 8 machine, goes to a website, and downloads malware that slows down the machine and makes it unusable. Finally, a local teenager wipes the machine, disables Secure Boot, and installs Windows 7. One would hardly say that this is a "f-cked up story of" malware, Secure Boot, and Windows 8. Secure Boot is merely incidental, and has nothing to do with the issue of malware on Windows 8.
- Spearchucker 13y agoNote that it is version-specific. I just flattened my Surface Pro 2 and used a non-OEM version of Windows, which required its own product key. Also, Windows 8 and 8.1 have different product keys, but if you upgrade OTA to 8.1 it will install the same SKU (OEM) for 8.1. Changing the OS is complicated with UEFI and secure boot, the usability is insanely bad, with a lot of boundaries being blurred. It's the worst experience I have ever had when installing a clean OS.