Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

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. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


greenhillmaniac

Member
  • Content Count

    397
  • Donations

    $0.00 
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by greenhillmaniac

  1. .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
  2. 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."
  3. 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 3205401
  4. 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 install was impossible (update hacking only goes so far). Actually, I've tested this, and .NET Framework 4.6.1 installs just fine on Vista. No errors whatsoever (I haven't tested .NET Framework 4.6.2, but I assume it's the same).
  5. https://msdn.microsoft.com/en-us/powershell/scripting/setup/installing-windows-powershell#BKMK_InstallingOnWindowsServer2008LH
  6. I would also go as far to say use 8.1 even if you don't like the modern "metro" aspect of it.
  7. 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.
  8. Starting this March, Microsoft separates IE updates from the Security Only updates, so you need to download the IE10 security update, yes.
  9. 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
  10. 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
  11. 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).
  12. 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.
  13. 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...
  14. 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:
  15. Can Windows Update packages detect the CPU and block accordingly?
  16. 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.
  17. 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
  18. 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!
  19. 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.
  20. 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
  21. 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
  22. 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.
  23. 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
  24. 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
×
×
  • Create New...