• Content count

  • Joined

  • Last visited

  • Days Won


greenhillmaniac last won the day on March 14

greenhillmaniac had the most liked content!

Community Reputation

92 Excellent

About greenhillmaniac

  • Birthday

Profile Information

  • OS
    Windows 8.1 x64
  • Country

Recent Profile Visitors

1,479 profile views
  1. 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
  2. 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.!ExhDEbDA!pUhzXKVp5-hgzvylW_btfQ
  3. 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).
  4. 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.
  5. 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...
  6. 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:
  7. Can Windows Update packages detect the CPU and block accordingly?
  8. Guess we already know how Microsoft is going to block Updates for Kaby Lake and Ryzen owners: with an update (how ironic!) 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.
  9. A bit of Google searching goes a long way
  10. Correct
  11. Great news, Windows 8.0 users: Server 2012 just got support extension to match that of Server 2012 R2!
  12. 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.
  13. 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
  14. Security Only Update: x64 x86 Monthly Security Update: x64 x86 Flash Player Update: x64 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
  15. 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.