Instalar Steam
iniciar sesión
|
idioma
简体中文 (Chino simplificado)
繁體中文 (Chino tradicional)
日本語 (Japonés)
한국어 (Coreano)
ไทย (Tailandés)
български (Búlgaro)
Čeština (Checo)
Dansk (Danés)
Deutsch (Alemán)
English (Inglés)
Español - España
Ελληνικά (Griego)
Français (Francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (Húngaro)
Nederlands (Holandés)
Norsk (Noruego)
Polski (Polaco)
Português (Portugués de Portugal)
Português - Brasil (Portugués - Brasil)
Română (Rumano)
Русский (Ruso)
Suomi (Finés)
Svenska (Sueco)
Türkçe (Turco)
Tiếng Việt (Vietnamita)
Українська (Ucraniano)
Informar de un error de traducción
LA Noire works just fine under Win7, 8, 8.1, 10 ... 64bit
Many simply leave all the defaults enabled in Win10 which is just wrong for a gaming PC.
Disable Cortana, Xbox and Game Capture, Game Mode, Full Screen Optimization, and set Games to ignore DPI Scaling options.
Changing TDR settings is a must also because these are set too low in Win8 and 10
Idk about way better a bit of a stretch. But it's basically looks like a revamp of W10 IMO with new skin.
I imagine there will be more holdouts than otherwise simply due to the TPM 2.0 requirements, although in 2025, Coffee Lake and second generation Ryzen will be like looking back on Haswell now (old, but still usable, so I do disagree with cutting them off but it will be old enough by then that most people will have moved on). Were it not for this, I imagine Windows 10 would be replaced about as fast as Windows 8/8.1 was, because it's just another Windows 8 with a new wrapper, like Windows 10 was, and it is a free update. But as it is, there will also be hardware reasons preventing upgrades, so this will likely keep Windows 10 rather relevant until around its end of support date, and even beyond, like Windows 7, though for totally different reasons.
Strangely one day it just started working which I put down to W10 but a lot of people have issues getting it to launch on W10
Which was my point that it’s always impossible to say what will work and what wont after an OS change.
It's not using the Win10 kernel. This new MS team came up with Win11 because much of the Win10 kernel source code was leaked. This allows basically every weakness and backdoor of Win10 to be public. So using an older kernel is simply not going to work moving forward. Just because some old visuals still remain doesn't mean it's a rescinded Win10. For example, things like the WINVER screen. As there was simply no reason to change such things.
Well I'm running the Win11 insider build since release day as a clean install. Even on a system without UEFI or TPM it works way better then 10 ever has. And I've taken the time to.load it up with all sorts of drivers and app, startup apps and background processes. Win10 is like Vista in comparison to 11
I need to correct my post above.
It's not using the Win10 kernel. This new MS team came up with Win11 because much of the Win10 kernel source code was leaked. This allows basically every weakness and backdoor of Win10 to be public.. [/quote]
I referred to Solarwinds before. Hence the heightened hardware security which is enforced to the end-user. Did they re-write the entire kernel? I think not. I do think more changes will be introduced gradually as Windows 11 evolves. Edit: if you disable PTT/TPM and Secure Boot, does your Windows 11 still run?
Too much change to the kernel will render a lot of software not yet tested on Windows 11 to now be incompatible with it. You don't want to shoot yourself in the foot too early.
https://en.wikipedia.org/wiki/Kernel_(operating_system)
Re-edit: altering a Windows 11 ISO to run without TPM check for example involves swapping a Windows 10 .dll for the Windows 11 one. That's not at the kernel level. But like I said, more to come no doubt.
Far as anyone can tell at least with insider build doesn't seem to be any issues using much older hardware but that can change at any point when MS want to cause issue, and I doubt RTM will be the same if MS goes out of their way to blocking all possible methods, or even far as adding new checker that cause problems, but that be little extreme if MS goes that far just because someone wasn't using TPM, or secure boot which shouldn't be base on the functionality of the OS.