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

    378
  • Donations

    $0.00 
  • Joined

  • Last visited

  • Days Won

    3

greenhillmaniac last won the day on March 20

greenhillmaniac had the most liked content!

Community Reputation

226 Excellent

2 Followers

About greenhillmaniac

  • Rank
    Update Seeker and Maintainer

Profile Information

  • OS
    Windows 10 x64
  • Country

Recent Profile Visitors

5,089 profile views
  1. Maybe it's already installed in your system. Vista throws that error when updates are already installed (or when they really aren't applicable, but most of the time it's the former).
  2. I think I clarify this issue in the readme located at the root of the repository, but no. Monthly Rollups contain all previous and current patches for Windows and Internet Explorer. Security Only is for folks who don't want to use Monthly Rollups and wish to select which patches to install.
  3. Here's some repository updates. Seems like the new June updates haven't caused any issues compared to the May updates(?). Replaced Monthly Rollup with the new KB4503273 (located on the root directory of the repository) Added Security Only Updates, KB4499180 and KB4503287 (located in the folder "/Security Only (Post August 2018)") Replaced Internet Explorer Cumulative Update with KB4503259 (located in the folder "/Security Only (Post August 2018)") Replaced .NET Framework Security and Quality with: -KB4495604 for .NET 2.0 SP2 (located in "/NET 2.0 SP2/Security and Quality Rollup") -KB4495596 for .NET 4.5.2 (located in "/NET 4.5.2/Security and Quality Rollup") -KB4495588 for .NET 4.6-4.6.1 (located in "/NET 4.6-4.6.1/Security and Quality Rollup") Added .NET Security Only Updates with: -KB4495609 for .NET 2.0 SP2 (located in "/NET 2.0 SP2/Security Only") -KB4495593 for .NET 4.5.2 (located in "/NET 4.5.2/Security Only") -KB4495587 for .NET 4.6-4.6.1 (located in "/NET 4.6-4.6.1/Security Only") Added a new folder into the root directory of the repository named SHA2 with the Servicing Stack update KB4493730 and KB4474419 (new version that fixes SHA2 support for MSI files) and a readme explaining why these updates are needed Added Extra updates KB4501226 (located in "/Extras") with an updated readme file Guess this could also count has the changelog for updates released this month. If there are any issues do post to warn others. BTW, should I include the .NET Framework 4.7.2 installer and instructions on how to install it? Could be interesting. https://mega.nz/#F!txxRyLzC!1vBMGzMHiL864f3bl1Rj1w
  4. Lol, Microsoft cares so little about Vista that they just straight up say: "Install Server 2008 patches, we don't care..."
  5. I think it requires Windows 7 because of the .NET 4.7.2. Either way, I believe one can simply extract the program files from the installer by simply opening it with 7-Zip (or similar).
  6. There's also Paint.NET that requires .NET Framework 4.7.2. Anyone can test that program
  7. Has anyone tried the final .NET Framework 4.8 release? I don't have a Vista VM at hand right now. https://dotnet.microsoft.com/download/dotnet-framework/net48
  8. If you would've told a costumer from 2001 that their purchase of Windows XP would get updates until 2019 they would not believe you! Yet, here we are with a new patch out of the regular POSReady 2009 support window
  9. That would be the dream... I also undertook recently an effort to preserve PT-PT updates, and while I got some luck with some of the updates released in the early 2000s until 2004, after that they started hosting every new update in that URL format you've posted, making it almost impossible to retrieve them. At the absolute limit, one knowing the filename would run a random character generator to try and find the correct URL, but that would be extremely time consuming.
  10. Just noticed this post. I'll give the script a try and I'll report back. If everything works fine, I'll try and include it with my Server 2008 and Server 2012 update repository. Thanks for sharing this and welcome to MSFN! Hope you have a great time here
  11. Actually, I've already created an ISO file containing updates for 2000, XP, Server 2K3 and Vista. The ISO also includes Windows Live Essentials 2009 (XP compatible) and 2010 (Vista compatible). The problem is that updates for NT 5.x are language specific, so I only accumulated PT-PT updates. If there's any interest in releasing that to the public do let me know. (I also managed to salvage some PT-PT updates and hotfixes for Windows ME and 98 before they closed down the hotfix service.)
  12. From a fellow Portuguese countryman to another I say: "Bem vindo!".
  13. The IE11 install is offered as a regular Windows Update. In order to modify it we would need to resign the modified .mum files so that Windows 8.0 would be contemplated in them. This, unfortunately, requires access to Microsoft's tools to do so, something we just don't have at our disposal.
  14. Unfortunately, it's impossible to install IE11 on regular 8.0, since they only included Server 2012 and Embedded 8 Standard on the update files description, regardless of pre-requisite updates. Abbodi1406 also confirmed this in MDL (and he was the one that got Powershell 5.1 to install on Windows 8.0).
  15. The Easter bunny hasn't forgotten about our favorite NT 6.2 OS: Replaced Monthly Rollup with the new KB4493451 (located on the root directory of the repository) Replaced Flash Player Security update with KB4493478 (located on the root directory of the repository) Added Security Only Updates, KB4489884 and KB4493450 (located in the folder "/Security Only (Post September 2016)") Replaced Internet Explorer Cumulative Update with KB4493435 (located in the folder "/Security Only (Post September 2016)") Added .NET Framework September Security Only Updates: -KB4488660 for .NET 3.5 SP1 (located in "/.NET Framework 3.5 Updates") -KB4488668 for .NET 4.5.2 (located in "/.NET Framework 4.5.2 Updates") -KB4488664 for .NET 4.6.x-4.7.x (located in "/.NET Framework 4.6.x-4.7.x Updates") Added extra update KB4490128 (located in "/Extras (Non Security Updates)") The sad news of the month is that IE11 is not Windows 8.0 compatible. I tried extracting the MSU package and even the CAB file, but analyzing the update.mum I noticed that they only included support for Server 2012 and Embedded: <parent> <assemblyIdentity name="Microsoft-Windows-ServerCore-Package" version="6.2.9200.16384" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" buildType="release"></assemblyIdentity> <assemblyIdentity name="Microsoft-Windows-Embedded-SKU-Foundation-Package" version="6.2.9200.16384" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" buildType="release"></assemblyIdentity> </parent> Which means Internet Explorer 10 will only have security updates until the beginning of 2020. I would suggest doing what @Jody Thornton's been doing and disabling IE10 altogether from the "Windows Features" function when the time comes. As for everything else, the .NET updates are only for adding support for the new Japanese calendar and the new timezone update does not replace previous timezone updates. https://mega.nz/#F!ExhDEbDA!pUhzXKVp5-hgzvylW_btfQ
×
×
  • Create New...