![]() ![]() Do y'all happen to know what/if there's a specific few updates to have to manually download and Install in Windows XP to fix it's automatic updates client at this time? It's not for jerry-rigging it to be supported now by sneaking new updates in, nor is it going to make it any more secure that it was at EOL, would just be so nice to get it's officially intended updates that Microsoft officially provided, of which do still exist on the servers, it's just that the way the Windows Update client initially connects to the service got changed making the barebones fresh install of XP unable to connect to Windows Update service, and hoping to find out if/what updates to manually install to get it connecting to Windows Update for now. (In case anyone do be wondering what those are if they are facing this issue, they are KB3020369, and then next in order, install KB3172605, whilst paying attention to x86 or 圆4.)Īnyways, that's how to fix it in Windows 7 for the time being. This is rather unrelated, but I have a hunch this scenario may be similar to this: When Installing a fresh copy of Windows 7 now in 2022, it's Windows activation, and Windows Update client won't work, but there are two updates to go manually download and manually install, then reboot the computer, then the activation, and automatic updates work. NET framework part, was something on Superuser website if I remember correctly. NET framework updates, I forget what I saw on that. Something about a certain servicing stack update(s) would be a possible fix to get the older clients to connect to the Windows Update servers, and be able to download and install the official previously released updates. Heard about an SHA change in July/August of 2020 that made the older Windows Update clients be unable to connect to Windows Update servers. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |