I'm curious if the new updates will throw completely bogus error codes, like "0x800f081B CBS_E_UNEXPECTED_PROCESSOR_ARCHITECTURE". (similar to a bad overclock that causes random bit flips) Like I would expect if you managed to boot Windows 7 on a Pentium I!
IvyBridge not supported after April updates? I do not understand! I have got Intel Core i5 3570K processor and after installed April 2017 updates: KB4015549 and KB4014565 windows pop up and is saying that: "Unsupported hardware" Why, any idea? I thought that only 7th generation of Intel Core processors are not "supported".
Assembling a Intel Core i7 7700 7th Generation (Kaby Lake) on a Gigabyte GA-B250M-DS3H motherboard with Windows 7 Professional x64. After installing about 250 updates a warning comes out that is not compatible and I must switch to an operating system specially designed for the processor... Windows 10 of course! And that will not install important security updates, total lie, since it does not install anything else, including .NET Framework and Office 2010 updates. Anybody knows a circumvent like I heard: uninstalling april KB4012218, KB4014565, KB4015549 updates? Thanks.
Uninstall KB4015549 but the WU block will be included in all future Monthly Rollup updates and Security-Only updates
Yes, but can be done a hack that every month will unlock updates that do that, or that part of the update?
You can keep March Rollup KB4012215 installed then on patch tuesday, you uninstall the latest installed Rollup (currently KB4015549), which will unblock WU then install the new Rollup (i.e. May Rollup), which will block WU until the next patch tuesday and so on, repeat that each month
@abbodi1406 Hy HT well I don't can believe why M$ make this with millions of people's around the world that bought use of software and now the same users stay in this situation is inadmissible IMO I hope sincerely someday Linux or similar O.S. open source stay easy to all peoples make use and forget M$; only time can talk myself want to see
Is this method OK? 1, donwnload update patches using WHDownloader. 2. unpack msu to cab. 3. update using dism. forfiles /m *.cab /s /c "cmd /c dism /online /add-package=@path /norestart" you can apply all patches by one batch file?
Sure. MS has the right to refuse support for older versions of Windows, but people also have the right not to buy the latest hardware. In my mind, that avoids the problem completely. It also sends a strong message to both MS and the hardware makers. If the hardware makers lose business because of it, they'll be forced to push MS to support it.
I have just installed Windows 7 Pro x64 on my Ryzen 1600 system to test this hardware blocking feature. Continuously installed all windows updates to the point of it reporting my system up-to-date and having no more available. Optional updates (except for Skype) are all installed as well. Thing is, windows update still works. The block is nowhere to be found. All drivers are latest and installed, there's no hardware spoofing in place. It could detect my CPU and chipset (B350), if it wanted to. What's up? MS lifting the block? Code being so messy that it blocks old stuff and leaves Ryzen alone? Professional SKUs not being blocked? KMS-activated systems not being blocked? Systems installed on MBR disks not using UEFI boot being exceptions? I'm confused. Any news on this?