heinoganda

Regarding KB2917500 I recommend my certificate updater. More information in this topic

How to uninstall this KB or prevented with an entry in the registry may I not write unfortunately!

Currently, it seems that the redirection was consciously changed by MS for WU/MU under IE. Whether this changes again is in the stars! As an alternative, following web links for Internet Explorer: for Windows Update http://update.microsoft.com/windowsupdate for Microsoft Update http://update.microsoft.com/microsoftupdate Here is a nice picture of our railway stations in Germany. Image source Twitter

Hey Den, do not fall asleep! I dare hardly write it, do not forget the MSI 4.5!

Just yesterday my own Updaterollup for May 2017 installed on my host computer (including the successor patch KB4018466 of KB4012598). The users who install the POSReady updates for their Windows XP monthly, I see no problem with this "WannaCrypt" attack. Maybe some users should reconsider it and yet use the POSReady updates for Windows XP.

Here is a link to the WSUS catalog, where a corresponding official download for Windows XP SP3 is available! http://www.catalog.update.microsoft.com/Search.aspx?q=KB4012598 XP SP3 For this vulnerability an appropriate topic was opened.

@Dave-H Complement: It is known that WEPOS / POSReady 2009 is not intended for use on a desktop computer and officially no Office products are supported! As we could see, WU / MU regularly is no longer supported under IE. Now the fact is the WU / MU (only available via links), with the most recent cumulative update for IE8, works perfectly however only as long as there is no update for an Installed Office product. It also means that the most recent updates have to be installed manually for the installed Office products before running WU / MU on IE. Due to the current situation, automatic updates should be disabled so that the system does not cause any unnecessary CPU load. Link for latest updates for Office 2007 products in the Download Center At the moment, it is a way to the goal! As far as I'm concerned, I'm going to think about the next time because of a little helper, where, by means of published download links, the necessary updates are downloaded and installed. Finally, only a cross-check with WU / MU.

This vulnerability was closed with the POSReady 2009 updates in March 2017 (KB4012598)!

With the current MSE definition, where the engine (mpengine.dll) is included!

@Roffen Please open the web links with Internet Explorer (IE)! @liamZ KB4020510 can only be downloaded manually!

Information about a security vulnerability in MSE! Care should be taken to ensure that the protected version of Malware Protection Engine 1.1.13704.0 is used. Further information: https://technet.microsoft.com/library/security/4022344.aspx

@Roffen Currently, it seems that the redirection was consciously changed by MS for WU/MU under IE. Whether this changes again is in the stars! As an alternative, I can offer you the following web links for IE: for Windows Update http://update.microsoft.com/windowsupdate for Microsoft Update http://update.microsoft.com/microsoftupdate This has already been pointed out in previous comments. KB976749 is an ancient patch for IE8 which has no relevance any more! @glnz Whether the two updates for .NET Framework are distributed via automatic updates, as well as WU/MU under IE, will show today (will in any case inform). Currently, the two updates for the .NET Framework are not delivered via automatic updates, as well as not with WU/MU under IE.

Flash Player Version 25.0.0.171 has been released! The Internet Explorer ActiveX plugin is available here: http://fpdownload.adobe.com/get/flashplayer/pdc/25.0.0.171/install_flash_player_ax.exe The NPAPI for Firefox is available here: http://fpdownload.adobe.com/get/flashplayer/pdc/25.0.0.171/install_flash_player.exe Currently, the Flash Player for Opera or Chromium (install_flash_player ppapi.exe) version v25.0.0.171 can be used! Tested with Google Chrome v49.0.2623.112. Installation Info for Google Chrome:

You would be surprised at what is in the .NET Framework Updates (SFX archive)! Regarding WU and MU in the IE, that will not change, especially since I have been watching for a long time. It started with the change from Windows Update to Microsoft Update no longer worked (only with the Weblink possible).

To the subject .NET framework, since I do not have to lead a "belief war" since it does not change the fact that the .NET Framework 2 is a component of the .NET Framework 3.5. The web link (http://windowsupdate.microsoft.com) is fixed in the wupdmgr.exe file as well as in IE files. The redirection goes to this website https://support.microsoft.com/en-us/help/12373/windows-update-faq Guess that this is not a bug, but it is willed by MS! Many paths lead to Rome, matching weblinks in the IE favorites list or shortcuts to the following destinations "%ProgramFiles%\Internet Explorer\iexplore.exe" http://update.microsoft.com/windowsupdate "%ProgramFiles%\Internet Explorer\iexplore.exe" http://update.microsoft.com/microsoftupdate

Version 3.5 of the .NET Framework was released on 19 November 2007. As with .NET Framework 3.0, version 3.5 uses Common Language Runtime (CLR) 2.0, that is, the same version as .NET Framework version 2.0. In addition, .NET Framework 3.5 also installs .NET Framework 2.0 SP1 and 3.0 SP1 (with the later 3.5 SP1 instead installing 2.0 SP2 and 3.0 SP2), which adds some methods and properties to the BCL classes in version 2.0 which are required for version 3.5 features such as Language Integrated Query (LINQ). These changes do not affect applications written for version 2.0, however. As with previous versions, a new .NET Compact Framework 3.5 was released in tandem with this update in order to provide support for additional features on Windows Mobile and Windows Embedded CE devices. The source code of the Framework Class Library in this version has been partially released (for debugging reference only) under the Microsoft Reference Source License. .NET Framework 3.5 is supported on Windows XP, Server 2003, Vista, Server 2008, 7, Server 2008 R2, 8, Server 2012, 8.1, Server 2012 R2, 10, and Server 2016. source https://en.wikipedia.org/wiki/.NET_Framework_version_history#.NET_Framework_3.5 KB4020517 and KB4014580, as KB4020510 and KB4014570 can easily extract with 7Zip and compare the contents of the patch files (extension msp). KB4014580 and KB4014570 are no longer required! http://www.msfn.org/board/topic/171814-posready-2009-updates-ported-to-windows-xp-sp3-enu/?page=39#comment-1106194 (I have updated accordingly!)

There are updates for the security updates KB4014580 and KB4014570! Further information: https://support.microsoft.com/en-us/help/894199/description-of-software-update-services-and-windows-server-update-services-changes-in-content-for-2017 Fixed a problem with the Powershell (stop-computer command fails. When this issue occurs, you receive a "Privilege not held" error message). More I could not find out.

Current Update for .NET Framework 2.0 sp2: NDP20SP2-KB4020517-x86.exe 05/01/2017 File download Current Update for .NET Framework 4: NDP40-KB4020510-x86.exe 05/01/2017 File download Info: .NET Framework 2.0 sp2 and .NET Framework 3.0 sp2 are a component of the .NET Framework 3.5 sp1 installer packages.

Otherwise for the POSReady updates I see no problem, which fits your specifications.

Unfortunately I can not offer a permanent solution at this point. A final question, how big is the memory of the computer (Due to the size of the definition files, I currently have to provide at least 850 MB in the VM)?

Hi DrWho3000, firstly is installed MSI 4.5 (KB942288-v3)? If POSReady updates are installed, it is necessary to have MSI 4.5, because there are security updates that otherwise destroy the existing MSI 3.1! This means that programs such as MSE can no longer be installed correctly. Second, how much memory does the computer have? What version of MSE is used?

So definitely also no POSReady key in the registry. Ever tried to reinstall MSE?

That is not normal. Will POSReady updates be installed?

It is nice to hear that your .NET Framework 4 is installed correctly again. The worst thing about a .NET Framework installation is the eternal update process. Since I have found a way to accelerate this.