![]() ![]() And this, even with a list, is quite difficult to do. The first method is easier and faster, but it has a serious drawback - you need to download all the necessary updates. There are two ways to get an up-to-date distribution of Windows 7: integrating updates directly into the image, and using a reference system to download and install updates. We will tell you how to do this in this article. You can avoid this if you compile your own distribution kit containing all the current system updates. Therefore, for the system administrator, the issue of its deployment is relevant, but since the last official image was built quite a long time ago, the systems installed with its help require a fairly large number of updates. Thanks to abbodi86's post on fixing RDP 8 (this drove me crazy for a month).Today Windows 7 is the main corporate system, de facto, taking over from Windows XP. This should work as a clean base for EOS builds. There are no settings changes or feature/component removals to worry about. Use the Pre-RDP preset first if adding RDP 8. NDP48 is installed here, instead of using the KB equivalent for visibility. There will be no more WU updates, except for MRT tool and undesired CEIP/telemetry patches.įor optional software, I add Visual C++ libraries (2010, 2013, 2015-2019), WMF 5.1 and MSE. Skip this if you're not interested in RDP. For RDP 8, pre-integrate 4819, 26 separately into a clean SP1 before applying the normal build (SSU, SP2, Platform, etc).Graphics component (6019) & WUagent don't need to be checked, both are now part of other rollups.Monthly rollup is Jan 2020 preview (9601), includes the black wallpaper fix.Updates Analyze wants a newer (ESU) SSU, ignore as 6952 is last for EOS.WU ends up matching almost everything on the live update list (excluding ESU versions). Now that EOS updates have stopped, I decided to see what WU required on a clean sheet of Ultimate SP1 plus the core basics: (Kind of like a final clean slate install of Win7.) I won't know until I try a manual Refresh on my other Win7 box.īut I thought I would mention this in case someone is having the same problem and wants to refresh their Win7 now that Win7 has reached EOL. He was explaining how people were finding that you had to install a new SS after a bunch of regular patches for everything to work.) (I thought of this the other day while reading Ask Woody. So now my theory is that it is some new Service Stack update in a running, patched Win7 that is interfering with another, obsolete SS in the running Win7. ![]() (Hard to catch a log because Windows wants to immediately revert back to the old Windows.)īut then I had a brainstorm (a brainwave in Clanger's world) - I tried Refreshing running, updated versions of Win7 back to an unpatched, vanilla Win7 SP1 iso. I assumed it was something that I removed using NTLite - or some arcane software that caused the failure. ![]() (That is, I run a patched Win7 setup.exe from inside a running Win7 machine, and chose "upgrade - keep my files and applications." (Or words to that effect.))įor the past 6 months, my Refresh of Win7 has failed. So, I've been trying to do my version of a (manual) Win7 Host Refresh on two Win7 boxes that have been updated over the years via NTLite. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |