Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×


  • Content Count

  • Joined

  • Last visited

  • Days Won

  • Donations


Everything posted by greenhillmaniac

  1. Since Microsoft decided to include the CPU blocking patch on all Security Only and Monthly Rollups for Windows 7 and 8.1, once again Windows 8.0 is verified as a great choice, free of meddling, as Microsoft proves it just doesn't care about its failed OS (in this day and age, that's a good thing).
  2. .NET Security and Quality Rollup Update (no telemetry AFAIK): https://www.catalog.update.microsoft.com/Search.aspx?q=4014982 KB4014563 is for .NET 3.5 KB4014557 is for .NET 4.5.2 KB4014548 is for .NET 4.6/4.6.1 KB4014545 is for .NET 4.6.2
  3. Yeah, I heard of the news. Frankly, I'll just keep installing the IE monthly updates, the Malicious Software Removal Tool and the Flash updates, without installing the Security Only updates for now. I'm adopting a @NoelC style approach of "If it ain't broke, don't fix it."
  4. Sure, here's a screenshot of my hidden updates: Most of these updates are Windows Update Client Updates from the Windows 10 Upgrade offer era, that are offered once you hide the July 2016 Rollup. Here's a list in text format: 2976978 3044374 3046480 3050267 3065988 3068708-(after hidding July Rollup) 3075249 3075853 3080149 3083325 3083711 3102812 3112336 3135449 3138615 3150513-(only if you install 2976978) 3161102- 3170735 3172614 3179574 3184143 3185279 Monthly/Preview Rollups (outdated with the March ones, but they are easy to hide) 3185331 3192404 3197874 3197875 3205
  5. My understanding of the issue is the following: Microsoft will continue to release security updates that are common to both Vista and Server 2008, but some that fix specific Server issues won't work. Also, to elaborate on the Powershell issue: Powershell 5.x was installable on Windows 8.0, because the .mum files inside the .cab, inside the .msu were NT6.2 agnostic (Basically, the .mum files have the info on which components to install, and they only required a x64 NT6.2 install). Powershell 3.0 on the other hand, had .mum files the required specifically Server 2008, and so a Vista inst
  6. https://msdn.microsoft.com/en-us/powershell/scripting/setup/installing-windows-powershell#BKMK_InstallingOnWindowsServer2008LH
  7. I would also go as far to say use 8.1 even if you don't like the modern "metro" aspect of it.
  8. Your best bet would be Abbodi1406 at mydigitallife. He was the one that made the script so Powershell 5.1 would install on Windows 8.0. I contacted him a few months ago, to get Powershell 3.0 on Vista, but he said it was not possible, because the individual packages were only Server 2008 compatible. Regardless, he understands a ton about Windows Updates in general, and would probably help us out.
  9. Starting this March, Microsoft separates IE updates from the Security Only updates, so you need to download the IE10 security update, yes.
  10. An update on the situation: AMD drivers are no longer Windows 8.0 compatible. Tested on 17.2.1. Everytime I tried installing them, it gave a BSOD. Tried different driver versions, all with the same error. RIP AMD cards on NT 6.2: 2012-2016 RIP AMD cards on NT 6.0: 2006-2015 RIP AMD cards on NT 5.1: 2001-2015
  11. A bit long overdue, but I updated the Windows 8.0 repository to include this month's Monthly Rollups, Security Only Updates, Flash Player and Internet Explorer 10 updates. I also included an updated timezone update in the extras and Powershell 5.1 (x64 only), complete with a script that extracts the update and installs its components, overcoming the Server 2012 only restriction. https://mega.nz/#F!ExhDEbDA!pUhzXKVp5-hgzvylW_btfQ
  12. If you'd like I can also create a Server 2008 updates for Vista repository on my Mega account... I think it will be more useful for Vista users, since 8.0 users have the Monthly Rollups, whereas Server 2008 still delivers updates the old fashioned way (that is, seperate KB for each update).
  13. Like Windows 7, you can hide all telemetry updates, as long as you have a list (like I do for 8.1). DiagTrack doesn't even show it's ugly face when I'm updating 8.1 systems. It's not an herculean task to stay private on 7/8.1, compared to 10, so my point still stands.
  14. Like I said in the post I linked, fades to black on UAC prompts will be slow, visual glitches, slow resolution change, and crash when trying to run WinSAT. Those are just some of of problems I encountered with an afternoon's worth of testing. I wouldn't recommend running Vista like this for anything. Who knows what else would be unstable... browsers with hardware acceleration, games...
  15. 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:
  16. Can Windows Update packages detect the CPU and block accordingly?
  17. 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 w
  18. 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
  19. 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!
  20. 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.
  21. 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
  22. 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-
  23. 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.
  24. 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
  • Create New...