Lioninstreet
New member
- Local time
- 7:34 PM
- Messages
- 29
I'm in the situation that I have some critical programs that don't play nice with w10. So now with NT6.1 "dead" and WU is off-line, I was wondering if anyone could help out with some arrow pointing.
And just to get this out of the way, this thread is not intended to be a discussion about how to utilize the post EOL Microsoft updating, but the most efficient way to patch to current (1/20 EOL date) a clean install of w7 & s2k8r2.
I've worked with WHDownloader which is great to capture updates for off line storage (it finds over 600 of them) and can identify what has been superseded. But it wont handle installing them or providing the proper order for installing them.
I've also used WOL (windows off line updater). That's a viable option. Like WHDownloader, it downloads updates for off line storage for use with future installs. But it will also install them in the proper order. That said, it's setup to only pull a little over 200 of the OS & .NET security updates. But if you can figure out how to manually customize it's URL list, the program will then download other updates that are available as well.
The XP compatible WUMT (windows update mini tool) and the similar WUM (windows update manager based on .NET 4.5.1) will also handle downloading and installing, but they don't save updates for future installs. So as MS continues the practice of thinning out the download catalog, our "dead" OS's become more and more exposed.
And then there's the issue of updating the hotfixes, powershell updates, Remote Desktop Protocol, & Windows Management Framework. Not to mention DirectAccess, Active Directory Access Protocol, Remote Server Administration Tools, Virtual PC, WorkFolders, & Server Connector.
And then of course there is slipstreaming (which I personally haven't had much luck with probably due to inexperience and lack of knowledge). It seems like all have their strengths and weaknesses.
So if you're aware of links to any definitive guides for solutions, or have comments for how you found success, please share.
And just to get this out of the way, this thread is not intended to be a discussion about how to utilize the post EOL Microsoft updating, but the most efficient way to patch to current (1/20 EOL date) a clean install of w7 & s2k8r2.
I've worked with WHDownloader which is great to capture updates for off line storage (it finds over 600 of them) and can identify what has been superseded. But it wont handle installing them or providing the proper order for installing them.
I've also used WOL (windows off line updater). That's a viable option. Like WHDownloader, it downloads updates for off line storage for use with future installs. But it will also install them in the proper order. That said, it's setup to only pull a little over 200 of the OS & .NET security updates. But if you can figure out how to manually customize it's URL list, the program will then download other updates that are available as well.
The XP compatible WUMT (windows update mini tool) and the similar WUM (windows update manager based on .NET 4.5.1) will also handle downloading and installing, but they don't save updates for future installs. So as MS continues the practice of thinning out the download catalog, our "dead" OS's become more and more exposed.
And then there's the issue of updating the hotfixes, powershell updates, Remote Desktop Protocol, & Windows Management Framework. Not to mention DirectAccess, Active Directory Access Protocol, Remote Server Administration Tools, Virtual PC, WorkFolders, & Server Connector.
And then of course there is slipstreaming (which I personally haven't had much luck with probably due to inexperience and lack of knowledge). It seems like all have their strengths and weaknesses.
So if you're aware of links to any definitive guides for solutions, or have comments for how you found success, please share.
My Computer
- Computer type
- PC/Desktop
- OS
- W6.1 64
