Windows 7 was released in 2009. It's not even a decade old. It's just 7 years old. We have never seen an OS losing support for new CPUs this fast. This is just Microsoft being anti-consumer.........once again.

"Just"? Look, when Windows 7 was released you only had GTX2xx/HD4xxx series, the best iPhone was the iPhone 3GS, Android was barely noticeable, the first Core i5 wasn't even released (one month later, and just one model)...man, that s*** was a long time ago 🙂 An OS should not be more than 4/5 years old, and we had to use Windows XP and Windows 7 for a bit more time because Microsoft failed to release better versions and Linux had poor gaming support. Myself, nowadays I just use Ubuntu but if i was using Windows, certainly was Windows 10 with Anniversary Update. I see no reasons to use Windows 7.

I agree, I hated Windows 8/8.1 .. and aside from all telemetry that Microsoft acquires, Windows 10 works very stable and beautiful. I assume that if you purchase a new PC all pimped up with a hardcore processor and nice GPU, you'll go Windows 10 anyway, even for DX12 support alone.

Yeah I wasn't a fan of Windows 10 initially but I've gotten somewhat accustomed to it and the weird ways it works plus MS changing things extensively between various major revisions of the OS. 😀 One thing that slightly annoys me is that you can't opt out of or even lower the telemetry stuff any more when on any of the insider branches including the release preview one, earlier it could be toned down a bit even if you could not turn it off entirely but now it's locked to full though thankfully the scans and such this then leads to as it does the data collection stuff and logging is done pretty infrequently but if you notice the User Experience Improvement related processes (Also forced on if on a insider branch.) or just rundll32 going on in the background and taking up HDD usage that's what it's doing though it should only take a few minutes. (And even as a normal user then as of the "RS1" / "build 1607" update and newer you can't disable it fully anymore - It did require group policy editing only found in the Pro edition though. - outside of the newly released server 2016 editions and possibly the corporate oriented enterprise variant of Win10, some other policies also saw a few restrictions like that.) As for CPU support I do not see how they would make them completely incompatible although support for newer processor extensions might not be 100% on older OS's and it might require the CPU/chipset software for a correct device name. (It's primarily just a collection of .inf files for component names and no actual .sys driver files - That's what the RST thing is for when using RAID. - so it's not entirely required but can be handy to have if the OS is a bit out of date and doesn't have them natively.)

Was about time. Old OS are being dropped from support and that's normal. If people want to stay in Windows XP and 7 it's their problem. This happens with every Windows version and ppl seem to forget just because they refuse to change OS. Move on people with 2016 and 2017 is near.

Really. It's not like MS is going to support any of the new features future processors will bring on old soon to be left to dust operating systems. It's wasted money it won't bring them new customers. Next step companies will move up to w10 or linux or whatever. They won't be using w7 forever. So the processors might work somewhat on older windows but not to their full potential. And of course there won't be proper drivers for anything that comes for the new platforms then.

It'd be nice if Windows 10 supported my rather expensive external soundcard, which it doesn't...

I guess it comes down to the manufacturer of said external soundcard? If its a niche item of course MS won't provide any tangible support for that. It's not like old soundcards are that supported unless the manufacturers have provided drivers.

I don't think this is new, even for Skylake it has new speed step code that is done on chip now and in window 10 there are power plans to support this handoff. I doubt win7 could just be patched by 3rd party, but it should work I imagine ,you just lose the new feature.

Instruction sets, and what basic identifiers Intel supports Microsoft and the Linux Foundation with. It's all kernel level stuff too in the OS, but if Intel and AMD tell the 2 that they will only support one set of operating systems, they'll comply easily. Look at OSx86. You cannot run a vanilla kernel on an AMD machine, you need an AMD compatible kernel.

It'd be nice if Windows 10 supported my rather expensive external soundcard, which it doesn't...

I think you can blame that on whoever made it not windows 10. 🙂

Just because it is not officially "supported" doesn't mean windows 7 won't work, just won't be able to complain if you have problems. Just a clever way to trick everyone into buying new windows 10 licenses.

Maybe they are removing some legacy instruction sets/extensions that are required only by older windows versions? Just guessing.

Move to cripple steam OS I reckon?

What does MS not supporting new CPU's on old Windows OS's have to do with steam OS?

that just shows how much MS values its customers.. after all, windows 8.1 is still in mainstream support until january 2018. -andy-

I see no reasons to use Windows 7.

I see one big reason - many of old games doesn't work under Windows 10. Why should I abandon this games because Microsoft can't handle backward compatibility? :3eyes: Even if I move on to Windows 10 for DX12 games I would leave partition with Win7 installed.

I see one big reason - many of old games doesn't work under Windows 10. Why should I abandon this games because Microsoft can't handle backward compatibility? :3eyes: Even if I move on to Windows 10 for DX12 games I would leave partition with Win7 installed.

Which of the all old games do not work. Btw you could always have a virtual machine for the said old games also. I know some of the cd games simply refuse to work. I had some that thought windows 10 is simply too old because they were programmed with specific windows in mind.

They still will support Linux so M$ can eat crow!

It looks to me like MS is trying to copy Apple in business practices which isn't really a good thing. supposedly Google is working on a new operating system . really hope it is true .

How did you come to that conclusion when it works on non MS operating systems.

That would be bad news for the guys still on Windows 7 looking forward to an upgrade.

Uh... why, exactly? If you're on a PC still using Windows 7 that isn't using a CPU older than Core2, what's stopping you from upgrading that PC to Windows 10, grabbing the serial key, and then installing Windows 10 directly on a new PC? Sure, it's an inconvenience. But if you intend to run Windows 10 on a brand new PC but you're starting off upgrading from Windows 7, you're already off to a messy start. Also just to point out, Linux != Unix. Linux is Unix-like. That being said, to my knowledge, there is currently Linux support for Kaby Lake and Zen, but I'm not sure what the current state is for OSes like the BSDs or AIX. To my knowledge, FreeBSD is currently working on supporting Kaby Lake and I haven't found any evidence that it supports Zen at all. As stated by other people in this forum, I'm sure these processors will still work on older OSes, but in terms of official support by participating companies, that can only be said by Windows 10 and Linux (and probably Mac).

Just in case a lot of people didn't get it, Microsoft and the Linux kernel maintainers have decided that they will not backport support for Kaby Lake and Zen to previous kernels. That's it, and it's the correct decision technically. AMD and Intel have no real say in this. SteamOS uses the Linux kernel, so the same rules apply. Basically, whatever OS you're using, you have to make sure you have the latest version for it to properly support the latest hardware. Despite popular belief, CPUs require drivers to perform and function properly. These drivers need to be written and maintained and since Microsoft has moved into a rolling release model (like the Linux kernel has since the beginning), there is no backporting.

This wouldn't bother me at all if Microtard hadn't "accidentally" limited dx9 vram to 4GB in W10.

This wouldn't bother me at all if Microtard hadn't "accidentally" limited dx9 vram to 4GB in W10.

It's not a Windows 10 issue. It also happens in Windows 7 and 8.1. It's a combination of driver/dx9. The author of ENB explains it at the NVIDIA forums.

Hello I've got some statistics from users which shows that a lot of them have 4Gb video memory limit for DirectX9 applications (dx11 is okay), even Titan videocards. Can't find dependency why this happen, same OS (win7, win8, win10), almost same videocards and drivers, but part of them have 4Gb, others proper amount equal or bigger than physical VRAM size. Problem actually consist from two parts, first is limitation of real VRAM and second is available fake VRAM, which is summ of physical VRAM and some amount of RAM which driver can allocate and use (in old terms these are local and non-local VRAMs). Fix of the problem is very simple and do not require much effort from driver developers. Games which use own streaming of textures and vertices (instead of managed by d3d) will run much smoother and faster, first of all these games are Fallout and Skyrim heavily modded with streaming made by me. PS: please, no silly things about 32 bit limit here, amount of available video memory can be tested by my VRamSizeTest, it allocates RTs till fail creating new one.

PS: Words like Microtard and Crapple have stopped making people sound cool since the mid 90s.

I see one big reason - many of old games doesn't work under Windows 10. Why should I abandon this games because Microsoft can't handle backward compatibility? :3eyes: Even if I move on to Windows 10 for DX12 games I would leave partition with Win7 installed.

What old games? I have yet to find a single game that doesn't run fine on Win 10. I can even still play old DOS games on Win 10.