greenhillmaniac

If you edit the INF file to have your hardware ID and to remove the block on Vista, it might work, but stability won't be great. See my post on this issue:

Can Windows Update packages detect the CPU and block accordingly?

Guess we already know how Microsoft is going to block Updates for Kaby Lake and Ryzen owners: with an update (how ironic!) https://support.microsoft.com/en-us/help/4012218/march-2017-preview-of-monthly-quality-rollup-for-windows-7-sp1-and-windows-server-2008-r2-sp1 https://support.microsoft.com/en-us/help/4012219/march-2017-preview-of-monthly-quality-rollup-for-windows-8-1-and-windows-server-2012-r2 If we go to Windows 7 and 8.1's update history page, both these March preview updates have one line in common: "Enabled detection of processor generation and hardware support when PC tries to scan or download updates through Windows Update." So, from now on, owners of new CPUs need to only install Security Only updates and stear clear of the Monthly Rollups. EDIT: Once again, Windows 8.0 users are the lucky ones, since Microsoft doesn't give a frick about NT 6.2, they didn't include this "feature" in the March preview update for Server 2012.

A bit of Google searching goes a long way https://support.microsoft.com/en-us/help/3123303/the-new-end-of-life-upgrade-notification-for-internet-explorer

Correct

Great news, Windows 8.0 users: https://support.microsoft.com/en-us/help/4015079/lifecycle-dates-extended-for-windows-server-2012 Server 2012 just got support extension to match that of Server 2012 R2!

What's your main card? You can copy the x86 patch files to the SysWOW64 folder. If you go a few posts below he also made a x64 patch.

https://support.microsoft.com/en-us/help/22811/windows-server-2012-update-history The monthly rollup contains all updates released from October till now. Since there was no Patch Tuesday in February, and nothing for Server 2012/8.1 in January, the rollup only includes this as new: "Addressed issue that leads to a read I/O latency of > 70 milliseconds when the disk commit exceeds 90%, < 16 GB commit available, and the paging file is at its maximum size." Plus the fixes from other months: Addressed issue where you can’t change the system time if the RealTimeIsUniversal registry entry is enabled in Windows. Addressed issue where event logging fails to log the IP addresses of incoming Remote Desktop Protocol calls. Updated Belarus’ ISO 4217 code from BYN to BYR. Addressed issue where a cluster fails to form or nodes fail to join a cluster if the cluster database contains duplicate network or interface entries. Addressed issue with the boot partition appearing in File Explorer after installing MS16-100. Addressed issue where external authentications through the Active Directory Federation Services (ADFS) Proxy role start failing after renewing the token signing certificate. Addressed issue that causes high CPU usage whenever a significant number of files are opened simultaneously and folders are being renamed. Addressed issue with revised daylight saving time. Addressed issue where some DFS namespace reparse points that are in the DFS server’s root share are unexpectedly deleted during a full synchronization with the Primary Domain Controller (PDC). Improved the reliability of Windows Kernel. Addressed issue that prevents pushed-printer connections and printer connections from trusted servers from being installed in Point and Print scenarios after installing MS16-087. Addressed issue when a cluster node sends an Internet Control Message Protocol (ICMP) request to a gateway, TCPIP returns a timeout error (Error code 11010, IP_REQ_TIMED_OUT), even if ICMP doesn’t receive a timeout. Addressed issue with incorrect character mapping between the 932 code page (Japanese Shift-JIS) and Unicode. Addressed issue that required users to wait up to 30 seconds after booting-up, before the device was available and ready for use. Addressed issue that prevents the automatic deletion of old Dynamic Host Configuration Protocol (DHCP) backup files—Extensible Storage Engine (ESE) transaction logs. Addressed issue that caused Cluster service on remaining nodes to stop unexpectedly when a failover cluster node experiences a power outage. Addressed issue that causes a NFS service to stop responding on a two-node Windows cluster deployment, affecting clients to not be able reach an NFS share. Addressed issue after installing KB3146706 that causes Office 2010 to stop responding when Enhanced Mitigation Experience Toolkit (EMET) is enabled. Fixed issue that may cause backups to not work because it appears there isn't enough disk space on the target volume, even when there is enough space for the backup. Addressed issue in Microsoft Secure Channel (SChannel) that sometime causes Transport Layer Security (TLS) 1.2 connections to fail depending on whether the root certificate is configured as part of the certificate chain for server authentication. Extended support of the Key Management Service (KMS) for Windows 8 and Windows Server 2012, in order to enable the activation of clients running Windows 10 Anniversary Update-based long-term servicing branch (LTSB) and Windows Server 2016 clients, when they become available. I don't think Microsoft includes telemetry in these, since Server 2012 is supposed to be light (and they don't give a s*** about NT 6.2 users)... Give it a shot, if you'd like

