greenhillmaniac

Finally... Just finished compilling 328 unreleased hotfixes for Windows 8.0 x64! Any interest in me releasing these files publicaly?

Another interesting hotfix not released in WU for 8.0 https://support.microsoft.com/en-us/help/3002653

I've been delving into the world of Windows 8.0 hotfixes, which basically are updates that fix very specific issues that Microsoft didn't issue in Windows Update, that got released in the timeframe of 8.0's release up until the beggining of 2016, and I discovered a very interesting one: https://support.microsoft.com/en-us/help/2929742 Lol, gramatical error on a KB article Anyway, if you apply this hotfix and put a registry key that they describe in the article you could reenable verbose BSOD just like in Windows 7 and earlier! This hotfix also exists for 8.1, but got bundled in a security update that was released in Windows Update, so everybody running 8.1 already has this possibility.

The only usable version of Windows 10 that exists is the Server 2016/LTSB 2016 variant because (you've guessed it) it had almost 2 years of constant patching. Those versions don't have any UWP processes or telemetry (if tweaked properly) running in the background. They don't suffer from annoying bugs, like basic Windows mouse functions being completely bugged out (7-Zip and even regedit suffer from this in the latest 1803 version)! These kinds of basic usability bugs never seem to get caught by Microsoft unless someone explicitly makes a fuss of it on social media (and even then...) When even Windows can't implement the Windows API properly you know something's f***ed: https://sourceforge.net/p/sevenzip/discussion/45797/thread/e730c709/

Even with 7 and 8.1 where Microsoft implemented the CPU block, all it does is display a nagging message saying the CPU is unsupported and stop you from updating from Windows Update and .msu files. You can still install updates from extracted .cab files with Dism and additionally use these community tools to circumvent the artificial block: https://github.com/zeffy/wufuc https://github.com/p-lider/WuaCpuFix

Don't worry what Microsoft says... I managed to get my AMD Ryzen 5 1600 working on Windows Vista and also installed Windows 7 on my Kaby Lake laptop just fine! What you really need to figure out is if you're OK with using (supposedly/allegedly) unsupported hardware on "old" OSes. I know I'm fine with it, as the few advantages Windows 10 brings are outshined by its incredible number of bugs, bloat and overall user unfriendliness. That's just my take on it... From my experience, new CPUs have the same performance on Windows 7/8 as they do in 10. The thing that will make it or break it are really the drivers. I know that Kaby Lake has GPU and chipset drivers fully compatible with 7 and 8.0/8.1, but I haven't researched Coffee Lake.

Since Windows 8.0 has such a pitiful marketshare and is technically not supported, Microsoft decided not to port the CPU block for NT 6.2 OSes (no unsupported CPU popups for 8.0 ). Technically, Kaby Lake and Coffee Lake should be compatible if you have the drivers for it (if you search the internet you're bound to find something).

They're not as experienced as Microsoft

Small repository update. Just happened to stumble upon KB3118401 for x86 Windows 8.0. If you didn't know, this update only appeared for Server 2012 on the Microsoft Catalog, which is only x64, but on the mydigitallife forums someone linked to a Microsoft Download Center link with a zip containg the update in x86 and ARM form. This update is needed to install Visual Studio 2015 and 2017 redistributables, since it includes Windows 10's Universal C Runtime (the only backport Microsoft ever did since 10's release I do believe). The update is in the same place as its x64 counterpart, in the "Extras" folder. https://mega.nz/#F!ExhDEbDA!pUhzXKVp5-hgzvylW_btfQ BTW - the Microsoft Download Center link for the interested: https://www.microsoft.com/en-us/download/details.aspx?id=50410

And finally, the often forgetten Windows 8.0 Replaced Monthly Rollup with KB4284855; Replaced the Flash Player update with KB4287903; Replaced the Internet Explorer cumulative update with KB4230450; Added the previous month's Security Only update, KB4284846. Have a good one https://mega.nz/#F!ExhDEbDA!pUhzXKVp5-hgzvylW_btfQ

Greetings from the underworld Finally got some time to update the repository, so here goes: SECURITY - ("6 - June 2018" Folder) KB4093227 - Description of the security update for the Windows Remote Desktop Protocol (RDP) denial of service vulnerability (v2 of April update) https://support.microsoft.com/help/4093227 http://catalog.update.microsoft.com/v7/site/search.aspx?q=4093227 KB4130956 - Description of the security update for the remote code execution vulnerability https://support.microsoft.com/help/4130956 http://catalog.update.microsoft.com/v7/site/search.aspx?q=4130956 KB4230467 - Description of the security update for vulnerabilities https://support.microsoft.com/help/4230467 http://catalog.update.microsoft.com/v7/site/search.aspx?q=4230467 KB4234459 - Description of the security update for the Windows kernel information disclosure vulnerability http://support.microsoft.com/help/4234459 http://catalog.update.microsoft.com/v7/site/search.aspx?q=4234459 KB4294413 - Description of the security update for the HIDParser elevation of privilege vulnerability http://support.microsoft.com/help/4294413 http://catalog.update.microsoft.com/v7/site/search.aspx?q=4294413 NON-SECURITY - ("Extras" Folder) KB4039648 - Update to add SHA-2 code signing support (updated with x86 support) https://support.microsoft.com/help/4039648 http://www.catalog.update.microsoft.com/Search.aspx?q=KB4039648 KB4090928 - Windows leaks handles in the lsm.exe process and smart card applications may display "SCARD_E_NO_SERVICE" errors (only apply after update KB4056446) http://support.microsoft.com/kb/4090928 http://catalog.update.microsoft.com/v7/site/search.aspx?q=kb4090928 KB4130978 - Time zone and DST changes in Windows for Morocco and the West Bank and Gaza https://support.microsoft.com/help/4130978 http://www.catalog.update.microsoft.com/search.aspx?q=4130978 INTERNET EXPLORER - (Root folder of x86 or x64) https://support.microsoft.com/en-us/help/4230450 http://catalog.update.microsoft.com/v7/site/search.aspx?q=KB4230450 That will be all. Cheers https://mega.nz/#F!txxRyLzC!1vBMGzMHiL864f3bl1Rj1w

You could always switch to the Security Only updates... Just install the Monthly Rollup for December, avoid any January updates and then continue patching with Security Only patches. This guarantees that you keep your system safe without any Meltdown/Spectre fixes

Mega must've removed your files, because it says they're not available anymore from your download link. EDIT: It's now working.

So you're linking Tweaks made by you from another forum that requires registry to access the file(s)? Couldn't you just place them here directly?

Honestly, I think it's good news... No performance loss for Intel CPUs on NT 6.2. Another plus for me

Windows 7 doesn't include Hyper-V in any of its editions. To get it you'd have to install either Server 2008 R2 or any Windows version past 8, Pro edition.

Unless someone actually manages to port the OneCore API Windows 10 uses for its apps (along with WinRT for Windows 8.x apps), no, it's impossible to run any Windows 10 apps on anything NT 6.x (I think it's kind of a blessing, really )

They until October 2016. From October until January 2016 you have to install the individual updates (that I have on separate folders in my repository).

I think those are the patches that Microsoft would release today, if not for the whole CPU exploit debacle. Unless you have an old AMD system (with an Athlon 64), you should be clear to install them.

Small repository update. More updates probably coming on Patch Tuesday: Updated Monthly Rollup Update to KB4056896; Added Security Only Update KB4056899 and updated IE10 Cumulative Update to KB4056568 (only on x86. Microsoft only provided the January IE10 update to Server 2012 so far). I'd also like to mention that these updates don't fix the recent CPU exploits, as mencioned on Microsoft's own article: https://support.microsoft.com/en-us/help/4072698 so they should be safe to install.

Updated the repository with 3 months of updates, including: All of the updates mentioned by @Ruan for November 2017, December 2017 and January 2018; Updated Extras folder with a better description of each update on a readme.txt file, a new timezone update and a dedicated folder for the .NET Framework 4.6.1 installer; Updated the readme.txt file at the root of the repository with updated info; Removed every superseeded update in the repository (from each month... It was a lot of manual labor). https://mega.nz/#F!txxRyLzC!1vBMGzMHiL864f3bl1Rj1w Should be all. Vista lives on for another month

@Ruan do you know if there's a new website for the updates released in 2018? I only have a link for the ones released in 2017: https://support.microsoft.com/en-us/help/894199/software-update-services-and-windows-server-update-services-changes-in

I found the following articles with a bit of DuckDuckGoing. For the lockscreen issue: http://www.grouppolicy.biz/2012/11/how-to-use-group-policy-to-change-the-default-lock-screen-image-in-windows-8/ https://techjourney.net/disable-lock-screen-in-windows-10-8-1-windows-server-2016-2012-r2/ For the default account picture: http://www.thewindowsclub.com/set-a-default-user-logon-picture-for-all-users

The ones of changing the INF file with those older entries and replacing the coinst17_30 dll?

Just tested @Tripredacus's suggestions, but they didn't work... I'm still convinced there's something going on at a sys file level that's keepign these drivers from installing, be it explicit Windows 8 blocking or just implicit code that prevents the installation by messing with the dxgkrnl.sys. Just tested with the recently released Crimson 17.12.1, but still got the same error. If anybody has the knowledge to debug drivers and check what's causing the BSOD please post here or PM me.