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

    442
  • Donations

    $0.00 
  • Joined

  • Last visited

  • Days Won

    7

greenhillmaniac last won the day on August 25

greenhillmaniac had the most liked content!

Community Reputation

303 Excellent

4 Followers

About greenhillmaniac

  • Rank
    Update Seeker and Maintainer

Profile Information

  • OS
    Windows 10 x64
  • Country

Flags

  • Country Flag

Recent Profile Visitors

6,917 profile views
  1. Forgot about this thread. I rearranged some items in my Mega account, and those links got expired. I'll update them as soon as I can.
  2. Is that the System Update Readiness Tool? I think you only need that if you have trouble installing updates. If your system was freshly installed, there's no need. I usually go: Platform Update + Suplement > Internet Explorer 9 > Net Framework 3.5, 4.6 and updates > Powershell 2.0 + BITS 4.0 > Media Player 11 > General > Security > Hotfixes The idea is to install as many updated components as possible before moving on to the General, Security, etc updates. That way, the updates will cover a wider range of software. I'd say so, yeah. The main one would be the TLS 1.1 and 1.2 updates, but you can also add the SHA2 updates (they do make Windows Update non functional, but @abbodi1406 managed to make it work regardless. go to MDL and you'll find it) In here you won't find any. It's usually best if you create your own.
  3. I have a R9 380, precisely the point where AMD drivers stopped working. Had to used a hacked together Embedded version of the drivers. Not ideal. Never heard of SDI. I'll have to check it out. EDIT: Yeah, your GPU still had officially compatible drivers with Vista, that's why SDI (Snappy Driver Installer?) found a matching pair.
  4. Any chance you'd also take a look at AMD drivers? They stopped working in mid-2015 when they changed driver branches (introduced with the RX 300 series: https://www.guru3d.com/files-details/amd-catalyst-15-15-download.html).
  5. So far I have it on Mega and my external HDD. Don't know if I can put in on Archive.org If you want to include subfolders just add the /s switch to forfiles.
  6. A small update on the repository. Thanks to the efforts of @Regele there are now EN-US version of IE9 and KB937286. I've also change the folders names in the Ultimate Extras to English.
  7. Will this custom kernel allow the installation of newer Windows 7 drivers on Vista?
  8. For the most part, these telemetry updates have all been included in the newest Monthly Rollup, so if you want to avoid it you should use @abbodi1406's script hosted on Askwoody: https://www.askwoody.com/forums/topic/2000012-neutralize-telemetry-sustain-win-7-8-1-monthly-rollup-model/
  9. You can use the /l flag to create a log. It would go something like this: start /w pkgmgr /ip /m:C:\Update\update.cab /s:C:\Sandbox /l:C:\log.txt
  10. Unfortunately, as far as I know, pkgmgr does not show any visual progress on update installation, unlike its successor, Dism. When an update is not applicable or has been superseded, pkgmgr simply doesn't install it, so you shouldn't have to worry too much about that. As long as you install updates in the correct order (from oldest to newest, installing first the Platform Update alongside IE9), you should be gold. I guess you could just install the Windows 7 AIK and adapt the script to use Dism, as it will act as a wrapper for pkgmgr, but I'm not sure it displays any more information.
  11. It does not. MS never bothered to port DiagTrack to NT 6.0.
  12. SHA2 updates disable Windows Update, since they bump the build number to 6003 Yes, you open command prompt with admin rights, then run the commands. I recommend you put the updates in a path with no spaces, like "C:\Updates", just so it's easier to run the commands.
  13. Yes, I mention it in the thread. Not entirely, but it is recommended that you install previous updates first. Some of the newer ones might not install without pre-requisites.
  14. Yeah, I posted it in a thread somewhere and it got lost to time (I can't find it either!). I still have those drivers archived: https://mega.nz/file/wgxAFCzJ#N8_D1L59p8isZ2Gz4nmgBPxkdXlFqS52uxbctbvumDQ They're AMD Embedded drivers based on an early 15.100 branch, still compatible with Vista. To use your R9 300 GPU (or any other, since it has few cards listed) with them you need to edit the INF and add your HWID (I think I added my GPU's HWID in that archive, the R9 380, so you could use that as the baseline for changes specific to your card).
  15. I have a pertinent question... Why create a thread, when this topic is already being discussed: https://msfn.org/board/topic/181739-windows-update-error-code-80072efd/ https://msfn.org/board/topic/178377-on-decommissioning-of-update-servers-for-2000-xp-and-vista-as-of-july-2019/ Furthermore, you're linking to the Server 2008 update repository that I created without any kind of credit. Honestly, this thread seems pointless...
×
×
  • Create New...