Security Only Update: http://download.windowsupdate.com/c/msdownload/update/software/secu/2017/02/windows8-rt-kb4012214-x64_b14951d29cb4fd880948f5204d54721e64c9942b.msu x64 http://download.windowsupdate.com/c/msdownload/update/software/secu/2017/02/windows8-rt-kb4012214-x86_5e7e78f67d65838d198aa881a87a31345952d78e.msu x86 Monthly Security Update: http://download.windowsupdate.com/d/msdownload/update/software/secu/2017/03/windows8-rt-kb4012217-x64_96635071602f71b4fb2f1a202e99a5e21870bc93.msu x64 http://download.windowsupdate.com/d/msdownload/update/software/secu/2017/03/windows8-rt-kb4012217-x86_6be56af67587060cb0e48c5f9f2b563736d4f866.msu x86 Flash Player Update: http://download.windowsupdate.com/d/msdownload/update/software/secu/2017/03/windows8-rt-kb4014329-x64_92ffd222695c3c3f8541ce409acd5b67b9c3e186.msu x64 http://download.windowsupdate.com/d/msdownload/update/software/secu/2017/03/windows8-rt-kb4014329-x86_6ecfb692d9b467357fc12f3a424f8bab67017c15.msu x86 Now the update convention is KB4XXXXXX. Interesting. These seem to be all updates available for the NT 6.2 line of OSes. Let me know if there are any more updates. Paging @JodyT for testing

I searched for updates on my Windows 8.1 Kaby Lake laptop this Sunday, and it worked just fine... Maybe they only applied that today.

https://support.microsoft.com/en-us/help/4012982/discusses-an-issue-in-which-you-receive-a-your-pc-uses-a-processor-tha So this is how they are gonna stop support on newer processors... Artificially make Windows Update not give updates. Gotta say, expected worse

LinusTechTips is just a bunch of clickbait videos with technology as their main theme. Most of the videos they make have no substance. One good thing this video prooved however, is how competitive Windows 7 still is, compared to Windows 10, in some of the benchmarks. Also, that Windows with no telemetry and magical good performance he mentions already exists. It's called Windows 8.1

There is a problem with this... Once the Windows 7 giant falls, we will fall with it. AMD already discontinued 32 bit Windows 8.1 support, stating the user count was too low to invest in such an effort. I fear for the future.

It's perfectly normal that most games that list 7 as a minimum still work on Vista, since both have DirectX 11... As an example: http://steamcommunity.com/app/208650/discussions/0/615086038677678684/ "Hey you all, guess what, it (Batman Arkham Knight) DOES work on vista. I'm running it on a vista, and it works amazing. Well the only main problem is my 4gb memory. Upgrading it in a bit. My computer has Intel Core i3, 4gb Memory, Nvidia GeForce GT 740, and Operating System Windows Vista."

On a side note, people are more interested in this thread for the Edge removing script, than to help the poor OP on restoring it

I would say that is a plus But seriously, what was in that script? Could you do a copy paste of it? I can't give much of an advice with that vague description alone...

People were much more willing to s*** on Windows 8 when it was new vs 10 now IMO

Curiously, I've had the opposite experience with Windows 10... Random bugs like Explorer crashing for no reason, the HDD going to 100% usage because of Microsoft Compatibility Telemetry Agent... Also, I would argue that the Windows 10 UI is worse than 8.1's. First of all, you have the weird mix of the Settings app and Control Panel, where some settings are in one, and some are in another. In 8.1, the Control Panel does it all (aside from changing the Picture of your account and lock screen). Then, you have the Metro apps that try to replace the regular Win32 counterparts, whose design is so big and adapted to touch, it makes it a pain to use, with no Context Menus, huge mouse movement to reach certains parts of the app that should be readily available and no keyboard shortcuts. I'm happy with my Windows 8.1 Pro with Media Center. I would argue that Bash for Windows is a plus on Windows 10 (the only one, honestly), but Vmware's Unity mode does the job for me.

The Control Panel is not gone. They just replaced the shortcut on the Win+X menu from the Control Panel into the Settings... This almost reminds me of the fake reports that CMD was gone from new Windows 10 builds, because they replaced certain shortcuts to Powershell. I know Windows 10 is bad, but not even Microsoft would do that

Atleast you can still use your GPU with Vista... Anything newer than the RX 2XX series won't work properly (such as my card)

Yup, Windows 8.x are still in December's update batch... like said earlier, you can't perfect perfection

Another first: https://blogs.technet.microsoft.com/msrc/2017/02/14/february-2017-security-update-release/ Patch Tuesday delayed!

It's built in, but you can disable it in the "Disable Windows Features" option on the control panel:

Be warned that I haven't been able to successfully install the Intel HDMI drivers on Windows 7. Perhaps with a bit more search it would be possible, but I've changed to Windows 8.1, as it suits my needs a bit better. The laptop model is a HP 15-ay105np, with a custom shop configuration to have 8Gb of DDR4 RAM: http://support.hp.com/us-en/document/c05326875/?openCLC=true

Don't be fooled. Check the INF file. They most probably have the Kaby Lake hardware ID only on the Windows 10 section.